1. Support
  2. Knowledge base
  3. 100021966

A comprehensive list of solutions for the most common NetBackup for Microsoft SQL Server database agent backup and restore issues

Article: 100021966
Last Published: 2022-10-20
Ratings: 8 0
Product(s): NetBackup & Alta Data Protection

Problem

A comprehensive list of solutions for the most common NetBackup for Microsoft SQL Server database agent backup and restore issues.

Solution

Refer to the following articles to address these issues:

  1. How to restore to an alternate client, same client, with a different DB name, with a move script, to a Cluster, SQL Transaction Logs.
     
  2. How to perform a backup of SQL, SQL in a Cluster, SQL Transaction Logs, and perform a cold backup.
     
  3. Backup or restore failed with error 1, 2, 5, 236. 239, or 58; SQL DB in Loading state after restore due to typing Mistakes in the Backup or Restore Script.
     
    • SQL RESTORE fails with Error 'RESTORE detected an error on page (10244:1799427905) in database "<DatabaseName>" as read from the backup set': https://www.veritas.com/docs/100019281
    • NetBackup for Microsoft SQL Server backups fail with Status Code 239 when attempting to back up a SQL Cluster: https://www.veritas.com/docs/100017117
    • Unable to restore SQL database when the master server is on Unix or Linux: https://www.veritas.com/docs/100019227
    • Other possible causes of backup or restore failures are as follows:
      • SQLHOST keyword in the script is pointing to the wrong host
      • Wrong master name in the script
      • BROWSE CLIENT = <virtual name> instead of the node name
      • SQLHOST specified in capital letters
      • Wrong DB name
      • Wrong SQLINSTANCE keyword in the script
      • BROWSE CLIENT in upper\lower case, must reflect the name in the Master if the Master is Unix
      • Database in loading state after restore: RECOVEREDSTATE was set to NOTRECOVERED
      • An ordinary restore script was used for an alternate client restore, the move script should be used instead
      • BROWSECLIENT keyword is missing
         
  4. Backup or restore fails with error: 2, 5, 23, 58, 48, or backup can hang due to incorrect name resolution or Network issues.
     
    • Explanation of bpclntcmd command options, the system calls being used, and recommended troubleshooting when the commands return errors: https://www.veritas.com/docs/100017942
    • Status Code 23 during client backups or restores, or when loading client properties: https://www.veritas.com/docs/100030186
    • Use the bpclntcmd to troubleshoot the following problems:
      • Incorrect DNS settings
      • Incorrect reverse lookup
      • Missing or incorrect IP address in the host file of the Client, Media or Master server.
         
  5. Backup or restore fails with error 1, 2, 25; restore fails with error 5, or Error "Exclusive access could not be obtained because the database is in use" due to 3rd party application problems.
     
    • Attempts to restore a SQL database fail with a Status Code 5. The NetBackup MS SQL Client "View Status" window shows the following message: "Exclusive access could not be obtained because the database is in use": https://www.veritas.com/docs/100017258
    • Status 995 is reported in the SQL Server error log for SQL Server DB backup using NetBackup SQL Server extension: https://www.veritas.com/docs/100017915
    • After adding a new client to an MS-SQL-Server policy, the new client fails with a Status Code 2 and, in the dbclient log file, the message "The requested name is valid, but no data of the requested type was found" is shown: https://www.veritas.com/docs/100017279
    • Other possible causes for failure:
      • Wrong SA user account password specified in the SQL Agent properties
      • No disk space
         
  6. Backup error 1, 2, 240, 199, Error 2: USER - Operation inhibited by NetBackup for Microsoft SQL Server: Only a full backup can be performed on the master database due to incorrect policies configuration.
     
  7. Backup failed with error 2, 167, backup or restore error 25, and bplist command error 133 due to parameters that can be changed via a GUI.
     
    • Most frequent causes:
      • Changed NetBackup (NBU) client service account to a working one, or one with the correct SQL rights
      • Selected "allow client browse" via Host Properties\Master
      • Added media server host name to client servers list
      • Corrected wrong master name in the client Registry
      • Corrected wrong client name in BAR GUI
    • During an alternate client restore, the error "ERROR Initializing NetBackup Catalog" occurs, launching the SQL Backup History Options GUI: https://www.veritas.com/docs/100016069
       
  8. Backup or restore error 41 or restore failed with error 5 due to needed tuning.
     
  9. Restore failed with error 25 or 13 because the BAR GUI was used to launch the restore instead of SQL Agent GUI.
     

 

Was this content helpful?

Article Languages