Ability to not allow ANY backup jobs to start AND make persistent
I would like to suggest a feature enhancement for NetBackup to give us the ability to not allow ANY backup jobs to start.
I've tried all sorts of combinations of the following:
- nbpemreq -suspend_scheduling
- vmoprcmd -h <media-server> -deactivate_host (or better yet, nbemmcmd -updatehost -machinestateop set_admin_pause -machinetype media -machinename <media-server> -master <master-server>)
- bpplinfo <policy> -modify inactive (deactivate all policies)
- bpconfig -tries 0 (which NO LONGER WORKS in NBU 7)
...to try to get a NetBackup to be completely idle, without having to shutdown processes.
- nbpemreq -suspend_scheduling: doesn't stop manual bpbackup or client-directed operations (database extensions, etc.)
- deactivate media server: lose the ability to manipulate tape devices
- deactivate policies: how do I know which policies were SUPPOSED to be deactivated on purpose versus the policies I JUST deactivated to do this maintenance
- bpconfig -tries 0: as mentioned, this ability was TAKEN AWAY
So quite simply, how can we get NetBackup to NOT run any jobs, and ALSO make this PERSISTENT across restarts of processes/daemons? nbpemreq -suspend_scheduling isn't persistent so if you bounce NetBackup, you could easily end up having jobs firing off immediately.
Why do we need this?
- How about patching NetBackup. Processes get restarted, but I don't want anything to run right away once all daemons come back up... I want to make sure everything looks ok (bpimagelist, make sure I can browse for restores, etc.).
- Any type of hardware maintenance (firmware updates to disk appliances, physical tape libraries, etc.).Yes I know I could stop NetBackup on the master and media servers, but what if we have multiple masters and a boatload of media servers?
Thanks for the consideration.