Running the migration to the new MSDP direct cloud tier server
Before you continue the process of installing and configuring the new MSDP direct cloud tier server, it is recommended that you set up logging. If any issues arise during installation, the logs help with diagnosing any potential errors during migration. The following items are recommended:
Ensure that the
/usr/openv/netbackup/logs/admindirectory exists before running the nbdecommission command.Set the log level to VERBOSE=5 in the
bp.conffile.Set loglevel=3 in
/etc/pdregistry.cfgforOpenCloudStorageDaemon.Set Logging=full in the
contentrouter.cfgfile.
To run the migration, go to the command prompt on the MSDP direct cloud tier server and run:
/usr/openv/netbackup/bin/admincmd/nbdecommission -migrate_cloudcatalystNote:
This utility needs to be run in a window that does not time out or close even if it runs for several hours or more. If the migration is performed on an appliance, you need to have access to the maintenance shell and it needs to remain unlocked while the migration runs. The maintenance shell must remain enabled even if it runs for several hours or more.
Select the Cloud Catalyst storage server to migrate and enter the information as prompted by the nbdecommission utility.
The following is an example of what you may see during the migration:
# /usr/openv/netbackup/bin/admincmd/nbdecommission -migrate_cloudcatalyst
MSDP storage server to use for migrated CloudCatalyst: myserver.test.com
Generating list of configured CloudCatalyst storage servers.
This may take a few minutes for some environments, please wait.
Cloud Storage Server Cloud Bucket CloudCatalyst Server Storage Server Type
1) amazon.com my-bucket myserver.test.com PureDisk_amazon_rawd
Enter line number of CloudCatalyst server to migrate: 1
MSDP KMS encryption is enabled for amazon.com.
Please confirm that CloudCatalyst was configured using
KMSKeyGroupName amazon.com:testkey
Continue? (y/n) [n]: y
Enter new disk volume name for migrated CloudCatalyst server: newdv
Enter new disk pool name for migrated CloudCatalyst server: newdp
Enter cloud account username or access key: AAAABBBBBCCCCCDDDDD
Enter cloud account password or
secret access key: aaaabbbbccccddddeeeeffffggg
You want to migrate amazon.com (bucket my-bucket) to
newmsdpserver.test.com (volume newdv, pool newdp).
Is that correct? (y/n) [n]: y
To fully decommission myserver.test.com after
CloudCatalyst migration is complete,run the
following command on the primary server:
/usr/openv/netbackup/bin/admincmd/nbdecommission
-oldserver myserver.test.com
Administrative Pause set for machine myserver.test.com
Migrating CloudCatalyst will include moving the images to server
newmsdpserver.test.com deleting the old disk pool, storage unit, and
storage server, deactivating policies that reference the old storage
unit, and restarting MSDP on server newmsdpserver.test.com.
Before proceeding further, please make sure that no jobs are running on
media server myserver.test.com or media server newmsdpserver.test.com.
This command may not be able to migrate CloudCatalyst
with active jobs on either of those servers.
To avoid potential data loss caused by conflicts between the
old CloudCatalyst server and the migrated MSDP server, stop the
NetBackup services on myserver.test.com if they are running.
It is recommended to make one or both of the following changes
on myserver.test.com to prevent future data loss caused by
inadvertently starting NetBackup services.
1) Rename /usr/openv/esfs/bin/vxesfsd to /usr/openv/esfs/bin/vxesfsd.off
2) Change "ReadOnly" to "1" in the esfs.json configuration file
See the documentation for more information about esfs.json.
It is also recommended to perform a catalog cleanup and backup prior
to migration so that the catalog can be restored to its original
state in the event that migration is not completed.
Continue? (y/n) [n]: y
Successfully cloned storage server: amazon.com to:
newmsdpserver.test.com_newdv
Storage server newmsdpserver.test.com has been successfully updated
The next step is to list the objects in the cloud and migrate
the MSDP catalog. The duration of this step depends on how much data
was uploaded by CloudCatalyst.
It may take several hours or longer, so please be patient.
You may reduce the duration by not migrating the
CloudCatalyst image sharing information if you are certain that
you do not use the image sharing feature.
Do you wish to skip migrating CloudCatalyst image
sharing information? (y/n) [n]:
Jun 24 15:37:11 List CloudCatalyst objects in cloud
Jun 24 15:37:13 List CloudCatalyst objects in cloud
Jun 24 15:37:18 List CloudCatalyst objects in cloud
Jun 24 15:37:26 MSDP catalog migrated successfully from CloudCatalyst
Disk pool newdp has been successfully created with 1 volumes
Moved CloudCatalyst images from myserver.test.com to newmsdpserver.test.com
Disk pool awsdp (PureDisk_amazon_rawd) is referenced by the following
storage units:
awsdp-stu
Storage unit awsdp-stu: host myserver.test.com
Deactivating policies using storage unit awsdp-stu
Storage unit awsdp-stu is referenced by policy testaws
Deactivated policy testaws
Deleting storage unit awsdp-stu on host _STU_NO_DEV_HOST_
Deleted storage unit awsdp-stu
Deleted PureDisk_amazon_rawd disk pool awsdp
Deleted PureDisk_amazon_rawd storage server amazon.com
Stopping ocsd and spoold and spad
Checking for PureDisk ContentRouter
spoold (pid 55723) is running...
Checking for PDDE Mini SPA [ OK ]
spad (pid 55283) is running...
Checking for Open Cloud Storage Daemon [ OK ]
ocsd (pid 55150) is running...
Stopping PureDisk Services
ocsd is stopped
Run MSDP utility to prepare for online checking.
This may take some time, please wait.
Starting ocsd and spoold and spad
Checking for Open Cloud Storage Daemon
ocsd is stopped
Starting Open Cloud Storage Daemon: ocsd Checking for PDDE Mini SPA
spad is stopped
spad (pid 56856) is running... [ OK ]
Checking for PureDisk ContentRouter
spoold is stopped
spoold (pid 57013) is running...spoold [ OK ]
Starting PureDisk Services
spoold (pid 57013) is running...
Enabling data integrity check.
Starting data integrity check.
Waiting for data integrity check to finish.
Processing the queue.
CloudCatalyst server myserver.test.com has been successfully
migrated to newmsdpserver.test.com.
To avoid potential data loss caused by conflicts between the
old CloudCatalyst server and the
migrated MSDP server, stop the NetBackup daemons (or services)
on myserver.test.com if they are running.
Monitor the output of the nbdecommission command for errors. Other logs to monitor for activity and potential errors are in the storage_path/log/ directory. You should monitor the ocsd_storage log and monitor the spad and spoold logs for any cacontrol command issues.
If an error is encountered and you can correct the error, you can resume the migration from that point using the start_with option as noted in the output from the nbdecommission command. If you have any questions about the error, contact Veritas Support before you resume the migration.
During the migration, there are several prompts that are displayed when the migration is run. You can use command line options to supply answers to these prompts, if necessary. Veritas recommends that you use the interactive prompts because it makes the migration easier to use and less error prone than using the command line options. If you choose to use the command line, the options are documented in the NetBackup Commands Reference Guide.
During the migration process most of the prompts are self-explanatory and the number and type of prompts can change. The number and type of prompts depends on the following:
The version of Cloud Catalyst being used at time of the migration.
If the Cloud Catalyst server is running at the time of the migration.
If KMS is enabled on the Cloud Catalyst server.
Table: Migration prompts discusses additional information about a few of the prompts.
Table: Migration prompts
Prompts | Description |
|---|---|
No MSDP storage server found on myserver.test.com. Please create the MSDP storage server before running this utility. | This output is displayed when the nbdecommission -migrate_cloudcatalyst command is run on a media server that does not have an MSDP storage server configured. |
Disk pools exist for storage server PureDisk myserver.test.com. CloudCatalyst migration requires a new storage server with no configured disk pools. | The sample output is displayed when the nbdecommission -migrate_cloudcatalyst command is run on a media server that does have an MSDP storage server configured and does have existing disk pools configured. Cloud Catalyst migration can only be run on a new MSDP cloud tier server with no existing disk pools. |
Enter cloud bucket name: | If the Cloud Catalyst server is not running at the time of migration you need to manually enter the existing Cloud Catalyst bucket or container name. This information is used for migration. |
Enter CloudCatalyst server hostname: | If the Cloud Catalyst server is not running at the time of migration you need to manually enter the server hostname of the existing Cloud Catalyst server to be migrated. |
Is MSDP KMS encryption enabled for amazon.com? (y/n) [n]: | If the Cloud Catalyst server is not running at the time of migration you may need to manually enter the KMS configuration settings for the existing Cloud Catalyst server. |
Enter new disk volume name for migrated CloudCatalyst server: | Enter the name of the MSDP Cloud disk volume to be created on the new MSDP cloud tier server. This name is used for the migrated Cloud Catalyst data. |
Enter new disk pool name for migrated CloudCatalyst server: | Enter the name of the MSDP Cloud disk pool to be created on the new MSDP server and used for the migrated Cloud Catalyst data. |
Enter cloud account username or access key: Enter cloud account password or secret access key: | Enter the credentials for the cloud account that is used to access the Cloud Catalyst data to be migrated. If you use AWS IAM role to access the data, you should enter |