NetBackup Calendar Based Scheduling for individual dates - is a run window required?
All, I am trying to setup a calendar based schedule that is based on individual run dates to run quarterly backup jobs. The run dates will be populated via a cron job on the master server (Solaris 11) on Jan 1 of every year. The population of the dates works fine but do I also need to set a run window for each date? If so how does one determine which day of the week is appropriate for the selected date (as each run date is on a different day of the week)? Do I need to create run window for every day of the week and preselect them as exclude dates and then have my cron job remove the exclude and add in the include date? Thank you in advance for your answers.Solved971Views0likes2Comments
Calendar Based Schedules - Same Date and Same Start Time - Other Schedules Still Run
Hi all. It's been sooooo long. Anyway, one of our clients has a NetBackup 8.0 environment running, but encountered the following issue. Schedule type is calendar based. They have 3 schedules per policy: 1. Daily - Ticked All Dates in month - Start-End-Window 9:00PM-2AM - SLP-Daily 2. Weekly - Ticked Fridays only - Start-End-Window 9:00PM-2AM - SLP-Weekly 3. Monthly - Ticked 1st of each month - Start-End-Window 9:00PM-2AM - SLP-Monthly The way I understand this priority system is, that the least frequent schedule wins whenever two or more schedules are due to run on the same day and with the same start time. What actually ends up happening is that, on each Friday, Weekly would run first, but if the jobs complete before 2AM, the Daily schedule would also start its jobs. In a way this makes sense because anytime before 2AM still falls within Daily's window. Similar things happen to Monthly schedules. On the 1st of every month, the Monthly schedule would run first, and if it finishes before 2AM, the Weekly would also start if it is a Friday. THEN, if it also finishes before 2AM, the Daily also starts next! 3 backups in 1 night, crazy. Clearly, we don't want more than one schedules to run on the same night! So I'm just reaching out here for your suggestions. I could only think of two half-solutions atm: Shorten the Start-End-Window from 5 hours to something like 1-2 hour: 9:00PM-10:00PM for all schedules, so that the next schedule waiting to start would unlikely have any backup window left to actually start. (This is not ideal because the guesswork makes this not always 100% accurate, plus there is actually a need for longer backup windows) Give up the Calendar type and use the Frequency schedule type. (Not ideal either because you can't select the 1st of each month that uses a special Monthly SLP.) Sooooo, any ideas on how to optimize this guys? Thanks all! RLeonSolved3.2KViews0likes6Comments