Comprehensive data protection for all workloads
Post Reply
jroesner
Novice
Posts: 6
Liked: never
Joined: May 25, 2011 3:22 pm
Full Name: JRoesner
Location: London, Ontario, Canada
Contact:

Replicate - 1 big job, or 20 small jobs

Post by jroesner »

Is it better to group your vm's into replication cycles, then create a single job for that goup, or is it better to have each vm replicate against its own job?

eg

You want to backup the following servers against the schedules.

Sql - 6 hours
web - 6 hours
FTP - 12 hours
nfs - 12 hours

should you group them into 2 jobs, one for sql/web, and one for ftp/nfs or make 4 jobs?

Thanks

Vitaliy S.
Product Manager
Posts: 24256
Liked: 1863 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Replicate - 1 big job, or 20 small jobs

Post by Vitaliy S. »

Given the specifics of your scenario (different replication schedule and the number of VMs to replicate), I would go with two VMs per job. In this case you would get the desired flexibility in scheduling and more granular control which cannot be achieved while having a single job for all VMs.

jroesner
Novice
Posts: 6
Liked: never
Joined: May 25, 2011 3:22 pm
Full Name: JRoesner
Location: London, Ontario, Canada
Contact:

Re: Replicate - 1 big job, or 20 small jobs

Post by jroesner »

Well, in actuality, there are about 30 vms and about 4 different ranges. But I think the principal holds true.

Vitaliy S.
Product Manager
Posts: 24256
Liked: 1863 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Replicate - 1 big job, or 20 small jobs

Post by Vitaliy S. »

Yes, If I were you I would group your production VMs into multiple replication jobs according to VMs Tier status/desired job schedule etc.

Post Reply

Who is online

Users browsing this forum: Baidu [Spider], Joubert.R and 32 guests