If you have backup schedules stepping on each other, you might try this...
I run the nbpemreq -predict_all command at midnight and have my operations 
staff check off the backups as they run. Now you have a paper trail for audits 
as well...

Run from cron at 00:00, use command nbpemreq -predict_all -date `date +%d/%m/%Y`


Date: Fri, 25 May 2012 20:28:10 +0530
From: nbuser <nbuser AT live DOT com>
Subject: Re: [Veritas-bu] Alert! Backups might not be triggering!!!!
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Message-ID: <BLU0-SMTP115864AAF658189D498A219BE010 AT phx DOT gbl>
Content-Type: text/plain; charset="iso-8859-1"

I am giving a scenario where monthly and yearly backups run on every First
Sunday of the month. What you can do is write a script which will run every
monday morning and which will check backups for that particular client
which ran in last 24 hours. If it doesn't find the yearly schedule it will
send a mail to the user with the warning.

On Fri, May 25, 2012 at 7:11 PM, reddi72 <nbu-forum AT backupcentral DOT 
com>wrote:

> Thanks for all the responses!!! Currently , i am not looking at how to get
> around this ,But, How to catch such situations proactively and  get alerted
> ?
>
> +----------------------------------------------------------------------
> |This was sent by smithareddy36 AT hotmail 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