Veritas NetBackup™ Appliance Decommissioning and Reconfiguration Guide
- Decommissioning a NetBackup appliance
- Reconfiguring a NetBackup appliance
- About reconfiguring a NetBackup appliance
- About reconfiguring a NetBackup appliance
- Appendix A. Migration from Cloud Catalyst to MSDP direct cloud tiering
- Appendix B. LUN reconfiguration
Migrating from NetBackup Cloud Catalyst Appliance to MSDP direct cloud tiering
Starting with NetBackup appliance release 4.1, the Cloud Catalyst feature is no longer supported. However, you are encouraged to move to MSDP direct cloud tiering. This technology offers improved performance, reliability, usability, and flexibility when compared to the earlier Cloud Catalyst product.
Details for migrating from Cloud Catalyst to MSDP direct cloud tiering are included in the Veritas NetBackup Deduplication Guide, Appendix B. You should review that information before proceeding with the migration.
This document provides the additional required information to convert a NetBackup Cloud Catalyst Appliance to use MSDP direct cloud tiering. The following describes the supported and unsupported migration scenarios, and the migration process.
Note:
Note: The procedures in this appendix must be run on MSDP servers running appliance versions 5.0 and later. The master server may be running a newer version, but the MSDP server on which the nbdecommission -migrate_cloudcatalyst command is run, must be running one of these versions.
New NetBackup appliance installations
You can deploy any new NetBackup Appliance with software version 5.0 and later and configure it to use MSDP direct cloud tiering.
Existing Cloud Catalyst Appliance installations
You can re-image most existing installations of Cloud Catalyst appliances with software version 5.0 to use MSDP direct cloud tiering.
Existing NetBackup appliance media server installations that are used as an MSDP target server
You can upgrade most existing NetBackup appliance media server installations with software version 5.0 to use MSDP direct cloud tiering.
Any NetBackup 5240 Appliance that used software version 3.1.x and was configured as a Cloud Catalyst storage server with a cloud bucket, and then modified as follows:
The appliance was re-imaged with software version 3.2 or later.
The re-imaged appliance was configured as a Cloud Catalyst storage server to use the same cloud bucket, without cleaning up the cloud bucket data. Therefore, the re-imaged appliance is using the same cloud bucket data that was first generated with version 3.1.x.
For this scenario, see the Veritas NetBackup Deduplication Guide, Appendix B for other migration options.
The actual time to complete the migration (Task 6: Perform migration steps) can vary, depending on the cloud provider involved and the available network bandwidth for downloading from the cloud. Most migrations should finish within 24 hours, and many require much less than 24 hours. However, in some cases it may take longer.
The following shows a summarized list of the required tasks to migrate to MSDP direct cloud tiering. Click on each link for the details of each task.
Task 1: Review migration documentation
Task 2: Upgrade primary server
Task 3: Collect required data to prepare for pre-migration steps
Task 4: Perform pre-migration steps
Task 5: Re-image and reconfigure Cloud Catalyst appliance
Task 6: Perform migration steps
Task 7: Perform post-migration steps
For complete details about migrating to MSDP direct cloud tiering, see the Veritas NetBackup Deduplication Guide, Appendix B.
For additional details about migrating a NetBackup Cloud Catalyst appliance to MSDP direct cloud tiering, review this entire topic.
Upgrade the associated primary server as follows:
For a NetBackup Appliance primary server, upgrade to appliance version 5.0 or later. See the Veritas NetBackup Appliance Upgrade Guide.
For a traditional NetBackup primary server, upgrade to version 10.0 or later. See the Veritas NetBackup Upgrade Guide.
Before you start the migration, collect the following information about the existing Cloud Catalyst appliance and any new information as needed for the migrated MSDP direct cloud tier storage server. Use the right column in the table to enter the information.
Table: Data for pre-migration tasks
Item | Configuration data |
---|---|
Cloud Catalyst appliance hostname | |
Admin login credentials to elevate to maintenance mode | |
Cloud Catalyst storage server name | |
Cloud Catalyst bucket or container name | |
KMS configuration/KMS Key Group Name | |
Name to use for the new disk volume for the migrated MSDP direct cloud tier storage server | |
Name to use for the new disk pool for the migrated MSDP direct cloud tier storage server | |
Your cloud credentials | |
Other cloud-specific configuration information | |
List of policies and SLPs, that currently write to the Cloud Catalyst storage server |
After you have completed collecting the information above, do the following:
Create a NetBackupCLI user with administrator privileges on the associated appliance primary server and on the appliance media server.
Sign in to the Veritas Download Center to obtain one of the following hot fixes (EEBs), based on the current software version on your Cloud Catalyst appliance:
NBAPP_EEB_ET4063815-5.0.0-1.x86_64.rpm
(for software versions 3.2)NBAPP_EEB_ET4063818-5.0.0-1.x86_64.rpm
(for software version 3.3.0.1)Note:
Hot fixes are not available for Cloud Catalyst appliances that use software versions earlier than 3.2. Before you can perform the migration for those appliances, you must first upgrade them to version 3.2 or 3.3.0.1.
After you have manually performed the initial pre-migration steps in the following task, hot fix installation performs the remaining pre-migration steps.
The following procedure describes the pre-migration tasks.
To perform the pre-migration steps
- Stop all jobs on the Cloud Catalyst appliance as follows.
Deactivate all backup policies that write to the Cloud Catalyst storage server.
Deactivate all storage lifecycle policies (SLPs) that write to the Cloud Catalyst storage server.
Verify all active jobs that are targeted for the Cloud Catalyst storage server have been stopped.
- Log in to the primary appliance server as a NetBackupCLI Administrator and run the following command to clean up the NetBackup catalog:
bpimage -cleanup -allclients -prunetir
For a traditional NetBackup primary server, log in to the NetBackup Administration Console to run the command.
- To complete the pre-migration steps on the Cloud Catalyst appliance, install the EEB that you downloaded from the Vertias Download Center (in Task 3) and respond to the prompts as they appear.
For a Cloud Catalyst appliance, you must re-image it with NetBackup Appliance release 5.0 and then reconfigure it.
Caution:
Do not perform a factory reset before you re-image the Cloud Catalyst appliance.
For other NetBackup Appliance media servers that use a different MSDP server, upgrade them to NetBackup Appliance release 5.0.
For re-imaged or upgraded appliances, you must also reset the storage and delete the existing PureDisk storage unit and disk pool on the media server as described.
After completing a re-image or an upgrade to NetBackup Appliance release 5.0
- Reset the storage and remove all PureDisk storage elements as follows:
Log in to the appliance shell menu and run the following command to reset the storage:
Support > Storage Reset
Log in to the NetBackup Web UI and delete the PureDisk storage unit and disk pool on the media server.
- For re-imaged appliances only:
After resetting the storage as previously described, reconfigure the appliance and set the Role for Media. You must associate this server with the same primary server that was used before the re-image. Make sure that the re-imaged appliance media server has an adequate amount of space for the MSDP partition.
If the appliance was previously configured for KMS, make sure to configure it after you have completed the reconfiguration.
Recreate the NetBackupCLI user with Administrator privileges (from Task 3), which was lost when you re-imaged the appliance.
After reconfiguration of a re-imaged Cloud Catalyst appliance to 5.0 or an upgrade of a NetBackup Appliance media server to 5.0, you are ready to perform the migration.
Note:
The actual time to complete this task can vary, depending on the cloud provider involved and the available network bandwidth for downloading from the cloud. Most migrations should finish within 24 hours, and many require much less than 24 hours. However, in some cases it may take longer.
To perform the migration steps
- Log in to the re-imaged or upgraded appliance as a NetBackupCLI Administrator and run the following command:
bpnbat -Login -loginType WEBUI -requestApproval
- To start the migration process, run the following command:
sudo /usr/openv/netbackup/bin/admincmd/nbdecommission -migrate_cloudcatalyst
- Monitor the migration and provide the following information or responses when prompted to do so:
The line number of the Cloud Catalyst server to migrate
Cloud bucket name
Cloud Catalyst server hostname
Indicate if MSDP KMS encryption is enabled for
cloudcatalyst_server_name
.New disk volume name for the migrated Cloud Catalyst server
New disk pool name for the migrated Cloud Catalyst server
Cloud account username or access key
Cloud account password or secret access key
Indicate if you want to migrate
cloudcatalyst_server_name
to the new MSDP cloud server.Verify that no jobs are currently running on the Cloud Catalyst server.
Decide if you wish to skip migrating Cloud Catalyst image sharing information.
Select how to handle the SLP-controlled images that are in-process or yet to be processed. Options are displayed.
Select how to delete the Cloud Catalyst disk pool, storage unit, and storage server, or how to deactivate the policies that reference the Cloud Catalyst storage unit. Options are displayed.
Immediately after the migration process has completed successfully, perform the following tasks:
After the migration process has completed successfully
- Log in to the appliance (image sharing server) as a NetBackupCLI Administrator and run the following command, and then restart the appliance:
cacontrol --catalog buildcloudcatalystobjects <new_disk_volume_name>
For details about this command, see the Veritas NetBackup Deduplication Guide, Appendix B.
- Create a new storage unit for this disk pool that was created during the migration through the NetBackup Web UI. Use the new storage unit as the destination for your policies and SLPs through the NetBackup Java Console.
- Re-enable any existing policies and SLPs that previously wrote to the migrated Cloud Catalyst server, as the migration process disables these policies.
- Optional step: To clean up any unused Cloud Catalyst objects from the cloud bucket, log in to the media server appliance as a NetBackupCLI user and run the following command:
cacontrol --catalog cleanupcloudcatalystobjects <new_disk_volume_name>
For details about this command, see the Veritas NetBackup Deduplication Guide, Appendix B.