Reverting back to Cloud Catalyst from a successful migration
The process to revert back to Cloud Catalyst assumes that a NetBackup catalog backup was performed for the primary server catalog before the nbdecommission -migrate_cloudcatalyst command was run. If no such NetBackup catalog backup image is available, it is not possible to revert to Cloud Catalyst because the migration process modifies the NetBackup catalog.
The reversion process also assumes that the command /usr/openv/pdde/pdcr/bin/cacontrol --catalog cleanupcloudcatalystobjects has not been run on the migrated MSDP cloud tier server. The reason for that is because once that command has been run, it is not possible to revert back to Cloud Catalyst.
The images that Cloud Catalyst wrote and that have expired since the migration was completed, have been removed from the cloud storage. Reverting to Cloud Catalyst does not make these images available for restore as that data no longer exists.
All caveats and limitations of performing a NetBackup primary server catalog recovery apply, see the section of the NetBackup admin guide that discusses catalog recovery in detail. Specifically, no data is written to the MSDP server or other storage servers after the point in time at which the catalog backup image was created is available. The data is not available for a restore after the NetBackup primary server catalog recovery is performed.
You can use one of the following procedures to revert back to Cloud Catalyst:
The following procedure assumes that the Cloud Catalyst server has been left in the same state that it was in at the time of migration and all services are stopped.
Reverting back to Cloud Catalyst when the server is in the same state when the migration was performed
- Stop the NetBackup services on the new MSDP cloud tier server.
- Open the NetBackup web UI.
- Click Recovery. Then click NetBackup catalog recovery.
- Select the catalog backup image that was created before running the nbdecommission -migrate_cloudcatalyst command to migrate Cloud Catalyst to MSDP cloud tier server.
- Complete all steps in the UI to recover the NetBackup catalog.
- Stop and restart the NetBackup services on the primary server.
- On the Cloud Catalyst server, ensure that the
esfs.jsonfile has the setting ReadOnly set to 0.If you only need to do restores and do not intend to run new backup or duplication jobs to Cloud Catalyst, then set ReadOnly to 1.
- Start the NetBackup services on the Cloud Catalyst server.
- Once the Cloud Catalyst storage server has come online, you can proceed with restores, backups, or optimized duplication jobs.
Backup or optimized duplication jobs require that ReadOnly is set to 0 in the
esfs.jsonfile. - If running a Cloud Catalyst version older than 8.2 (example: 8.1, 8.1.1, 8.1.2), you may need to deploy a new host name-based certificate for the media server. You can deploy the certificate by running the following command on the primary server:
/usr/openv/netbackup/bin/admincmd/bpnbaz - ProvisionCert <CloudCatalyst host-name>
You must restart the NetBackup services on the Cloud Catalyst server.
- You may need to run the following command to allow Cloud Catalyst to read from the bucket in the cloud storage:
/usr/openv/esfs/bin/setlsu_ioctl <cachedir>/storage/proc/cloud.lsu <bucketname>
No harm is done if you run this command when it is not needed. If you do run the command, you can see the following output:
return code: -1 File exists.
- (Optional) Remove the entire MSDP cloud sub-bucket folder in cloud storage to avoid wasted space and avoid any problems with future migration to MSDP cloud tier server.
The following procedure assumes that the Cloud Catalyst server was reused and or reinstalled as an MSDP cloud tier server or is unavailable for some other reason.
Reverting back to Cloud Catalyst when the server was reused and or reinstalled when the migration was performed
- Stop the NetBackup services on the new MSDP cloud tier server.
- Open the NetBackup web UI.
- Click Recovery. Then click NetBackup catalog recovery.
- Select the catalog backup image that was created before running the nbdecommission -migrate_cloudcatalyst command to migrate Cloud Catalyst to MSDP cloud tier server.
- Complete all steps in the UI to recover the NetBackup catalog.
- Stop and restart the NetBackup services on the primary server.
- Reinstall the Cloud Catalyst server using the same NetBackup version and EEB bundles that were active when migration was performed.
- Then contact Cohesity Technical Support to use the rebuild_esfs process to recover that Cloud Catalyst server from the data in cloud storage. (The rebuild_esfs process supersedes the old drcontrol method of recovering a Cloud Catalyst server. The drcontrol method is deprecated.)
- (Optional) Remove the entire MSDP cloud sub-bucket folder in cloud storage to avoid wasted space and avoid any problems with future migration to MSDP cloud tier server.