Setting a new policy schedule for a user to kick off

[JayKoonz]

NetBackup 4.5 fp7 - Windows master server - unix clients
I have an exsisting policy with the normal full and incremental schedules. The user wants the capability to setup an additional schedule, with a different retention, that can only be run on Sun from 3am to 5am, and only if they want to run it, and including a different set of files each time.
If I add an new schedule to a policy with the right retention-period and start-window, it would then kick off every Sunday at 3 am. Not what I want.
Looks like you can only disable an entire policy, not just a schedule within that policy. Not what I want either.
The user wants to kick off the policy using something like "bpbackup -w -p xxxxx-Unix -s newsched filename" so each backup will contain a different set of files to be backed up.
The user has a need to do this to get the latest stuff backed up in preparation for some system/application changes. But I can't see how I can do it in an exsisting policy. And if I setup a new policy, I'll have the same problem with it running every week as a full backup since there won't be default filelist on the command.
My current thinking is setup a new policy, with a Sunday morning only schedule. Write a script for the user that will run something like "bpbackup -w -s newname -f filelist". The script will check to see if a file called filerlist exsists and if not, pull in a default filelist file that I'll have hidden somewhere. But I'm not thrilled with that solution.
Any thoughts on how I can do this ??

 

[lenski]

You need to create a new policy which is user type. The policy is the same as the original apart from the schedule page which 'Type of Backup' is User Backup. This is left active but will only run when requested by the user i.e. manual sumbition even when the window is open. The window can be as you wish so the user may only submit in that time. You do however have to make config changes to netback to allow User Backup and at the moment I can't remember what they are because as a rule I hate giving users any power. They would then open the limited GUI on the client and select the files and submit their job.