Forum Discussion
You don't need to create different jobs, you can run multiple stages in the same job, and add offsite stages to your backup stages.
My backup plan is the same as yours, except I duplicate my incr jobs offsite as well. My current job looks like this:
Source server -
- Full Weekly - 1st and 3rd Saturday (or 2nd and 4th, but weekly works)
- Verify as separate job on completion
- Duplicate to offite storage on completion (while verify runs)
- Incremental daily - Weekdays
- Verify as separate job on completeion
- Duplicate to offsite Storage on completion (while verify runs)
- Quarterly backup to tape
- Duplicate from most recent backup to long term storage vault
Every one of my source servers has the same setup.
I've found a great key to running many jobs at the same time is to break out the verification job as a separate chained job instead of as part of the backup, that way you can save a lot of time pushing your duplicate.
Having multiple Jobs against a source server is rather redundant unless you need to do something like back a single service instance up (ADDS, sql) and even then it might not be worthwhile to have a separate job.
Also, BIG NOTE: Backup Exec will report the live data set size in the console NOT the backup set size, you will have to view the job history or run a deduplication report against the server to see the actual amount of data sent to the server.
Related Content
- 10 months ago
- 10 years ago
- 10 years ago
- 14 years ago