196 "Backup Window Closed" when end of calendar week is hit

[jpriddy]

I am running NBU 7.0 on Windows 2008 R2.  I have several backup policies that have a calendar schedule to kick off a Full Backup on Fridays.  I have set my backup window to Friday 6:00 PM, All of Saturday, All of Sunday, and end at 6:00AM Monday. 

Every weekend, any backups that do not start before 12:00:00 AM Sunday generate error 196.  Is there a way to make the backup window "wrap" or something?  To treat Saturday and the following Sunday as contiguous so the my jobs aren't failing to start within my intended window?

Thanks.

[Andy_Welburn]

(sorry but I always get confused with that!)

I presume the window that's open on the Monday morning is a part of the overall window & not just a "standalone" 6 hours?

***EDIT***

Could you maybe supply the output from:

bppllist policy_name -U

***EDIT***

Re-reading your post: "To treat Saturday and the following Sunday as contiguous so the my jobs aren't failing to start within my intended window?"

Then YES:

Yes:

[jpriddy]

Hi Andy,

It's just like in the attachment that I posted in the first post.  When I created the window, I started at Friday 6:00PM and dragged the mouse to the bottom corner all the way to the end of the day on Saturday.  Then I clicked the mouse on Monday 6:00 AM, and dragged the corner all the way to the top left of the window, Sunday 12:00AM.  I didn't know of another way to create this window... since I did it in two separate steps, does that mean they are separate "standalone" windows like you spoke of? 

I'll post a bpplist in a few.

Thanks.

[Andy_Welburn]

Just drag your cursor from 6pm Friday to 6am Monday & see what happens!

Doing it your way did create two windows & you've seen the result of that with the 196 errors.

***EDIT***

Forget the bppllist output - it will just confirm the two windows.

[jpriddy · Accepted solution]

My bpplist output originally looked like this for my weekly schedule:

  Schedule:          Weekly-Full
   Type:            Full Backup
   Maximum MPX:     1
   Synthetic:       0
   PFI Recovery:    0
   Retention Level: 3 (1 month)
   Number Copies:   1
   Fail on Error:   0
   Residence:       (specific storage unit not required)
   Volume Pool:     (same as policy volume pool)
   Server Group:    (same as specified for policy)
   Calendar sched: Enabled
     SPECIFIC DATE 0 - 07/06/2010
     Friday, Week 1
     Friday, Week 2
     Friday, Week 3
     Friday, Week 4
     Friday, Week 5
   Residence is Storage Lifecycle Policy:     0
   Daily Windows:
         Sunday     00:00:00  -->  Sunday     24:00:00
         Monday     00:00:00  -->  Monday     06:00:00
         Friday     18:00:00  -->  Friday     24:00:00
         Saturday   00:00:00  -->  Saturday   24:00:00 

When I used the Duration fields to extend the window instead of the mouse I noticed the "daily window" changed to a single contiguous window:

  Schedule:          Weekly-Full
   Type:            Full Backup
   Maximum MPX:     1
   Synthetic:       0
   PFI Recovery:    0
   Retention Level: 3 (1 month)
   Number Copies:   1
   Fail on Error:   0
   Residence:       (specific storage unit not required)
   Volume Pool:     (same as policy volume pool)
   Server Group:    (same as specified for policy)
   Calendar sched: Enabled
     SPECIFIC DATE 0 - 07/06/2010
     Friday, Week 1
     Friday, Week 2
     Friday, Week 3
     Friday, Week 4
     Friday, Week 5
   Residence is Storage Lifecycle Policy:     0
   Daily Windows:
         Friday     18:00:00  -->  Monday     06:00:00 

So the BOTTOM result for my window is how NetBackup must see it, in order to stop my 196 errors (assuming that the backups actually start before 6:00AM Monday as I expect)?  If so, that's a pretty simple fix...

Thanks.

[jpriddy]

Now I see you EDITs to your previous post.  I'll update my schedules accordingly and post the results.

[Andy_Welburn]

One large window of 60hours instead of what looks like four windows originally.

I take it these are some hefty backups?

[Zahid_Haseeb]

I think 196 errors mean that backup jobs were not able to START within the backup window that you specified in your backup policy. you try to fixed you schedule backup window

[jpriddy]

I'm backing up about 110 VM's, a large SQL cluster, Enterprise Vault, a file server and a few other physical servers.  Usually runs 36-48 hours.

[Zahid_Haseeb]

You try to increase the time window of backup OR i request you to fix the already time window for backup