Video Screencast Help

Large backups spanning

Created: 04 Oct 2012 • Updated: 04 Oct 2012 | 8 comments
This issue has been solved. See solution.

Hey guys, i am running into a bit of trouble with a files server backup.

I have a 5Tb file server, which takes days and days to backup, and normally fails somewhere in between.  This isnt working for me.  I want to be able to split the selection list into smaller chunks, but then i dont want the jobs to be running concurrently and smashing the poor file server disk.

Staggering the backups also doesn't seem to work, as i have tried, doing some on Monday, then some more on wednesday, but i end up with misses, and two or more jobs running and hitting the disk at the same time.

Is there a method i can use where i setup a multiple jobs on the same server but force them to onnly run one after the other has finished?

Comments 8 CommentsJump to latest comment

pkh's picture

You can try chaining your jobs.  See my article below

ajhstn's picture

Hi pkh,

your article on chaining jobs looks interesting, thank you it might be an option.

Will this work with incremental jobs also.  I wish to have something like on Friday start a FULL backup of  1/3rd of the backup set, followed by the next portion, followed by the final portion.  Then on Saturday i want to do an incremental of the first part, then chain the next part, then the final part, then on Sunday repeat the incrementals, then again on Monday, through to Thursday..

ajhstn's picture

Another question..

Would it be better to use One-Time Backups for each of my jobs, and then execute them one after the other with post commands using ps?

Or can they be normal backup jobs?

ajhstn's picture

Im confused what schedule i would create my backup job with, because after the post command releases it from being on hold, wont it then just go into a scheduled state, and wait for its schedule before it starts??

pkh's picture

Since you want to do incremental backups, you would have to define a normal backup job, not a one-time backup.  It does not matter what schedule you put the jobs on.  The important thing is to put them on hold.

When use you the Start-BEJob cmdlet, the jobs are executed immediately.  They will not follow the schedule and they will still remain on hold if they are already placed on hold.

If you had used the Resume-BEjob cmdlet, then the jobs will be released from hold and put on their respective schedule.

ajhstn's picture

Once the cycle of jobs has run through and each job completes, does the job automatically go back to on hold, ready for the the first job to be started again?

pkh's picture

As I said, Start-BEJob does not release the jobs from hold so they will always be on hold until you release them either through the console or using Resume-BEJob.