Hi Randy,

Yes, the problem is there in v6.5.2A as well. The 'A' version just stops a full 
backup being run after the upgrade, even if only an incremental is scheduled. 
6.5.2 has changed the way Calendar based scheduling works. It is due to go back 
to 'normal' in v6.5.3 (due in Q4 '08 but not here yet...).

So if you have calendar based scheduling with a window that crosses the 
midnight boundary, expect to see 196 errors turn up. Frequency-based scheduling 
isn't affected. You can get around the 196 errors by enabling 'Retries allowed 
after runday' in your schedules but this just means your jobs restart after 
they've failed at 00:00:00am. It's not an elegant fix. Another option is to 
amend your jobs so only some start before midnight (enough to have all of them 
running and un-queued by midnight) with the rest starting afterwards.

Cheers,

Simon.

+----------------------------------------------------------------------
|This was sent by simon.caudwell AT lloyds DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu