Forum Discussion
Nicolai
7 months agoModerator
hi etmsreec
Put VERBOSE = 5 in bp.conf and restart Netbackup. This will increase the debugging level of bpsched and maybe explain why a previous bpsched is still examine the NBU policies.
Check for :
- any zombie processes
- use /usr/openv/netbackup/bin/bp.kill_all to stop all Netbackup processes and check with bpps -a they are ALL gone. Kill -9 on the NBU process that doesn't die.
- host names with non ASCII names or hostnames with a extra dot e.g srv1.acme. <-- dot in the end of host name.
- davidmoline7 months agoLevel 6
Hi etmsreec
In addition to the suggestions from Nicolai have a look for stale lock files.
These will most likely be in the /usr/openv/netbackup/bin directory and for bpsched the lock file may be bpsched.lock or bpsched.lck. Shutdown NetBackup before removing any lock files.
The final step would be to reboot the server to ensure there are no zombie processes etc. as per Nicolai .
Cheers
David- Nicolai7 months agoModerator
bpsched.lock or bpsched.lck - good memory davidmoline
I had a faint memory of lock files, but time had erased the name of the files in my memory :)
Related Content
- 2 years ago
- 3 months ago
- 4 years ago
- 11 years ago
- 2 months ago