OPERATIONAL DEFECT DATABASE
...
...
A backup job that targets an HPE StoreOnce Catalyst repository may display either of the following messages: In Veeam Backup & Replication 12.0, the job will fail and display the error: OSCLT_ERR_IMMUTABLE_EPOCH_REQUEST_EXCEEDS_MAXIMUM. Err: -1817 In Veeam Backup & Replication 12.1, the job will complete with the following warning: Immutability flag on backups was set with warning: Immutability period for some backups exceeds the maximum value allowed by the target repository, using the maximum supported value instead.
This situation occurs when the immutability period required by the job within Veeam Backup & Replication exceeds the value set for 'Maximum ISV Controlled Data Immutability Retention' on the target Catalyst Store. Starting with HPE StoreOnce firmware version 4.3.2, backups stored on a Catalyst Store can be marked as immutable to prevent accidental or malicious deletion. This feature is supported by Veeam Backup & Replication 12. However, to use this feature, the 'Maximum ISV Controlled Data Immutability Retention' setting on the target Catalyst Store must be configured to a value greater than the immutability period needed by the job. If this value is not set high enough, Veeam will attempt to set the immutability period for a file to a value greater than what is allowed by the Catalyst Store setting, which will result in the following behavior: For Veeam Backup & Replication 12.0, an error will be displayed, and the job will fail. For Veeam Backup & Replication 12.1, the job will complete with a warning explaining that the immutability period of the file was set to the maximum value permitted by the Catalyst Store. For example, if the immutability retention Veeam would set is 30 days, but the 'Maximum ISV Controlled Data Immutability Retention' on the Catalyst Store is only 14, Veeam will instead set the immutability to 14 and display the warning: Immutability flag on backups was set with the warning: Immutability period for some backups exceeds the maximum value allowed.
To address this situation, check the 'Maximum ISV Controlled Data Immutability Retention' setting on the Catalyst Store and ensure it is set to a value greater than the immutability period needed by the backup job(s) writing to the storage. If the setting is too low, increase it to match the required period. Then, re-run the job(s) to confirm the issue is resolved. Note: When calculating the maximum immutability duration required for Veeam backup jobs, it's important to consider any GFS (Grandfather-Father-Son) restore points that may be created. For example, if long-term retention in the backup job is set for 7 yearly full backups, the 'Maximum ISV Controlled Data Immutability Retention' setting on the Catalyst Store must be set to a value higher than 7 years.
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
