I have a customer that would like to have a way to save decommissioned server backups for 7 years. Their normal retention for backup jobs is 1 year. They use Data Domain for archive storage. When they decommission a server they would like to keep the backup for 7 years. My thought was to create a second repository on the Data Domain, move the backups there and then remove the server from the backup job. Would this effectively exclude those backups from retention policies?
Solved
Long term storage for Decommissioned servers
Best answer by TylerJurgens
Another option would be to simply take a VeeamZIP of the VM (before you delete it) and target whatever repository you want to target for long term storage and set it to expire after 7 years.
That would take a backup of the VM from the current point in time and keep it until it expires out. You can also set encryption on that backup if you should so choose.
+20Yes, any VM you remove from a backup job would then exclude it from any of the Job’s settings, including Retention. It would also, if it is set, invoke the Deleted Items setting in the Storage section > Advanced button > Maintainance tab, and delete the VM server after the days set here.
How were you planning on moving the VM data to your 2nd, long-term DD Repo?
Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
I was just going to remove the server from the job - then use the console GUI, right click the server under “Disk” and select move...but that only moves to another job. I expect I would need to setup a CIFs and do a manual copy.
Sorry for my confusion...I would use the “Copy Backup” selection when right-clicking the server. ( I knew it was in there somewhere!)
+21mjkellerii wrote:
Sorry for my confusion...I would use the “Copy Backup” selection when right-clicking the server. ( I knew it was in there somewhere!)
Yes, that is the option to move the backups between repositories.
Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
+7Another option would be to simply take a VeeamZIP of the VM (before you delete it) and target whatever repository you want to target for long term storage and set it to expire after 7 years.
That would take a backup of the VM from the current point in time and keep it until it expires out. You can also set encryption on that backup if you should so choose.
Tyler Jurgens | Senior Technical Product Marketing Manager | Veeam Legend x3 | vExpert ** | VMSP/VMTSP | VCP-2020 | VSP/VTSP | Tanzu Vanguard | VMUG Calgary Leader | VUG Canada Leader | https://explosive.cloud | @Tyler_Jurgens | BlueSky: @tylerjurgens.bsky.social
+8VeeamZIP was going to be my suggestion as well...a one-time backup that’s not subject to the normal retention policies.
Derek M. Loseke, Senior Systems Engineer | Veeam Legend 2022-2024 | VMSP/VMTSP | VCP6-DCV | VSP/VTSP | CCNA | https://technotesanddadjokes.com | @dloseke
+20mjkellerii wrote:
Sorry for my confusion...I would use the “Copy Backup” selection when right-clicking the server. ( I knew it was in there somewhere!)
Yep...that’s what you could do.
Others have mentioned performing a VeeamZIP operation as well. So, you have a couple options you could do.
Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
VeeamZip would work for most cases and is probably the best and easiest solution. This customer however will need to archive backups of Physical machines - so the best solution for them is the extra repository. Thanks everyone for you responses!
Comment
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.