DOCUMENTATION: What is the process for decommissioning a NetBackup 6.5 or 7.x media server?

Article:TECH62119  |  Created: 2010-01-24  |  Updated: 2013-04-16  |  Article URL http://www.symantec.com/docs/TECH62119
Article Type
Technical Solution


Issue



DOCUMENTATION: What is the process for decommissioning a NetBackup 6.5 or 7.x media server?


Solution



In NetBackup 6.5.3 or higher environments, the preferred method for decommissioning a media server is nbdecommission, the Media Server Decommission Wizard.  This wizard can be downloaded for versions 6.5.3, 6.5.4, 6.5.5 and 7.0 by following the appropriate link in the Related Articles section below.

Note: The nbdecommission command is included in the NetBackup 6.5.6 and 7.0.1 release updates as well as in NetBackup 7.1 GA and above and is documented in the Symantec NetBackup Commands Reference Guide. No separate download is needed.

Decommissioning and removing a media server from a NetBackup configuration manually requires several steps. If devices attached to the media server contain NetBackup media, move the media to a new media server. If the media is no longer usable or valid, delete it from the NetBackup configuration.

If not using nbdecommission, the following procedure can be used to decommission a server (the <old_server>) and move its media to a new media server (the <new_server>). If this procedure is not performed and a subsequent restore requires media that is associated with the old media server, the media must be imported. Importing media consumes more time than the following procedure.

To decommission a media server

Note: All commands referenced below can be found in the following directories:

UNIX: /opt/openv/netbackup/bin/admincmd
Windows: <install_path>\VERITAS\NetBackup\bin\admincmd

1. Run the bpmedialist command to determine which tapes on <old_server> contain NetBackup images that have not expired. The -l option produces one line of output per tape.  
 bpmedialist -mlist -l -h <old_server>

2. Use the NetBackup Administration Console to move the tapes in the robots that are attached to <old_server> to non-robotic status (standalone).  Select each robot that is attached to <old_server>. Select all of the tapes and move them to standalone (select Actions > Move).

3. Choose another server or the master server to manage the tapes from the decommissioned server.  Logically move the media from <old_server> to <new_server>, as follows: 
 
If both <old_server> and <new_server> are at NetBackup 6.0MP7 or later, or NetBackup 6.5.2 or later, run the following command:
 
bpmedia -movedb -allvolumes -oldserver <old_server> -newserver <new_server>
 
Note: This command modifies the NetBackup image database and the media server entry in the header files of all the backups taken by <old_server> is replaced with a <new_server> entry.

E.g.

Header file example     
 
  # FRAG: c# f# K rem mt den fn id/path host bs off md dwo f_flags f_unused1 exp mpx rl chkpt rsm_nbr seq_no media_subtype keep_date copy_date i_unused1
FRAGMENT 1 1 890 0 0 0 0 C:\backup\windows_client_1320927029_C1_F1 windowsmaster 262144 0 0 -1 0 windowsmaster 1322136629 0 65537 0 0 0 1 0 1320927040 0
BACKUP_ID windows_client_1320927029    

Note :This is the location where the images reside C:\backup   ,In order to restore the backups move the images to same location on new media server. The operating system should the same ,so that the path could be accessed.

Now if this command is executed    

C:\Program Files\Veritas\NetBackup\bin\admincmd>bpmedia -movedb -allvolumes -oldserver windowsmaster -newserver linuxmedia         

The header file looks like this 

# FRAG: c# f# K rem mt den fn id/path host bs off md dwo f_flags f_unused1 exp mpx rl chkpt rsm_nbr seq_no media_subtype keep_date copy_date i_unused1
FRAGMENT 1 1 890 0 0 0 0 C:\backup\windows_client_1320927029_C1_F1 linuxmedia 262144 0 0 -1 0 windowsmaster 1322136629 0 65537 0 0 0 1 0 1320927040 0
BACKUP_ID windows_client_1320927029
 
 
If <old_server> or <new_server> is at a version earlier than NetBackup 6.0MP7, or NetBackup 6.5.2, run the following command for each volume that has active  images as identified in step 1:
 
 bpmedia -movedb -ev media_ID -oldserver <old_server> -newserver <new_server>
 
Run tpconfig or vmoprcmd afterwards to ensure that nothing remains showing against the old media server.

4. Use the Administration Console to configure NetBackup so that restore requests are directed to <new_server>.  In the General Server host properties of the master server, add a Media Host Override entry that specifies <old_server> for the Original backup server and <new_server> as the Restore server.

5. Use the NetBackup Administration Console  to delete the following in this order: 
  • All storage units that use the robots that are associated with <old_server>.  
  • Drives from <old_server>.  
  • Robots from <old_server>.
  • Note: In case NetBackup is already uninstalled from the media server ,while deleting the devices from the GUI ,we may get an error mentioning the volume manager daemon on that server is not running,In that case run the following command from the Master(EMM) server:
     
    nbemmcmd -deletealldevices -machinename -machinetype media
6. Modify any policies that specify the storage units on <old_server>.  Change the policies to point to any other defined storage units in the NetBackup configuration or to Any Available.  

7. Use the NetBackup Administration Console to remove any reference to the decommissioned media server in the Servers host properties of the master server.  Also, remove references in the Servers host properties of all media servers and all clients.
 
8. Restart the NetBackup daemons or services on any system that was updated.

9. Run nbemmcmd -deletehost -machinename <old_server> -machinetype media to remove reference to the media server from EMM. Run nbemmcmd -listhosts to verify that all references have been removed.  

10. Remove any files named <old_server> found in the remote_versions directory:
UNIX: /opt/openv/netbackup/remote_versions
Windows: <install_path>\VERITAS\NetBackup\Remote_Versions

11. If any robots from <old_server> are reused on other media servers, perform the following actions:
 
Shut down the affected servers and disconnect the robots from the old servers.  Connect the robots to the new media servers.  Verify that the operating systems on the new media servers recognize the robots.  
 
Use the NetBackup Device Configuration Wizard to add the robots and drives to the media servers.  
 
Use the NetBackup Administration Console to create the appropriate NetBackup storage units.
 
Use the NetBackup Administration Console to inventory the robots that are attached to <new_server>.  The inventory updates the location of all tapes in these robots.
 
Note: This document is also applicable to a SAN media server.  A SAN media server is the same as a media server except it only backs up itself and does not backup remote clients.



Legacy ID



306838


Article URL http://www.symantec.com/docs/TECH62119


Terms of use for this information are found in Legal Notices