Backup From Snapshot jobs remain in queued state even after resources are increased on Snapshot Manager
This issue occurs in NetBackup 11.1 environments where parallel stream/read is enabled. Backup from snapshot jobs for grant parent or anchor images may remain in a queued state even after the resource capacity is increased on the Snapshot Manager server. In such cases, the jobs wait for available Memory units per Snapshot Manager Server resources, and the Job Details tab displays the following message:
Limit has been reached for the logical resource <Snapshot Manager Server name>.Cloud.Memory units per CloudPoint
This behavior occurs because the resource limit capability published by the NetBackup Snapshot Manager server may not immediately reflect recent changes in system resources. When the NetBackup Snapshot Manager instance type is modified to increase RAM and/or CPU, or when the number of pods is increased in a Cloud Scale deployment, the updated capability may not be immediately consumed by NetBackup. As a result, the queued jobs continue to wait for resources even though capacity has been increased.
:
Perform the following steps to ensure the updated resource capabilities are detected and used by NetBackup:
Perform a NetBackup Snapshot Manager discovery and allow it to complete. This updates the resource capability data published by the NetBackup Snapshot Manager server.
Start a new backup job for any VM instance. This triggers a refresh of cached resource limit information in the Policy Execution Manager (PEM).
If the issue persists, restart the NetBackup services on the primary server to force a complete reload of the resource capability data.
Note:
The increased or decreased resource capability on the NetBackup Snapshot Manager server may take time to reflect in NetBackup. Performing the above steps ensures that the updated configuration is recognized and utilized during subsequent backup job scheduling.