02-04-2019 11:24 AM
Plan to apply window updates to our Master/Media server(same box) and will need a reboot after that.
Looking for a properly restart procedure :
stop services
clean bpsched locks
delete bpjobd.act.db......
any info..
thanks.
Solved! Go to Solution.
02-04-2019 12:09 PM
Windows updates are quite straight forward and most probably won't encounter any issue as such. Take a catalog backup before update if you prefer, recommend to take catalog backup to Tape or Basic Disk.
Steps to Stop NetBackup on Media, Master or Master/Media
1. Logon to NetBackup Activity monitor and kill any active running jobs. Wait for jobs to get killed.
2. Inactive all SLP's to start Duplication jobs immediately after restart
3. Close the all the activity monitor Console or any Java console on any of the backup servers
4. Disable Data Collection for OpsCenter to stop the alerts
5. Open command prompt to run the NetBackup command in next steps
6. Shutdown NetBackup on Media servers (bpdown -v -f)
7. Let the NetBackup stop completely on the media servers, use bpps -s command to see if any service or process is running
8. Shutdown NetBackup on Master Server (bpdown -v -f)
9. Use bpps -s to make sure no Backup related processes are running on either Media server or Master Server
10. Try run bpdown -v -f couple of time if you see certain processes still running after executing bpps -s
12. Sometime processes may take some time to shutdown, wait for 2-3 minutes
02-04-2019 12:09 PM
Windows updates are quite straight forward and most probably won't encounter any issue as such. Take a catalog backup before update if you prefer, recommend to take catalog backup to Tape or Basic Disk.
Steps to Stop NetBackup on Media, Master or Master/Media
1. Logon to NetBackup Activity monitor and kill any active running jobs. Wait for jobs to get killed.
2. Inactive all SLP's to start Duplication jobs immediately after restart
3. Close the all the activity monitor Console or any Java console on any of the backup servers
4. Disable Data Collection for OpsCenter to stop the alerts
5. Open command prompt to run the NetBackup command in next steps
6. Shutdown NetBackup on Media servers (bpdown -v -f)
7. Let the NetBackup stop completely on the media servers, use bpps -s command to see if any service or process is running
8. Shutdown NetBackup on Master Server (bpdown -v -f)
9. Use bpps -s to make sure no Backup related processes are running on either Media server or Master Server
10. Try run bpdown -v -f couple of time if you see certain processes still running after executing bpps -s
12. Sometime processes may take some time to shutdown, wait for 2-3 minutes
02-04-2019 12:13 PM
NetBackup will automatically start after the Windows Update Reboot so I havn't added that step. But if you are doing NetBackup recycle without reboot - after following steps in above comment you can follow below steps.
Starting NetBacup (On Reboot it will start Automatically)
1. Start the NetBackup on master (bpup -v -f)
2. Once you see NetBackup starting on Master server start the NetBackup on rest all of the Media servers (bpup -v -f)
3. Logon to the console after couple of minutes, the CPU utilization goes high during NetBackup start on cmsbck01.
4. Kill if you see any job in waiting state
5. Use "C:\Program Files\Veritas\Volmgr\bin\vmoprcmd -devmon hs" command to check the overall status of Media servers
6. Make sure you see backup starts completing
7. Activate ALL SLP's to start the Duplication Jobs
8. Enable Opscenter Data Collection
Note: Path for the bpdown and bp is "C:\Program Files\Veritas\Netbackup\bin"
02-05-2019 12:18 AM
Why do want to do this?
clean bpsched locks
delete bpjobd.act.db......
I have never seen or experienced the need for these steps.
02-05-2019 08:29 AM
I did some googling and someone suggest do those steps.....