We have about 100 VMs to backup each night. about 70 require 30 day retention, the rest require several years of monthlies to be kept.
I was going to create two separate backup jobs for these, but I wonder if I can back them all up daily in one job for 30 days and have a backup copy job pointing at all the VMs we have tagged for '10 year retention' instead?
It's my understanding the backup copy job doesn't necessarily have to point to a backup job, but can just point to a group of tagged VMs instead.
-
- Expert
- Posts: 114
- Liked: 3 times
- Joined: Sep 02, 2010 2:23 pm
- Full Name: Steve B
- Location: Manchester, UK
- Contact:
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Is this a valid backup\copy job configuration.......
Hi Steve, yes, this is a valid approach, you can define the scope of the backup copy jobs as you wish.
-
- Expert
- Posts: 114
- Liked: 3 times
- Joined: Sep 02, 2010 2:23 pm
- Full Name: Steve B
- Location: Manchester, UK
- Contact:
Re: Is this a valid backup\copy job configuration.......
OK, thanks for confirming. We'd always previously just done a backup copy job of an existing backup job. I guess the copy job is pretty much an independent entity though. The name is a bit misleading.
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Is this a valid backup\copy job configuration.......
Correct, instead of copying whole backup chain blindly backup copy job will synthetically create required restore points in "target" location from VM data in source backup repositories. Thanks.
Who is online
Users browsing this forum: AdsBot [Google] and 39 guests