SQL Server policy backups that use intelligent groups may fail with a status code 200 when the associated credentials in a credential rule are invalid
A SQL Server policy backup can fail with a status code 200 during scheduled backups when the following details apply:
Instances that are associated with the intelligent groups in the policy were discovered and registered using credential rules.
Intelligent groups are used in the policy to query the NetBackup environment for the databases.
A warning message: "No databases were found for instance {0}." can be found in the job details. This message indicates an issue where NetBackup attempted to access the SQL Server instances or databases and the NetBackup asset database appears to be empty.
Error from job details:
Jan 15, 2025 11:45:00 AM - Info nbjm (pid=3606803) starting backup job (jobid=5) for
client <mssql_client>, policy <mssql_auto_protect_policy>, schedule Full
Jan 15, 2025 11:45:00 AM - Info nbjm (pid=3606803) requesting MEDIA_SERVER_ONLY resources
from RB for backup job (jobid=5, request id:{71277C90-D368-11EF-A88B-C711544AD613})
Jan 15, 2025 11:45:00 AM - requesting resource <media_bdstu>
Jan 15, 2025 11:45:00 AM - requesting resource <media_server>.NBU_CLIENT.MAXJOBS.
<media_server>
Jan 15, 2025 11:45:00 AM - granted resource <media_server>.NBU_CLIENT.MAXJOBS.
<media_server>
Jan 15, 2025 11:45:00 AM - estimated 0 kbytes needed
Jan 15, 2025 11:45:00 AM - begin Parent Job
Jan 15, 2025 11:45:00 AM - begin Application Resolver: Step By Condition
Operation Status: 0
Jan 15, 2025 11:45:00 AM - end Application Resolver: Step By Condition; elapsed time
0:00:00
Jan 15, 2025 11:45:00 AM - begin Application Resolver: Resolver Discovery
Jan 15, 2025 11:45:01 AM - Warning nbpem (pid=3606866) No databases were found
for instance {0}.
Jan 15, 2025 11:45:01 AM - Error nbpem (pid=3606866) backup of client <mssql_client>
exited with status 200 (The scheduler found that no backups are due. Or, the target
hosts do not need to be upgraded.)
Operation Status: 0
Jan 15, 2025 11:45:01 AM - end Application Resolver: Resolver Discovery; elapsed time
0:00:01
Jan 15, 2025 11:45:01 AM - begin Application Resolver: Policy Execution Manager
Preprocessed
Operation Status: 200
Jan 15, 2025 11:45:01 AM - end Application Resolver: Policy Execution Manager
Preprocessed; elapsed time 0:00:00
Jan 15, 2025 11:45:01 AM - begin Application Resolver: Stop On Error
Operation Status: 0
Jan 15, 2025 11:45:01 AM - end Application Resolver: Stop On Error; elapsed time 0:00:00
Operation Status: 200
Jan 15, 2025 11:45:01 AM - end Parent Job; elapsed time 0:00:01
The scheduler found that no backups are due. Or, the target hosts do not need to be
upgraded.(200)Any supported Windows version
Any supported SQL Server version
NetBackup 11.0 or later
An issue exists with the credentials that are configured in the credential rule. The rule may contain an invalid username or password. Or, the user does not have the necessary permissions to access the instances or databases. This situation can occur because NetBackup does not validate a credential when the credential rule is created. Consider a case where a NetBackup administrator receives a request from the SQL Server administrator to create a credential rule. Later when the SQL Server administrator activates the credential rule, that administrator finds that the credential that was selected for the rule has an outdated username or password.
Validate the configured credentials for the SQL Server instances or databases that are included in the policy.
To validate the credentials
- On the Instances tab, select the check box for instance.
- Select Manage credentials.
- Select the option Select from existing credentials.
- Select the credential that is associated with the credential rule.
- Select Next.
- Review the messages that the validation displays. Then modify the credential as needed.