How to perform a BCS Media Server rename for an advanced disk pool basic disk and tape

How to perform a BCS Media Server rename for an advanced disk pool basic disk and tape

Article: 100045227
Last Published: 2019-04-12
Ratings: 0 0
Product(s): NetBackup

Migration Procedure

The following procedure is intended to assist with migrating a NetBackup media server from one host to another with a different name, or it can also be used to rebuild an existing host with a different host name on the same type of operating system platform (EG Solaris 10 to Solaris 11, RHEL 6.9 to RHEL 7.5 or Windows 2008 to Windows 2012R2).

Limitations

This procedure does not cover a media server with MSDP or OST storage devices defined.

For a rename of media servers with these types of storage disk pools defined, a cost quote can be obtained from Veritas Consulting Services to perform the migration for you.

Alternatively, duplicate the MSDP associated with the disk pool on this host to an MSDP disk pool on an alternative host. Once you are certain all images have been duplicated successfully and you have tested restores on the target media server, you can expire the copies on this media server. Remove the MSDP disk pool and PureDisk storage server before beginning the migration of the other storage elements to your target media server or rebuilding your source media server.

This procedure works migrating media servers from Windows to Windows and from the same type of Unix to Unix.

If you need to migrate a media server from HPUX/AIX to RHEL/Oracle please see the following document though this does not permit a rename of the server. https://www.veritas.com/content/support/en_US/doc/MediaServerMigration

This procedure does not apply to NetBackup master servers. To rename a master server will require assistance from Veritas Consulting Services to perform the rename for you.

Assumptions

The following items are assumed to have been completed and/or tested prior to migration date:

  • Tape/Disk zoning: the target media server has been zoned to see defined NBU tape drives and disk
  • Firewall rules: Any firewall rules which need to be modified or created have been completed.
  • Tuning: All OS and TCP/IP tuning has been completed to include any TCP routes.
  • Installation Paths: NetBackup installation paths must be the same on source and target media servers, including basic and advanced disk storage unit paths.
  • Software: All necessary software and current patches, including NetBackup, have been downloaded and are available.
  • VxSS/NBAC: VxSS or NBAC are not implemented within the environment. If enabled, this must be disabled beforehand and set up again afterwards.
  • Storage Units: This process is supported for the following Storage Units: AdvancedDisk, Advanced Disk and robotic tapes unless MSDP is configured on the source media server itself. In which case the images must be migrated from the source media server to alternate media servers (otherwise after the migration the images may be unavailable and inaccessible.)


Terminology

Source media server – the original media server

Target media server – the new media server

SLP – Storage Lifecycle Policies

Robotic Control Host – host where the robotic changer physical path is defined.

In this document we have used the following names as examples

   Media server original name:  source-media
   Media server new name after procedure: target-media


Pre-migration Tasks

  1. Ensure all zoning for the robot changer and drives is complete to allow access from the target media server.
     
  2. Download any Operating System, SAN, robotic and drive software required for the target media server.
     
  3. Collect an NBSU output (to ensure you have details of the existing configuration if needed).
     
  4. Ensure the NetBackup installation software and any relevant binaries are available for installation.
     
  5. Keep an eye on the SLP duplication backlog. Wait for it to complete prior to starting the rebuild/migration as there must be no pending SLP duplications/replications.
     
  6. Update all media servers (including master server) and clients with the target media server. (This is to add the target media server to the known hosts lists for when the migration is complete)

From NBU GUI:

  • On the master server admin console, go to Host Properties > Clients
  • Select first client to modify, then press and hold down the CTRL Key, and then select each additional client to modify.
  • Right-Click all the highlighted clients and select Properties
  • Verify the title bar states Client Properties for X hosts (X= number of hosts selected)
  • Select Servers on the Left
  • Click the Add button on the top listed under Additional Servers.
  • Enter the server name of the target media server.
  • Click add to add the server to the list.
  • Click apply, and this will update the server on those clients/media servers/masters selected.
  • Click OK
  1. Delete the robot and tape devices associated with the source media server.

  2. If migrating to a media server with a different name, build the target media server and install NetBackup with the same version. (Including any required emergency engineering binaries.)
     
  3. Use the nbdevquery command to identify the disk pool ID (needed later to update the image headers).
    # /usr/openv/netbackup/bin/admincmd/nbdevquery -listdv -stype AdvancedDisk
    V7.7 Disk_Adv_media1 AdvancedDisk /adv_disk_media1 @aaaac 1.00 0.96 3 1 0 1 0 0 14

 

Migration Tasks

  1. Set the source media server to inactive. Using the NetBackup Administration Console:
    • click Media and Device Management > Devices > Media Servers 
    • b.  Right click media server and click: Deactivate 
    • Using the nbemmcmd command from the master server: /usr/openv/netbackup/bin/admincmd/nbemmcmd -updatehost -machinename <source-media> -machinestateop set_admin_pause -machinetype media -masterserver <master-server>
       
  2. Ensure all SLP duplications are completed. (/usr/openv/netbackup/bin/admincmd/nbstlutil stlilist -U) If not complete, cancel the pending SLP duplications or wait for them to complete.
     
  3. Stop all NetBackup processes on the source media server and disable them from restarting automatically by removing start up scripts or disabling the services.
     
  4. Disable all backup policies and storage lifecycle policies which access the source media server are disabled, including those on A.I.R. replication remote servers.
     
  5. Create the ‘/usr/openv/netbackup/bin/NOexpire’ file on the master server to avoid any image clean-ups running while manipulating the catalog during the media server changes.
     
  6. Ensure all jobs are complete before beginning the migration.
     
  7. Unmount the disk drives associated with the AdvancedDisk and BasicDisk (if applicable) pools.
    If rebuilding, ensure these disks are not rebuilt during the operating system installation.
     
  8. Rebuild the media server with updated operating system version. Install all required OS packages.
    (Ignore if using a target media server built on new hardware.)
     
  9. Install any other required packages needed for support of the robot and drives and any other customer software.
    (Ignore if using a target media server built on new hardware.)
     
  10. Install the same version of NetBackup and any required EEB’s. Configure with the target media server name.
     
  11. Shutdown NetBackup on source and target media server.
     
  12. Update the bp.conf on the target media server with the correct server information.
     
  13. Mount the disk used previously for the AdvancedDisk pool on the target media server using the same mount point as used on the source media server (create mount point as necessary). If the disk cannot be mounted on the new system, copy the data in the AdvancedDisk pool to same location on the target media server. (Method such as: tar, sftp or scp data can be used. Ensure data is copied in binary format)
     
  14. Start NetBackup on the target media server (re-enable services/start up scripts)
     
  15. Create the target storage server for the AdvancedDisk pool:
    /usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server <target-media> -stype AdvancedDisk
     
  16. Add the target media server storage server to the existing disk pool:
    /usr/openv/netbackup/bin/admincmd/nbdevconfig –changedp -dp <source-disk-pool-name> -stype AdvancedDisk -add_storage_servers <target-media>
     
  17.  Remove the source media server storage server from the disk pool
    /usr/openv/netbackup/bin/admincmd/nbdevconfig -changedp -dp <source-disk-pool-name> -stype AdvancedDisk -del_storage_servers <source-media>
     
  18. Remove the Advanced Disk server role from the original media server name
    /usr/openv/netbackup/bin/admincmd/nbdevconfig -deletests -storage_servers <source-media> -stype AdvancedDisk
     
  19. Migrate the BasicDisk data to the target media server (method such as: tar, sftp or scp data can be used. Ensure data is copied in binary format).
     
  20. Create a mount point which matches the BasicDisk pool mount point on the source media server.
     
  21. Create a basic disk storage unit and use the correct mount point for it on the target media server
     
  22. Delete the Basic Disk storage unit on the source media server
     
  23. Delete the BasicDisk server role on the source media server
    /usr/openv/netbackup/bin/admincmd/nbdevconfig -deletests -storage_servers <source-media> -stype BasicDisk
     
  24. Change all the images on the disk pool to be owned by the rebuilt media server in the image database (Check the diskID in the nbdevquery output in point 9 in the pre-migration steps above).
    /usr/openv/netbackup/bin/admincmd/bpimage -oldserver <source-media> -newserver <target-media> -id <@aaaab>
    /usr/openv/netbackup/bin/admincmd/bpimage -oldserver <source-media> -newserver <target-media>

     
  25. Use the Java GUI to create robots and drives as necessary on the target media server.
     
  26. Move all tape media associated with the source media server to the target media server name run:
    /usr/openv/netbackup/bin/admincmd/bpmedia -movedb -allvolumes -oldserver <source-media> -newserver <target-media>
     
  27. Run ‘nbdevquery -listdp/-listdv’ and bpstulist commands to confirm the configuration looks correct. Also check the NetBackup Java Gui.
     
  28. Test backups and restores for both the disk pool and tape media.
     
  29. Update all policies and SLPs with the target media server’s storage unit details.
     
  30. Remove all references to the source media server’s storage units.
     
  31. Reactivate all policies and SLP’s.
     
  32. Run a further NBCC to confirm there are no images or tape media associated with the source media server name. When happy these have been removed, use ‘nbdecommission’ with appropriate binaries to clean up the source media server references.
    https://www.veritas.com/support/en_US/doc/18716246-126559472-0/v12948402-126559472
    Note: If doing this at NetBackup 7.x download the EEB to avoid removal of more credentials than intended and apply them before running nbdecommission:
    https://www.veritas.com/content/support/en_US/article.100000462.html
     
  33. Once happy the configuration is up and running okay, delete the ‘/usr/openv/netbackup/bin/NOexpire’ file on the master server.
     
  34. Run the following commands to cleanup the disk volume references and to force an image cleanup.
    /usr/openv/netbackup/bin/nbdelete -allvolumes -force
    /usr/openv/netbackup/bin/admincmd/bpimage -prunetir -allclients -cleanup

Was this content helpful?