• EN
Solved

Long term storage for Decommissioned servers

  • 25 January 2024
  • 8 comments
  • 110 views
M
Userlevel 2

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?

icon

Best answer by TylerJurgens 25 January 2024, 22:32

View original

8 comments

coolsport00
Userlevel 7
Badge +17

Yes, 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
M
Userlevel 2

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.

 

M
Userlevel 2

Sorry for my confusion...I would use the “Copy Backup” selection when right-clicking the server.  ( I knew it was in there somewhere!)

Chris.Childerhose
Userlevel 7
Badge +20

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 - VMCA2022 | VMCE2023 | Veeam Vanguard 7* | Veeam Legend 3* | vExpert 5* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
TylerJurgens
Userlevel 7
Badge +6

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.

Tyler Jurgens | Cloud Infrastructure Engineer | Veeam Legend x2 | vExpert ** | VMSP/VMTSP | VCP-2020 | VSP/VTSP | Tanzu Vanguard | VMUG Calgary Leader | VUG Canada Leader | https://explosive.cloud | @Tyler_Jurgens | BlueSky: @tylerjurgens.bsky.social
dloseke
Userlevel 7
Badge +6

VeeamZIP 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-2023 | VMSP/VMTSP | VCP6-DCV | VSP/VTSP | CCNA | https://technotesanddadjokes.com | @dloseke
coolsport00
Userlevel 7
Badge +17

 

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
M
Userlevel 2

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


Terms & Conditions