Comprehensive data protection for all workloads
Post Reply
mbaker33
Novice
Posts: 8
Liked: never
Joined: Jun 06, 2013 2:04 pm
Full Name: Mark Baker
Contact:

Scheduling Backup Copy Jobs

Post by mbaker33 »

Hello All,

I've done the research, I just can't get to the bottom of this particular problem.

What we are looking for is for the Backup Copy job to copy the job data off site as soon as it finishes. Instead, what seems to happen is, as soon as the schedule starts, it attempts to copy the data that is already in place. We also don't want to do the job copy starting at 8am (after all jobs are completed) since our SAN will be replicating off site during the day and there isn't enough room on the pipe for the added backup sync. I'm sure it's something super easy, I just can't get the timing right. We also can't figure out if all we need to do is disable the job, and configure a second backup location to make this work properly. Nothing we've tried has given us our desired end result. It seems like this should be a much easier process to accomplish than it has turned out to be.

Any input would be appreciated.

Thank you,

Mark
Shestakov
Veteran
Posts: 7328
Liked: 781 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: Scheduling Backup Copy Jobs

Post by Shestakov »

Hello Mark, let`s try to make it simple.
mbaker33 wrote:What we are looking for is for the Backup Copy job to copy the job data off site as soon as it finishes.
If you know when your backup job finishes approximately, you can schedule the job to run in a particular time of the day.
Another option is to set backup copy job run as a post-job activity for the source backup job, so it will start as soon as the source job finishes.
mbaker33 wrote:Instead, what seems to happen is, as soon as the schedule starts, it attempts to copy the data that is already in place.
When backup copy job starts VBR accesses VM backup files in the source repository, retrieves data blocks for a specific VM from the backup file, copies them to the target repository and composes copied blocks into a backup file in the target backup repository. Note that first run of the job creates Full backup file, at every next synchronization interval VBR writes the copied data blocks into the incremental backup file.
mbaker33 wrote:We also don't want to do the job copy starting at 8am (after all jobs are completed) since our SAN will be replicating off site during the day and there isn't enough room on the pipe for the added backup sync.
For that purposes, specify backup copy window when the backup copy job must not transport data over the network.
mbaker33 wrote:We also can't figure out if all we need to do is disable the job, and configure a second backup location to make this work properly.
Backup copy job makes more sense, because the backup copying process does not affect virtual infrastructure resources, does not require an additional snapshot of a VM and does not produce any load on VMs whose backups are copied. Also, WAN acceleration can be use to speed up backup copy job.
Thanks.
Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot], Mehl and 301 guests