How to remove NetBackup Media Server Deduplication option (MSDP) configurations from a NetBackup environment.

Article:TECH150431  |  Created: 2011-01-26  |  Updated: 2014-07-16  |  Article URL http://www.symantec.com/docs/TECH150431
Article Type
Technical Solution


Issue



How to remove NetBackup Media Server Deduplication option (MSDP) configurations from a NetBackup environment.


Solution



Warning:- These steps will expire any images associated with the MSDP Disk Pool to be removed!!!!

 NOTE: For NetBackup version 7.0.1, the script in step 13 is only available with the latest dedup bundle from ET2233961 / TECH153190.  For version 7.1.0.1, only with the latest dedup bundle from ET2412409.  Delivered in 7.1.0.2 and higher and in version 7.5. Please upgrade to obtain this functionality.

All commands are located in the admincmd directory unless otherwise noted:

Unix:   
/usr/openv/netbackup/bin/admincmd
Windows:  <install path>\NetBackup\bin\admincmd


1. Ensure a recent and successful hot catalog backup exists before proceeding. In the next steps we are going to delete Storage Lifecycle Policies (SLPs), Storage Units, and Image references in the Catalog.

2.  Make sure no policies point directly or indirectly (through SLP) to the MSDP we are going to decommission. This is to ensure no new backup images will be written to the MSDP while we are removing it in the next steps. Furthermore it will make it possible to remove the SLPs pointing to the MSDP.

3. Make sure that the MSDP doesn't hold any images still under SLP control. Use nbstlutil to cancel SLP processing for any images that are currently being read from or written to the MSDP being decommissioned.

4. Carefully expire only the images from the catalog that pertain to the Disk Pool to be removed. (NetBackup administration console -> NetBackup Management -> Catalog, 'Action' dropdown set to 'Verify', change 'Disk type' dropdown to PureDisk, and 'Disk Pool' dropdown to the MSDP Disk Pool name in question. Then change the start date to a past date/time to accommodate the oldest images, then click 'Search Now'. Select all the images found, right-click and choose 'Expire'.) 
Wait for the NetBackup 'Image Cleanup' jobs to complete before proceeding.

Additional steps may be involved if using Storage Lifecycle Policies:

If, during image expiration, you receive an error :

NetBackup status code: 1573
Message: Backup image cannot be expired because its SLP processing is not yet complete

Do ONE of the following:

  • Wait until SLP processing for that image is complete, then retry the expiration operation.
     
  • Use the nbstlutil -cancel command to cancel further processing on the relevant image: nbstlutil cancel -backupid <BackupID>
    Then retry the expiration operation.
     
  • Add the -force_not_complete option to the bpexpdate command to force expiration even if the image-copy is not SLP complete:
        
    bpexpdate -stype PureDisk -dp <disk pool> -dv <disk volume> -force_not_complete

         Use -notimmediate if there are many images to be deleted. Refer to HOWTO43656.

Continue with the next steps only after completing the previous steps.

 5. Delete any SLPs that point to the MSDP.
If you instead choose to remove the MSDP from the SLPs (for example, if you plan to re-add it later), make sure that no SLP versions refer to the MSDP.
This can be verified with the command:   
nbstl -L -all_versions

Note that if 'CLEANUP_SESSION_INTERVAL_HOURS' has not been changed in the LIFECYCLE_PARAMETERS config file, then old SLP versions may exist 14 days (default) after a new SLP version has been created.  See TECH172249 and HOWTO68320 for further information.

6. Delete any storage units that belong to the MSDP.

7. Clean up images using nbdelete and bpimage:

 nbdelete -allvolumes -force
 bpimage -cleanup -allclients

8. Set the Disk Pool to a down state using nbdevconfig (install_path\NetBackup\bin\admincmd):

nbdevconfig -changestate -stype PureDisk -dp your_MSDP_disk_pool_name -dv PureDiskVolume -state DOWN

9. Run this command on the master server to list all server entries:  nbemmcmd -listhosts
Take note of the NDMP machinetype entry for the storage server in question.

10. Delete the Disk Pool from the NetBackup Administration Console -> Devices -> Disk Pools

11. Delete the storage server credentials, storage server and the storage server NDMP machine type from the EMM database:

\Volmgr\bin\tpconfig -delete -storage_server your_MSDP_storage_server_name -stype PureDisk -sts_user_id root

nbdevconfig -deletedp -stype PureDisk -dp you_disk_pool_name

nbdevconfig -deletests -storage_server your_MSDP_storage_server_name -stype PureDisk

nbemmcmd -deletehost -machinename your_MSDP_storage_server_name -machinetype ndmp

Note that the tpconfig and nbdevconfig commands above will fail if you deleted the storage server and credentials in the NetBackup Admin Console. This is OK.

12. Stop NetBackup services on the MSDP server.

13. Execute the PDDE_deleteConfig script to remove the MSDP configurations:

Windows: <install_path>\Veritas\pdde\PDDE_deleteConfig.bat
UNIX/Linux: /usr/openv/pdde/pdconfigure/scripts/installers/PDDE_deleteConfig.sh

14. Remove any cfg files referring to the MSDP server under /usr/openv/lib/ost-plugins (Unix) or \NetBackup\bin\ost-plugins (Windows).  This must be done on the MSDP server itself and any other servers referencing the host as an 'Additional Server'.
On the MSDP server being deleted, also remove the cfg files for any other MSDP servers. These will be re-created should one later be re-created on the MSDP host.

15. Delete the deduplication storage directory (and db path, if it was specified at installation time).
* Note: If this is an appliance (52x0), do NOT delete /disk. It is better to do a Factory Reset at this step when on an appliance (
HOWTO94245)

16. Start the NetBackup services/processes.

17. Create new Storage Server and Disk Pool
Admin Console --> Storage Servers --> New Storage Server
Admin Console --> Devices --> Disk Pools --> New Disk Pool 

 

 

 





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


Terms of use for this information are found in Legal Notices