Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Deduplication Guide
  3. Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
  4. About Cloud Catalyst migration cacontrol options
NetBackup™ Deduplication Guide

About Cloud Catalyst migration cacontrol options

NetBackup has multiple cacontrol options that help with cleanup of images and help to make the Cloud Catalyst migration more successful.

Note:

Multiple cacontrol command options are not intended to be run directly because running the nbdecommision command activates the cacontrol option. Carefully review all options in Table: cacontrol options.

Table: cacontrol options lists the cacontrol command options that you can use during the Cloud Catalyst migration and how to use those options.

Table: cacontrol options

cacontrol option

Description

buildcloudcatalystobjects

Location:

/usr/openv/pdde/pdcr/bin/cacontrol 
--catalog buildcloudcatalystobjects <lsuname>
<lsuname> = Name of the MSDP Cloud LSU 
that was migrated from CloudCatalyst.

This option creates a lookup table for image sharing after successful migration to the MSDP cloud tier. After migration, this command should be run on the image sharing server and then the services on that server should be restarted.

cleanupcloudcatalystobjects

Location:

/usr/openv/pdde/pdcr/bin/cacontrol 
--catalog cleanupcloudcatalystobjects <lsuname>
<lsuname> = Name of the MSDP Cloud LSU 
that was migrated from CloudCatalyst.

This option removes unused Cloud Catalyst objects from the cloud after successful migration to the MSDP cloud tier server. This command can be run as an optional step which may be run a few days or weeks after the migration. This option cleans up any Cloud Catalyst objects which the new MSDP cloud tier server does not need. Do not run unless confident that the migration was successful since you cannot revert to Cloud Catalyst to access the data once this command is run.

migratecloudcatalyst

Location:

/usr/openv/pdde/pdcr/bin/cacontrol 
--catalog migratecloudcatalyst <lsuname>
<cloudcatalystmaster> <cloudcatalystmedia> 
[skipimagesharing] [start_with]
<lsuname> = Name of the MSDP Cloud LSU 
to be migrated from CloudCatalyst.
<cloudcatalystmaster> = Master server name.
<cloudcatalystmedia> = Media server hostname of 
the CloudCatalyst server to be migrated.
[skipimagesharing] = Flag which indicates to skip 
migrating the image sharing data from CloudCatalyst 
to the new MSDP Cloud LSU.
[start_with] = Indicates the point at which to 
resume a failed migration after the cause 
of the failure has been addressed.

The nbdecommission -migrate_cloudcatalyst command calls this cacontrol command as needed. Do not run this cacontrol directly. Instead, use the nbdecommission -migrate_cloudcatalyst command to perform the migration.

migratecloudcatalyststatus

Location:

/usr/openv/pdde/pdcr/bin/cacontrol 
--catalog migratecloudcatalyststatus <lsuname>
<lsuname> = Name of the MSDP Cloud LSU being 
migrated from CloudCatalyst.

The nbdecommission -migrate_cloudcatalyst command calls this cacontrol command as needed. Do not run this cacontrol directly. Instead, use the nbdecommission -migrate_cloudcatalyst command to perform migration.

Feedback

Was this page helpful?
Previous

About the Cloud Catalyst migration -dryrun option

Next

Reverting back to Cloud Catalyst from a successful migration

Feedback

Was this page helpful?