06-15-2012 12:37 PM
We have a backup rotation where the months that have a 5th Friday use a "Week 5" backup job and get written to a "Week5" backup-to-disk folder. I cannot find an option to manually select dates in one backup job like I have been able to do in versions prior to 2012. Is the solution to create seperate jobs ?
thanks
06-15-2012 07:40 PM
I just want to fully understand how you used 'specific dates' to achieve 5th week scheduling in prior versions of BE. My interpretation is that, you would anyways have had to configure a policy with two backup tasks such that,
Please confirm if this understanding is correct.
Thanks,
Mandar
06-16-2012 12:53 PM
Thanks for the reply..
You are pretty close, we would actually schedule one job per storage location. So we would have a Week2 job that would run everyone 2nd Friday of each month to a Week2 backup-to-disk folder and then the next month it would be overwritten and the same for Week3, and Week4. Week5 is the oddball since only some months have a 5th Friday in them but I was still able to create one job and one storage location and have the job run on the specific 5th fridays as I would set it up for the next couple of years at a time.
As an example of Week5 job and Week5 storage , in backup exec 2010 I could select run on; 6/29/12, 8/31/12, 11/30/12, 3/29/13 etc..
What it appears I need to do in 2012 version is to create an independent backup job (i could still reuse same storage location) for each 5th friday?
If this is the case, it is not a big deal, i just want to validate i am recreating my backup schedule properly, but the other thing was when i upgraded from 2010 to 2012 it didnt transfer the 5th Friday date properly but turned it into a recurring date of every 76 days which was wrong. So maybe this issue is a bit of a bug with the upgrade process and possibly a feature request for future version/patch.
thanks
06-16-2012 10:23 PM
Thank you for sharing the details. To address your two questions,
I have already circulated the scenarios that you have mentioned within our team. Thanks once again!
Regards,
Mandar