This is actually something which happens to me quite regularly so i 
believe symantec need to take notice of it.

My case is slightly different in that i have a number of policies for 
different SSO Media servers.

Out of the blue one of the policies does just not schedule to run yet no 
change has been made to it.

A manual backup works fine yet still no scheduled backup works.

The only way i have been able to get around it is this :-

Copy the policy to a new name
Delete the old policy
Copy the new name policy back to the original name
Delete the new name policy.

I'd like to know why this happens too as as you say its not picked up in 
the activity monitor.

I have it on my list to check that my report script has a known list of 
clients and to alert if any of them are not present in the daily report. 
This i have not yet gotten around to doing though.

Cheers


Tageson, Jim wrote:
>
> We uncovered a situation recently where some client backups in 
> scheduled policies were not running at all. These clients were in 
> active policies with several other clients which were running just 
> fine. We discovered a total of 4 clients in 2 policies which were just 
> not running their backups at all. Other clients in these 2 policies 
> were being scheduled as expected. We went for 19 days without backups 
> running on these 4 clients. Since they never were scheduled, there 
> were obviously no errors in Netbackup at all and we didn’t know we had 
> a problem until someone requested a restore and we saw no backups had 
> run. We opened a ticket with Symantec and they have escalated it to 
> the highest level. The problem was finally resolved by a recycle of 
> the Netbackup daemons, but no cause has been determined due to lack of 
> log files during the time of the problem.
>
> Symantec believes the policies somehow got corrupted and they believe 
> this is an isolated issue and probably will not occur again. However 
> if you are not monitoring to see if all your scheduled backups are 
> actually running, you will never know you have a problem.
>
> This is just to alert other users of this issue and to urge them to 
> make sure that this is not a widespread problem.
>
> We are currently running Netbackup 6.0MP6 on an AIX master server.
>
> **Jim Tageson**
>
> **Netbackup Administrator**
>
> **BayCare Health System**
>
> Phone: 727-467-4586
>
> E-mail: james.tageson AT baycare DOT org <mailto:james.tageson AT baycare DOT 
> org>
>
> Confidential:  This electronic message and all contents contain information
> from BayCare Health System which may be privileged, confidential or otherwise
> protected from disclosure.  The information is intended to be for the 
> addressee
> only.  If you are not the addressee, any disclosure, copy, distribution or use
> of the contents of this message is prohibited.  If you have received this
> electronic message in error, please notify the sender and destroy the original
> message and all copies.
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>   

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