Master server migration to an NetBackup Appliance

Article:TECH203048  |  Created: 2013-02-21  |  Updated: 2013-03-04  |  Article URL http://www.symantec.com/docs/TECH203048
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Environment

Issue



It is sometimes necessary for a customer to replace the hardware they use for their master server with a NetBackup Appliance. This tech note explains how catalog backup and recovery can be used to perform this migration.

If one or more of these conditions is not met please contact Symantec Consulting Services or your Business Critical Account Manager for assistance.

 

  1. The existing NetBackup master must be Unix based (recovery from Windows to Appliance is not supported)
  2. The existing NetBackup master must be 7.5.0.4 or higher.
  3. The version of existing NetBackup installed on the old and Appliance must be the same release update of NetBackup (e.g. if the old master server is running NetBackup 7.5.0.4, the Appliance must be installed with version 2.5.1(b)). A version table can be found by running a Installation and Upgrade checklist on the SORT web site under 'Symantec NetBackup Appliances'
  4. The existing NetBackup master server must not be a media server for SharedDisk, OpenStorage or MSDP. Customers should expire or duplicate all copies of disk storage attached to the existing master.
  5. The host name and IP address of the existing master and new appliance must be the same.
  6. The existing master catalog components must be restored to paths that exist on the Appliance, for example a Solaris system with a install of /opt/openv/ would require a symlink on the Appliance to to the appliance default of /usr/openv/ (for example running a ln –s /usr/openv /opt/openv) to enable a successful restore.
  7. The existing master server must not be clustered.
  8. Key Management Server (KMS) and NetBackup Access Control(NBAC) are not supported on a Appliance master and cannot be recovered using this procedure.
     

Solution



The following procedure should be used when migrating to an Appliance:

1.  Make a full catalog backup of the old master server and shut it down.
 

2.  Prepare the new Appliance as a master server using the same host name and IP address as the old master server (ensure that the conditions stated above are met).
 

3.  Make a copy of the bp.conf created on the Appliance
 

4.  Restore the catalog backup created from the old master server to the new Appliance master server. Details of the catalog restore process can be found in the Disaster Recovery section of the NetBackup Troubleshooting Guide.
 

5.  From the copy of bp.conf in step 3, update the restored bp.conf with the following settings:


PREFERRED_NETWORK =
NETBACKUP_APPLIANCE_MODE =
IP_ADDRESS_FAMILY =


6.  Once the catalog has been restored confirm the basic operation of NetBackup by running test backup and restore jobs.


7.  If the master server is also a tape media server, run the device discovery wizard to update the locally presented devices and storage units.
 

8.  If the original master is not a Linux (RedHat or Suse) run the command "nbemmcmd -updatehost -machinename <master server name> -machinetype master -operatingsystem linux” Running this command updates the operating system field in the EMM master server record to the appliance OS of Linux.
 

9.  The default Appliance configuration for storage units/slp/catalog backup will be overwritten. This will cause the Appliance self test to fail certain tests due to lack of defaults.
 




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


Terms of use for this information are found in Legal Notices