Symantec Backup Exec 2012 - Tape policy
Created: 16 Jun 2012 | Updated: 27 Jul 2012 | 10 comments
This issue has been solved. See solution.
Hello,
How i can create backup policy for tape driecty like Backup exec 2010 and how i can create b2k like be 2010
Thanks
Discussion Filed Under:
Comments 10 Comments • Jump to latest comment
Hi Omar,
You create a selection list first.
Then go to Job Setup, and look down the left side of the screen...there is an option to create a policy there (don't choose the wizard option!). Click that, and follow the prompts.
It will ask you for the name of the policy, days to run them as well as times, and it will automatically set up the rules as well so that the jobs don't clash.
Check the link below if you get stuck...
http://astolstechblog.blogspot.com/2010/10/create-...
Thanks!
If you find this is a solution, please mark it as such.
Hello,
Sorry man i mean Backup Exec 2012
Omar A. G. Dweik
Qatar - Doha
I guess he is asking how to do it on BE 2012.
BE2012 is a different animal. I haven't found any "policies" in there as it is server oriented. Each server contains their own jobs, unles you create a group (I haven't experienced with it although).
mmm...in that case, check below which is taken from the TN listed below it:
4. Backup Job creation
a. Backup Job Policies - While there is no longer a “Policy” container for Job Definitions per se, the Job Definition essentially serves the same function, but is created in a more automated fashion.
http://www.symantec.com/business/support/index?pag...
Omar: I recommended you read the Admin Guide on more than a couple of times using BE 2010, and I SERIOUSLY recommend you do this with BE 2012. Like the poster above me stated, BE 2012 is vastly different to any other version, and if you don't become familiar with it, you're going to dig yourself into a very big hole.
http://www.symantec.com/business/support/index?pag...
If you find this is a solution, please mark it as such.
Craig,
I understand that BE2012 does create policies in a more automated way (but in a more server oriented sense). I can't find how to apply policy rules...or does it only depend on the job schedule config?. How about if I want to create a GFS job?
On the other hand, how does BE2012 manage multiple concurrent backup jobs to a single tape drive (or a storage with just 1 concurrent job enabled)?. I couldn't find the priority tab which existed previously on the 2012. I will read again the Admin manual, too...however english is not my primary language, so I'll try my best.
Thanks,
Marco
Regarding GFS and automatic policy rules...
BE 2012 follows automatically configures the policy rules based on the following,
Following is an example to configure a GFS type of job family,
In response to this, BE 2012 automatically sets the supersede releationships where, on last Friday of the month, Monthly Full runs superseding weekly full and daily incremental whenever the start time conflicts. On any other Friday of the month except last, Weekly Full runs superseding the Daily Incremental task. For all other remaining days, the incremental task runs.
Thanks,
Mandar
What happens if the superseeding task is put on hold ?
ie: the weekly that should superseeds the daily is put on hold. what happens then ?
I have such a case and it seems BE2012 ignores the hold status and superseeds my incr daily with a monthly task which is on hold ! So nothing runs during that monthly scheduled time window.
And more : even run now will not start the job !
Is this a bug or a feature ?
This is how it worked in previous releases of BE as well, i.e. BE 2010 R2 or earlier. If a top level job in precedence hierarchy is on hold, the lower level jobs are not allowed to run.
I would like to understand your scenario of putting the higher level (superseding) jobs on hold. Appreciate your inputs.
Regards,
Mandar
The reason for holding high level jobs is that the customer has not enough tapes in the library to run weekly and monthly jobs. So we hold them until tapes are delivered. And only the daily full + incr are let to run.
I don’t want to delete these jobs, just to prevent them to run until conditions are ok. But as you say it seems to also hold lower level jobs.
now that this condition has triggered (high level jobs that could run put on hold) the scheduler is completely hung. no jobs will run even newly created ones, and unholding all jobs seems to do nothing.
I have opened a case for all this.
Thanks for sharing the scenario. We will have a discussion on the same.
Regards,
Mandar
Would you like to reply?
Login or Register to post your comment.