How to avoid tape drives showing as DOWN, or Device Path Missing in NetBackup (in a Windows environment) after a Media Server/s reboot.

How to avoid tape drives showing as DOWN, or Device Path Missing in NetBackup (in a Windows environment) after a Media Server/s reboot.

Article: 100002002
Last Published: 2020-04-01
Ratings: 7 5
Product(s): NetBackup

Problem

How to avoid tape drives showing as DOWN, or Device Path Missing in NetBackup (in a Windows environment) after a Media Server/s reboot.

Error Message

How to avoid tape drives showing as DOWN or Device Path Missing in NetBackup in a Windows environment after a Media Server(s) reboot.

Solution

Any changes made to devices or switches through which devices are connected require the following steps to be done to establish proper connectivity.

MASTER SERVER:
 
  • Suspend NB Scheduling by running:  ....\Veritas\netbackup\bin\admincmd\nbpemreq -suspend_scheduling
  • Suspend User initiated backups by running:   ...\Veritas\netbackup\bin\admincmd\bprdreq -terminate

Reference:-       How to prevent backup jobs from starting while running job complete so that maintenance can occur once all jobs have completed? 
                          https://www.veritas.com/support/en_US/article.000038919



MEDIA SERVER:
  • Confirm from the Operating System perspective that the devices are being presented properly. Use the Windows Device Manager.
  • Delete phantom Devices

Reference:-       DOCUMENTATION: How to delete "ghost" or "phantom" devices from the Windows Device Manager when using Veritas NetBackup (tm) 
                          https://www.veritas.com/docs/000042456




ON SAN SWITCHES:
  • Confirm that the switch is able to see the devices connected to it properly.
  • A switch reboot is best option. If switch reboot is not possible, disabling and enabling the ports on the switch allows a re-scan to find the devices connected.


MEDIA SERVERS:
 
  • Confirm that the robot(s) and tape drives are visible from the NetBackup perspective for each Media Server by running the following commands
Windows

Install_Location\Veritas\volmgr\bin\scan -tape 

Install_Location\Veritas\volmgr\bin\tpautoconf -t 

Install_Location\Veritas\volmgr\bin\scan -changer 

Install_Location\Veritas\volmgr\bin\tpautoconf -r

 Linux

/usr/openv/volmgr/scan -tape

/usr/openv/volmgr/tpautoconf -t

/usr/openv/volmgr/scan -changer

/usr/openv/volmgr/tpautoconf -r 

 
MASTER SERVER:
 
  • Reset all NBRB allocations in NetBackup (from Master Sever) by running:  ..\Veritas\netbackup\bin\admincmd\nbrbutil -resetAll

( Note: nbrbutil -resetall, is going to cancel all the existing allocations for all the running and if there is any active job it will fail. Check if there are multiple tape libraries and media servers with this Master, as running the command will affect active backups from other tape libraries. Hence, take all necessary precaution like, running the command when no backups are running or let the active backups complete)



LOCALLY ON THE MEDIA SERVER OR FROM THE MASTER SERVER:
 
  • Gather a list of configured drives by running on the media server:  ...\Veritas\volmgr\bin\tpconfig -d
  • For each drive marked DOWN manually UP the drive by running the following on the media server:  ...\veritas\volmgr\bin\vmoprcmd -up <drive Index>
  • Or use this command to UP the drive from the Master Server :  ...\veritas\volmgr\bin\vmoprcmd -up <drive Index> -h <MEDIA-SERVER-HOSTNAME>

Note: The <drive Index> is the first column in the 'tpconfig -d' output.



ON THE MASTER SERVER:
 
  • Run the device configuration wizard to confirm devices are configured properly.
  • Perform a robot inventory update on all configured robots.
  • Resume NB Scheduling by running :  ...\veritas\netbackup\bin\admincmd\nbpemreq -resume_scheduling
  • Resume User initiated jobs by running:  ...\veritas\netbackup\bin\initbprd

Reference:-       How to prevent backup jobs from starting while running job complete so that maintenance can occur once all jobs have completed? 
                        https://www.veritas.com/docs/000038919
 

 

Was this content helpful?