08-13-2009 07:53 AM
I used to be able to specify "bpconfig -tries 0" which stops all scheduled backups (in 5.1), jobs near completion (while tries are set to 0) will allow the library (robot) to remove the media from the drive and into its perspective slot in the library. Now, with 6.5.3, utilizing "nbpemreq -suspend_scheduling" stops scheduled jobs but also halts the library from completing its task (eg. setting media back to its slot when pending job(s) finally completes while in "nbpemreq -suspend_scheduling" mode). When I see that the backup job is complete through my Activity Monitor, I click on my Device Monitor and realize that the robot has NOT emptied the drive(s). What i have to do is set "nbpemreq -resume_scheduling". With this said, I will not be able to maintain the library because other jobs just kicked off and forces me to "Cancel" the jobs. Needles to say, its somewhat inconvenient.
My co-worker is also experiencing the inconvenience of having to do a manaul catalog backup while in "nbpemreq -suspend_scheduling". He has to "nbpemreq -resume_scheduling" in order to kick off a "manual" catalog backup. there is not much documented in the "NetBackup Commands Unix and Linux.pdf" file.
What command(s) can we use to mimic what we did when using bpconfig -tries 0?
Solved! Go to Solution.
08-20-2009 01:27 PM
08-13-2009 08:19 AM
08-13-2009 08:52 AM
08-13-2009 02:36 PM
08-14-2009 06:20 AM
08-17-2009 12:37 PM
08-20-2009 10:41 AM
08-20-2009 10:57 AM
08-20-2009 01:01 PM
08-20-2009 01:27 PM