Video Screencast Help

Ability to not allow ANY backup jobs to start AND make persistent

Created: 03 Mar 2011 | 4 comments
bcblake's picture
1 Agree
1 Disagree
0 2 Votes
Login to vote

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) try to get a NetBackup to be completely idle, without having to shutdown processes.

Problems are:

- 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.

Comments 4 CommentsJump to latest comment

David McMullin's picture

I use this script on unix to deactivate ALL my policies, then another just like it to read the output and reactivate them...

# cat
# get list of active policies and save to file
# Look at the 12th field of your output.
# This will be a 1 if it is inactive and a 0 if it is active.
# bppllist POLICY -l|grep INFO | awk '{print $12}'
# step 1 - move active list!
mv /var/adm/scripts/active.policies.txt /var/adm/scripts/active.policies.`date +%Y%m%d.%H%M`
# step 2 - for all policies check if active and store name and deactivate
for i in `/usr/openv/netbackup/bin/admincmd/bppllist`
  echo $i
  ACTIVE=`/usr/openv/netbackup/bin/admincmd/bppllist $i -l |grep INFO | awk '{print $12}'`
  if [ $ACTIVE = 1 ]
        echo $POLICY" Policy is already deactivated!"
        echo "Adding policy name to file - "$POLICY
        echo $POLICY  >> /var/adm/scripts/active.policies.txt
        echo " and deactivate if active! "
        /usr/openv/netbackup/bin/admincmd/bpplinfo $i -modify -inactive &

/usr/openv/netbackup/bin/admincmd/nbpemreq -updatepolicies

NBU 7.0.1 on Solaris 10
writing to EMC 4206 VTL
duplicating to LTO5 in SL8500
using ACSLS 7.3.1

Login to vote
Piotrek B's picture

Try to use this one:

#bprdreq -terminate

I think this should omit yours problems

Login to vote
David McMullin's picture

bcblake is looking for somethnig that will remain in place if he stops all netbackup processes and then restarts them...

NBU 7.0.1 on Solaris 10
writing to EMC 4206 VTL
duplicating to LTO5 in SL8500
using ACSLS 7.3.1

Login to vote
Morten Seeberg's picture

Vote for this one, its in review:

Did you restore something today?

Login to vote