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 host becomes unresponsive
NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide

Snapshot Manager host becomes unresponsive

In certain environments, the NetBackup Snapshot Manager host may become unresponsive during Cloud Instance Protection (CIP) operations.

This issue has been observed on burstable instance types such as Azure B-series and AWS T-series, but not on other instance types like Azure D-series.

When multiple data movers start within a short period during a CIP run, the CPU credits of the burstable NetBackup Snapshot Manager instance can drop to zero. As a result, the host may enter an unresponsive state for a short duration.

This behavior can also occur in Cloud Scale deployments when nodes are configured with B-series instances.

Workaround:

It is recommended not to use burstable instance types (for example, Azure B-series, AWS T-series) for the NetBackup Snapshot Manager host in production environments.

Feedback

Was this page helpful?
Previous

Backup From Snapshot jobs remain in queued state even after resources are increased on Snapshot Manager

Next

Cloud VM Backup From Snapshot job fails with error 20

Feedback

Was this page helpful?