We are planning to create a offsite backup from our datacenter to another location up north. Currently we break up all our VM's by O/S for the dedup. This was explained as a best practice a few years ago (If this is not best practice let me know). So with that said should we create one backup copy job with all VM's in it or break them up by backup jobs?
If someone could answer or point me in the right direction I would appreciate it...
Thanks,
-
- Novice
- Posts: 9
- Liked: never
- Joined: Oct 28, 2010 4:35 pm
- Full Name: Jbo
- Contact:
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Backup Copy Job - Offsite
Yes, this is still best practice to group similar VMs into the same backup job for better dedupe ratios. As to the backup copy jobs, then you need to group VMs based on the required retention policy settings and RPOs. Do you use WAN accelerators for the backup copy jobs?
-
- Novice
- Posts: 9
- Liked: never
- Joined: Oct 28, 2010 4:35 pm
- Full Name: Jbo
- Contact:
Re: Backup Copy Job - Offsite
I'm in the process of setting up the seed. Yes, I'll be using the WAN accelerator.
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Backup Copy Job - Offsite
Got it, so if you're concerned about data traffic, WAN accelerators is the way to go.
Who is online
Users browsing this forum: No registered users and 30 guests