Prerequisites for MSDP server evacuation
Before performing an MSDP server evacuation, ensure that the following prerequisites are met:
Ensure that the MVG server is in the server list of the primary server in
bp.conffile. See the following article for more information: https://support.cohesity.com/s/article/article-100017409Ensure the following settings on the MVG server:
NGINX is configured and running on the MVG server. If the MVG server is configured on BYO before NGINX is configured and enabled, run the following command to reconfigure SPWS and NGINX.
/usr/openv/pdde/vpfs/bin/vpfs_config.sh --configure_byo
Add the MVG evacuation directory in BPCD_ALLOWED_PATH in
bp.conffile.BPCD_ALLOWED_PATH = <mvg-storage-path>/mvg/cache/evac
For example, if MVG server is configured in
/msdpdirectory,BPCD_ALLOWED_PATH = /msdp/mvg/cache/evac
Assign the disk volume of the MSDP server to an MVG volume if it has not been assigned yet. Ensure that the MVG volume includes other disk volumes that are configured in 'Normal' mode. These volumes should have sufficient available space to store the images that are migrated from the MSDP server.
If the MSDP server contains the existing images that are not created through the MVG volume, take one of the following steps to allow the MVG server to initiate optimized duplication jobs for those images:
Option 1: Add all the load balancing media servers of the MVG server in the load balancing media server list of the MSDP server. Alternatively, you can add part of the media servers. By doing so, ensure the storage unit that is used for evacuation has the common media servers specified.
Option 2: Configure NetBackup to not require common media servers between the source and the target storage servers by running the following command on the primary or MVG server:
/usr/openv/netbackup/bin/admincmd/nbemmcmd -changesetting -SHARE_CRED_TO_DUP_READER 1 -machinename <primary server>
See Identifying images not created through the MVG volume on the MSDP server.
If the MSDP server has a cloud volume that needs to be migrated, use the cloud volume migration feature:
If the cloud volume is not currently associated with any MVG volume, use the cloud volume migration feature.
If the cloud volume is already part of an MVG volume or you plan to start using it through an MVG volume.
If you plan to discontinue the use of the cloud volume and want to migrate all data to other storage locations, you can still use the server evacuation process.
You cannot initiate evacuation of a cloud volume within an MVG volume from the NetBackup web UI. Use MVG CLI commands to start the evacuation. You can then monitor the evacuation status using the CLI or the web UI.
Note:
MSDP server evacuation is not supported for any cloud storage types that do not support optimized duplication such as AWS Glacier, AWS Deep Archive, and Microsoft Azure Archive.
If possible, prefer using the cloud volume migration feature over MVG server evacuation for cloud volumes. It is more efficient, as it avoids data movement.
If a universal share is configured on the MSDP server, perform the universal share backup to the MVG volume. Once the evacuation is complete, you can provision and recover data from the universal share backup.