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.