DOCUMENTATION and DOWNLOAD: How to use Symantec's NetBackup Media Server Decommissioning Tool for NetBackup 7.0

Article:TECH130438  |  Created: 2010-01-24  |  Updated: 2012-05-31  |  Article URL http://www.symantec.com/docs/TECH130438
Article Type
Technical Solution


Environment

Issue



DOCUMENTATION and DOWNLOAD: How to use Symantec's NetBackup Media Server Decommissioning Tool for NetBackup 7.0


Solution



Overview:
The nbdecommission command line tool will be shipped with NetBackup 7.0.1 to guide the user through the steps involved in decommissioning a media server. The utility attached to this document allows this functionality in NetBackup version 7.0.

Decommissioning a media server means removing all the references of a server from the NetBackup domain so that there is no visible or measurable impact on the remaining functional environment.

nbdecommission can also be helpful in situations where a media server has been incorrectly decommissioned and there are still references to the old server.
 
 
Description:
The nbdecommission utility helps the user to view all the references that an old server has and provides help through the decommissioning process. The -list_ref -oldserver hostname option displays all that is associated with the old server, which allows users to break the associations on their own. This option does not decommission the server.

The -oldserver hostname [-newserver hostname] option provides a step-by-step guidance to decommission the old server. You can run the command on the master server or any server that is not decommissioned. The decommissioning process is clean and removes old media server entries in the EMM DB and bp.conf file which can slow down backup operations. The command does not assume that the old server is up and responsive.


Usage:
nbdecommission -oldserver <hostname>
 
[-list_ref | -newserver <hostname> [-file <op_dump_file>]]
 
[-M <hostname>] [-v]
 

Options:
-oldserver <hostname>
Specifies the name of the media server to be decommissioned.

-list_ref
Lists all the references to the media server to be decommissioned.

-newserver <hostname>
Specifies the name of the media server where tape media should be moved before decommissioning the old media server. It is also used as the default new media server (which can be overridden by the user) for moving disk pools.

-file <op_dump_file>
Specifies the name of the operation dump file.  All the operations performed to decommission a media server are logged in this file.

-M <hostname>
Specifies the master server name.

-v
Specifies verbose output.

Example:
In this example, the media server with the hostname clapton is being decommissioned.
 
Recommend running the nbcommission commands on the master server.

1. Execute the nbdecommission -list_ref command to generate the list of references to clapton:
 
# nbdecommission -oldserver clapton -list_ref > /tmp/clapton.references
 

 
2. Examine the output file - in this case, /tmp/clapton.references - to make sure that the command has captured everything.  
 

 
3. If you are satisfied with the results, run nbdecommission to decommission the server and, optionally, log the output to a file:
 
# nbdecommission -oldserver clapton -file /tmp/clapton.decommission
 

 
4. Follow the steps displayed on screen to decommission the media server.
 

 
5. If an output file is specified - in the example above, /tmp/clapton.decommission - it can later be reviewed, to review which changes were performed in the NetBackup environment.
 

 
Limitations:
It is important to note that there are several things the nbdecommission command does not do:
 
  • It does not process the media server deduplication pools.
  • It does not update the vm.conf file on NetBackup servers in your environment. Therefore, the old server may remain in the vm.conf file on NetBackup servers until it is manually edited out.
  • It does not update the configuration files on clients. Therefore, the old server may remain in the server lists on the clients. If you replace an old server with a new server, the new server is not added to the client server lists.
  • It does not decommission clustered media servers.
  • It does not handle Vault profiles. If there are Vault profiles that refer to devices on the old server, they must be updated manually before running the tool.
  • When run, nbdecommission moves the old server to an Administrative Pause state so that no new jobs are started.  However, NetBackup still can start backup and restore jobs for BasicDisk, as those jobs obtain resources differently than do jobs for other storage destinations. And nbdecommission may itself clear the administrative pause as needed to allow the image expiration to work. Some jobs can start running during this period.

 

Attachments

7.0_decommission_354756.zip (4.6 MBytes)


Legacy ID



354756


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


Terms of use for this information are found in Legal Notices