thats called user backups.

I do a lot of those - job kicks of and does something on the server - when that something is done the job kicks off a user backup.

only problem is you cannot "see" what you have schdeuled unless you look at the contents of the jobs.

User backups are initiated on the individual servers.  For example, our DBA's kick off their own backups and restores.  What I am talking about are manual backups initiated on and by the Master Server - executing the policies you have defined without using NetBackup's scheduler.

It will work fine if you have one or two jobs. But when you have multiple policies it becomes hard to define when to run a Full and when to run a diff for given policy. It will become more complicated when you have schedules runnin on specific day of monht e.g. last sunday of every month etc.

You cleanup jobs may not run the way it should be since there is no schedule . 

Other than these I don't see any issue why it will not work.

Using bpbackup, you specify the policy and schedule to execute.  Just stack a bunch of "bpbackup" in a command file and let it rip.  However, you make a very good point about running on a specific day....

My issue is that I need to have Calendar based scheduling, not Frequency based.  Prior threads have talked about this.  Our backup windows do cross the 00:00 mark - even for our daily's and the "corrected" behaviour under NBU 6.5.2 is not acceptable.  Maybe using a Calendar based policy to kick off a manual backup would take care of this matter.  I need to look at some of the exits provided and see how to utilize this.