On Wed, Nov 5, 2008 at 7:18 AM, Tageson, Jim <[EMAIL PROTECTED]>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.
>
This is not a new problem and one that pops up regularly. It's absolutely,
positively the most severe issue that NetBackup can have since data is
silently ignored with no warning to the backup admins. We've seen it over
the years with 6.0MP2 being the worst example.
We regularly watch not only for failures but also have cronjobs out there
that check to see if any backups have run for specific clients. For
example, if no database archive logs get backed up, and email is sent out to
the DBAs and backup admins. We occasionally view the Aptare StorageConsole
volume graphs to see if the patterns make sense - this was our original
trigger into the 6.0 issues.
You can never be too careful with your backups...
.../Ed
Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
[EMAIL PROTECTED]
_______________________________________________
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
