Video Screencast Help
Search Video Help Close Back
to help

Media Server Reboot

Created: 13 Nov 2012 | Updated: 07 Dec 2012 | 4 comments
rajesh Talla's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi ,

Our environment has media servers 6.5.6 , cluster  master 7.0.1 , both linux redhat.

We found one of our media server has a ECC:error which  requires a driver installation and our sysadmins are working on this update.

I was told there is good chance of this media server may have to be rebooted , and as a Netbackup admin what precautions should i take on this mediaserver to have netbackup function properly after reboot

I did a research and found netbackup daemons & services has to be stopped before reboot , is this a safe practice , if yes what are the commands to do so.

 also i wanted to check how i can maintain a consistency of media server connectivity with tape library after reboot

currently our media server is connected to an  SL 500 and a Quantum VTL (dedup appliance).

What would be a best approach for me to get through this reboot with respect to netbackup and please provide if there is document for this kind of situations.

Please reach me out if any additional info is required from my side or if i am missing any thing.

Thanks,

Rajesh

Comments 4 CommentsJump to latest comment

Yasuhisa Ishikawa's picture

To stop NetBackup daemons, run "/usr/openv/netbackup/bin/goodies/netbackup stop" on the server.

Then run ""/usr/openv/netbackup/bin/bpps -a" to check running processes.
If some process still remains, stop that by ""/usr/openv/netbackup/bin/goodies/bp.kill_all".

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

0
Login to vote
  • Actions
Yasuhisa Ishikawa's picture

There are nothing to do but keep hardware connectivity and power to keep tape devices on linux.
Run "/usr/openv/volmgr/bin/scan" before and after, and compare outputs. If device files was changes, you need to fix it.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

0
Login to vote
  • Actions
rajesh Talla's picture

Thanks for sharing the info.

As you said i believe "/usr/openv/netbackup/bin/goodies/netbackup start" will start all the daemons again and will it start  the process killed by issuing ""/usr/openv/netbackup/bin/goodies/bp.kill_all" ?

or

What would be the command to start Netbackup up & running.

also ,

If i come across missing  paths to tape drives after reboot by validating through "/usr/openv/volmgr/bin/scan", what should be the next immediate action i am supposed to take ?

should i start with inventory robot , also as a question will "/usr/openv/volmgr/bin/scan" also shows the volumes under the libraries ?

Thanks ,

Rajesh

 

 

0
Login to vote
  • Actions
Yasuhisa Ishikawa's picture

"/usr/openv/netbackup/bin/goodies/netbackup start" will start all the daemons

Yes.
 

If you find missing devices after reboot, you should check hardware connectivity and hardware status. This often caused by mistake in wiring or powering procedure. Before you start to power on your server, you should check if hardware wiring is exactly same as before, and devices have been already online.
After check, try to reboot again.

Or, if you can see all devices but device path was changed, most quick way I prefer is remove devices(or drive path) in NetBackup and run Device Configuration Wizard again.

Please note that scan command displays robot and drives visible on the server. but does'nt volumes in robots. In this scenario, volumes will not be changed. Even if changed, just run inventory and update volume configuration.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

SOLUTION
+1
Login to vote
  • Actions