Up to this point, for a particular client I have been doing a "One Server, One Job" rotation. I see the error of my ways and I want to start grouping them.
What's the best way to do that? I was guessing it would be best to group servers with identical operating systems but I'm also wondering if I should be mindful of the size of the various VMs.
What if they reside on different local repositories?
-
- Service Provider
- Posts: 137
- Liked: 1 time
- Joined: Jan 08, 2010 5:15 pm
- Full Name: Seth Zwicker
- Contact:
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Advice on offsite Backup?
Seth, you can group VMs using any factor that is reasonable in your case. It can be grouping critical VMs together to have similar SLA (lower RPO, for example), or VMs that should have similar retention. Veeam B&R performs dedupe between VMs in the job, so, right, the more VMs with similar OS (or even created from the same template) the job has, the higher space savings are. Here's also one of the existing topics regarding this.
-
- Service Provider
- Posts: 137
- Liked: 1 time
- Joined: Jan 08, 2010 5:15 pm
- Full Name: Seth Zwicker
- Contact:
Re: Advice on offsite Backup?
What if the VMs (identical OS, possibly from the same template) reside on different repositories? How much of a penalty lies there?
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Advice on offsite Backup?
There will be no deduplication among different repositories, since deduplication on target side is done within a restore point.
As to actual penalty, it's impossible to say without running tests.
Thanks.
As to actual penalty, it's impossible to say without running tests.
Thanks.
Who is online
Users browsing this forum: Google [Bot], Semrush [Bot] and 76 guests