Task fails with "Repository is not compatible with Catalyst Store with fixed block setting enabled"

A Veeam Backup & Replication job targeting a StoreOnce Repository backed by a Catalyst Store that has Fixed Block Chunking enabled  fails with either of the following errors:

Repository <repository_name> is not compatible with Catalyst Store with fixed block setting enabled

Error: OSCLT_CLTERR_VARFIX_WRITE_SIZE_NOT_MULTIPLE_OF_CHUNK_SIZE. Err: -3113
 Failed to write data to the object

This error message indicates that the Catalyst Store has Fixed Block Chunking enabled, but the StoreOnce Repository within Veeam Backup & Replication does not have block alignment enabled. Align backup file data blocks is disabled because prior to Veeam Backup & Replication 12, the default was for that setting to be disabled when creating a StoreOnce Repository.

Starting with StoreOnce firmware version 4.3.2, HPE provided the ability to enable fixed block chunking on a Catalyst Store during its creation to improve incremental backup and synthetic full performance for backup files pre-aligned by Veeam Backup & Replication. This functionality is supported starting in Veeam Backup & Replication 11, and requires that block alignment be enabled for the StoreOnce Catalyst repository.

If the Catalyst Store has fixed block chunking enabled, the Align backup file data blocks option must be enabled within the StoreOnce Repository created in Veeam Backup & Replication.

• If Veeam Backup & Replication 11/11a is installed, edit the Store Once repository and manually enable the Align backup file data blocks option.
  
• If Veeam Backup & Replication 12 is installed, edit the StoreOnce repository and click Next through each of the repository wizard pages. Veeam Backup & Replication will automatically update the repository settings to match the StoreOnce required settings.
  

 

Note: Starting in Veeam Backup & Replication 12, when creating a new StoreOnce Repository Align backup file data blocks option is automatically enabled.

If either of the errors mentioned above has occurred and the block alignment option is enabled, the jobs will begin to function but will not benefit from fixed block chunking. Since the existing backup chains, already on the repository, are using variable chunks that do not match the new fixed chunks, you will not get the full fixed block performance improvement, and storage space consumption on the StoreOnce will be impacted. To start getting the performance improvements immediately and not have increased disk space consumption, after Align backup file data blocks is enabled, a new backup chain must be started by forcing the creation of a new Active Full backup.