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™ Snapshot Manager for Cloud Install and Upgrade Guide
  3. Section II. NetBackup Snapshot Manager for Cloud maintenance
  4. Troubleshooting NetBackup Snapshot Manager for Cloud
  5. Snapshot Manager failed to retrieve the specified cloud domain(s), against the specified plugin instance
NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide

Snapshot Manager failed to retrieve the specified cloud domain(s), against the specified plugin instance

This issue is observed when the docker/podman daemon is restarted without gracefully stopping the NetBackup Snapshot Manager. This causes the container IP's to be mismatched, due to which the communication/resolution of NetBackup Snapshot Manager services fail.

Workaround:

Perform the following:

  • To restart the Container Manager daemon, gracefully stop the NetBackup Snapshot Manager services by running the following command:

    flexsnap_configure stop

    This would stop all theNetBackup Snapshot Manager services in correct order, which would prevent any errors occurring from stopping or restarting of the Container Manager daemon.

  • Restart the Container Manager daemon and proceed to start the NetBackup Snapshot Manager services using the following command:

    flexsnap_configure start

    This command would start all the NetBackup Snapshot Manager services in the correct order while maintaining the communication between the services.

  • In case the Container Manager daemon has been restarted, without gracefully stopping the NetBackup Snapshot Manager services, the user should run the following command:

    flexsnap_configure restart

    This would stop and start services in the correct order hence ensuring that NetBackup Snapshot Manager works correctly.

Feedback

Was this page helpful?
Previous

Restore from snapshot of a VM with security type Trusted Launch fails

Next

Issues with SELinux configuration

Feedback

Was this page helpful?