Video Screencast Help

Scheduling duplications with Backup Exec 2012 NOT WORKING !!!!

Created: 02 Apr 2013 • Updated: 10 Apr 2013 | 5 comments
Tinus's picture
This issue has been solved. See solution.


In reference to this post:

What PKH says:

"No.  For your proposed backup scheme, on the last Sunday of the month, your monthly backup will run and your weekly backup will be superceeded and not run.  This is because both jobs start at the same time and the monthly job has a less frequent schedule."

This is not true !!!

I have 4 BE3600 R2 appliciances with 2 MSL2024 tapelibraries on 2 sites, where on each site 1 appliance has a tapelibrary attached.

I have configured a job to: backup to disk, duplicate to disk and finally, weekly duplicate to tape with 4 weeks protection, on the last saturday/sunday of the month 12 months protection and the last saturday/sunday of the year permanent protectedion.

This means that I have to schedule 3 duplication stages for the week, month and year tape.

However last saturday/sunday BOTH month and week dupicate run.

So, how to solve this.

It would be better if Symantec puts back the scheduler from BE2010 !!!!!!!!!!


Operating Systems:

Comments 5 CommentsJump to latest comment

Colin Weaver's picture

Please log a formal support case so that we can fully look into your problem

King_Julien's picture

I noted the same behavior last week.

Anyway, I still have to review all the jobs to see if I did something wrong in the configuration because they worked in the past. 

A second of your life, ruined for life.

Tinus's picture

Hi all,

I have spoken with a Symantec Technical guy and he confirms this behavior to be a known problem with the 2012 release.

A fix for this is to be expected at the end of this year.

In the mean time you'll need exclude the schedules that will conflict.

Good luck !


King_Julien's picture

Thanks for the update! 

A second of your life, ruined for life.

pkh's picture

Note that my statement that is quoted in the original post is for the superceding of backup JOBS, not duplicate jobs.  Duplicate job scheduling is not quite the same as normal job scheduling which may result in the problem described.