Backup jobs fail with error 2060017 when Snapshot Manager is configured with Kubernetes extensions
This issue occurs in NetBackup 11.1 environments where the Snapshot Manager is configured with Kubernetes extensions. Backup jobs may intermittently fail with error code 2060017 when they are scheduled to execute on the Snapshot Manager host and required resources are unavailable. In Kubernetes-integrated environments, Snapshot Manager publishes a cumulative capability combining the Snapshot Manager host and Kubernetes extension resources. When the data mover workflow launches on the Snapshot Manager host, the required resources might not be locally available, resulting in the failure.
:
Limit the number of concurrent jobs on the Snapshot Manager host to reduce resource contention.
Perform the following steps on the Snapshot Manager host:
Open the following file for editing:
/usr/openv/var/global/flexsnap.confAdd or update the following section:
[capability_limit]
max_jobs=1
Save the file and restart the Snapshot Manager service:
systemctl restart nbsm
After applying the change, monitor job success rates and resource utilization. Adjust the max_jobs value as needed based on workload and available resources.
Note:
This workaround applies only to environments where Snapshot Manager is configured with Kubernetes extensions and backup jobs fail with error code 2060017 when scheduled on the Snapshot Manager host.