Dell data domain immutability

[phiaramos]

Hello,

I'm confused with the immutability with Data Domain. We have enabled the Retention Lock on Dell DD side, having 30days minimum and 5years maximum.
Then set the backup repository 'make recent backups immutable for: 30 days'

We encountered the below warning on the jobs
2/8/2024 10:24:57 AM :: A problem occurred during setting the immutable flag: Immutability period for some backups is lower than the minimum value allowed by the target repository, using the minimum supported value instead.

I have read the https://www.veeam.com/kb4501
So we tried adjusting the immutability retention on the Veeam repo to 31 up to 40 days, but still getting the same warning when running the job again. What should be the interval between minimum Retention Lock and Veeam repo immutability retention should be?

Regards,
Phia

[foggy]

Hi Phia, do you have GFS retention configured for this job?

[we!come]

Hi foggy,

What happen if I have to configured GFS retention for this job ?

[Dynamic]

Hello,

I'm confused with the immutability with Data Domain. We have enabled the Retention Lock on Dell DD side, having 30days minimum and 5years maximum.
Then set the backup repository 'make recent backups immutable for: 30 days'

We encountered the below warning on the jobs
2/8/2024 10:24:57 AM :: A problem occurred during setting the immutable flag: Immutability period for some backups is lower than the minimum value allowed by the target repository, using the minimum supported value instead.

I have read the https://www.veeam.com/kb4501
So we tried adjusting the immutability retention on the Veeam repo to 31 up to 40 days, but still getting the same warning when running the job again. What should be the interval between minimum Retention Lock and Veeam repo immutability retention should be?

Regards,
Phia

Hi Phia,
...did this warning occured after reached your 30days of the min-retention-period on your compliance mode enabled mtree?
I have currently an open case on that, could be an issue within the newly retention-lock feature since 12.1

We are currently testing, what happens, when we only do a "fresh" backup/backup chain (in our case, we had already a backup-chain, and later activated the new feature on it).

Best regards
Markus

[rennerstefan]

Hi,
If you have a case open please share the case number so we can also have a look at the status.
Thanks

[3d0]

Hello,
I'm writing for the same warning but in a different scenario:

03/04/2024 06:12:25 :: A problem occurred during setting the immutable flag: Immutability period for some backups exceeds the maximum value allowed by the target repository, using the maximum supported value instead.

I'm aware that it's legits and appears due to the difference bethween the immutability configured on our DataDomain (15gg), and the GFS retentiont that maintains: 14 restor point + weekly full 4 weeks + monthly full 12 months.

But the above scenario is the desidered one.

Is there a way to tell Veeam to ignore this specific check? As to avoid the warn to appear?

In eg., something like the register key that avoid warnings on free space as follow:
Key Location: HKLM\SOFTWARE\Veeam\Veeam EndPoint Backup
Value Name: DisableVolumeFreeSpaceCheckWarning

Thank you!

[n.mattia]

Hi, thank you 3d0 I have the same issue.
It would be awesome to suppress these warnings or, better, have the ability to set the GFS restore point immutability period.
Having immutable restore points for 2 years is likely to cause saturation of backup repositories.

[3d0]

Hi n.mattia,

as you suggested: a feature like the ability to set the immutability period for restore points of GFS chains could be a nice workaround for the warning that appears.

Several customer already asked how to silence the warning:

"A problem occurred during setting the immutable flag: Immutability period for some backups exceeds the maximum value allowed by the target repository, using the maximum supported value instead."

Regards.

[foggy]

There's a registry value to suppress immutability warnings, please contact support to obtain it.

[3d0]

Thank you Foggy,

I'll advise our customers.

Have a nice day.

[stewsie]

Hi

I also have an issue with this warning. We are on Veeam 12.3 and have recently enabled immutability on the DD so we can carry out some tests. It was set on the DD as min 14 and max 15 for testing. The repository in Veeam is configured to make backups immutable for 14 days and the backup job is also configured to keep 14 retentions and for GFS 2 weekly backups. What have I configured incorrectly? We have just changed the setting on the DD so the min is 14 and max 30 but no change

[foggy]

GFS backups will be kept longer than that 15 days max you've configured, hence the warning.

Please review the following for a better understanding:

https://helpcenter.veeam.com/docs/backu ... ata-domain
https://www.veeam.com/kb4501

[stewsie]

In conjunction with Veeam support we have edited the DD setting to 60 days Max and still get the warning message. Logs have been uploaded

[rennerstefan]

@stewsie can you please share the veeam support case id? I would likt to have a look
Thanks

[stewsie]

07664549 is the case number

[foggy]

Hi Paul, just to clarify, are you seeing the warning for the 'lower than the minimum value' for the immutability period or 'higher than the maximum'?

[stewsie]

"A problem occurred during setting the immutable flag: Immutability period for some backups is lower than the minimum value allowed by the target repository, using the minimum supported value instead. "

The backup job is now configured to keep 7 days with 1 weekly backup. Initailly it was 14 and then changed to 21 all part of investigating the warnings

The Veeam repository is configured for 14 days which is the min setting on the DD. It is reading the settings correctly from the DD as if I try to change the repository setting to a lower or even a higher number I get the warning message.

Another strange thing is that in Veeam One I see no immutable backups. Today I added 4 more VMs to the test immutable backup job and now in Veeam One I see the 4 VMs added. Neither of these VMs alerted when the backup job ran. I need to wait for another 6 days to see if when the number of retentions is reached (7) to see if they also alert when the backup runs.

Never had issues like this when we tested immutability using S3 storage

[foggy]

Try to lower the min allowed value on the storage (say, to 13 days). There's a 'grace' period in Veeam B&R to cover things like time mismatch, job duration and timeouts, but there's a chance it is not enough in your case for some reason, and your 14 days are lower than 14 days on the array, resulting in the warning.

[stewsie]

My colleague who manages the DD told me it isn't possible to change the Min value. I have added the registry key to at least surpress the warnings.