Hello,
We have a backup copy job that offloads data to an S3 storage. We want to change the bucket used, but for a new backup copy job. The question is: if we deactivate the first backup copy job, will it retain the applied retention settings? Currently, we have a 15-day retention, with 7 days set as immutable.
Veeam 12
Thank you!
Best answer by Chris.Childerhose
If you are disabling the initial Backup Copy job, then it will retain the retention and apply it in the background I believe. The new job will use whatever retention is set up.
See this section of the help about retention - Short-Term Retention Policy - User Guide for VMware vSphere (veeam.com)
+21If you are disabling the initial Backup Copy job, then it will retain the retention and apply it in the background I believe. The new job will use whatever retention is set up.
See this section of the help about retention - Short-Term Retention Policy - User Guide for VMware vSphere (veeam.com)
Hello,
we have some “orphaned” Backups which we have to keep for retention policy reasons.
But I don’t have the impression, these backups are processed by the background policy retention checks.
Manually triggering the check using “apply retention now” on the backup node doesn’t seem to process detached backups …
Am I right and is there an alternative way to scan orphaned backups (via PoSh ?) for outdated backup files?
Thank you,
Stefan
+21Hello,
we have some “orphaned” Backups which we have to keep for retention policy reasons.
But I don’t have the impression, these backups are processed by the background policy retention checks.
Manually triggering the check using “apply retention now” on the backup node doesn’t seem to process detached backups …
Am I right and is there an alternative way to scan orphaned backups (via PoSh ?) for outdated backup files?
Thank you,
Stefan
According to this the background retention should clean up your Orphaned backups - Background Retention - Veeam Backup & Replication User Guide
You may need to contact support to figure out why it is not doing this but first check the retention period for those backups as it might not be at the point of being able to remove backups yet.
Wow, thanks for the quick reply!
Yes, I still need to double-check that I'm not mistaken.
I'll look into it.
Best regards, Stefan
+21Wow, thanks for the quick reply!
Yes, I still need to double-check that I'm not mistaken.
I'll look into it.
Best regards, Stefan
Not a problem. If you have other questions feel free to ask but let us know how things go so we can add to this post with more information on the subject.
It was finally easy to analyze and to resolve:
we were mapping an older backup chain imported from a replaced backup infrastructure.
the old backup chain contained some servers twice - an old error I never noticed until now.
The 2 years old backup duplicates were registered to veeam correctly but longtime out of retention scope. I manually removed the duplicate backup chains from the backup copy job - and now they are delete from the configuration database.
I also checked the log for the background retention task - all other servers in this “reused” backup chain are processed correctly.
Thank you again,
Stefan
+21It was finally easy to analyze and to resolve:
we were mapping an older backup chain imported from a replaced backup infrastructure.
the old backup chain contained some servers twice - an old error I never noticed until now.
The 2 years old backup duplicates were registered to veeam correctly but longtime out of retention scope. I manually removed the duplicate backup chains from the backup copy job - and now they are delete from the configuration database.
I also checked the log for the background retention task - all other servers in this “reused” backup chain are processed correctly.
Thank you again,
Stefan
Great. Glad to hear you solved the issue and got things working again for retention.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.