#1 Global Leader in Data Protection & Ransomware Recovery

Immutability Warning for Data Domain Repository: "Immutability flag on backups was set with warning"

KB ID: 4501
Product: Veeam Backup & Replication | 12 | 12.1
Published: 2023-10-03
Last Modified: 2023-12-05
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

A backup job that targets a Dell Data Domain repository completes with the warning, "Immutability flag on backups was set with warning:", specifically with the endings:

Immutability period for some backups exceeds the maximum value allowed by the target repository, using the maximum supported value instead.

or

Immutability period for some backups is lower than the minimum value allowed by the target repository, using the minimum supported value instead.  

Cause

This occurs when the immutability period required by the job within Veeam Backup & Replication either exceeds the 'Max retention period' value or is lower than the 'Min retention period' value set for Retention Lock on the target Data Domain storage.

Starting from Veeam Backup & Replication 12.1, backups stored on a Data Domain store can be marked as immutable to prevent accidental or malicious deletion. If the max and min retention period values on the target Data Domain store are not set high and low enough to accommodate a value for the immutability period needed by the job, Veeam will set the immutability period for a file to a corresponding value allowed by the Data Domain store setting, which will result in the warnings described in this KB article.

For example, if the immutability retention Veeam would set is 30 days, but the 'Max retention period' within the Data Domain settings is only 14, Veeam will instead set the immutability to 14 and display the 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.

Solution

To address this, check the Retention Lock settings on the Data Domain store and make sure those are set to a value greater and lower than what's needed by the backup job(s) writing to the storage. If the 'Max retention period' setting is too low, increase it to match the required period, if the 'Min retention period' setting is too high, decrease 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 'Max retention period' setting on the Data Domain store has to be set to a value higher than 7 years.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.