Forum Discussion

lafo's avatar
lafo
Level 4
11 years ago

SQL backup fail with statuscode 2

Hi We have a 2008 SQL server that we can't backup from the master. It fails wit statuscode 2 Backup from the client works well. Env: Master: Windows 2008 Client : windows 2008 with ...
7.6
Agent for Microsoft SQL Server
Backup and Recovery
NetBackup
Troubleshooting
Windows Server (2003-2008)
  • Marianne's avatar
    Marianne
    11 years ago

    This is your problem:

    <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <87><[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.>

     

    First check is to work with the SQL dba to ensure SQL instance is up and running.

    Check that all info in SQL backup script is correct.
    If Instance and/or database names are specified, check that all are correct.
    Carefully check for typo errors. 
    Check if Client name is correct in the script.

    Lastly, check that NBU Client Service on the SQL server is started as a domain account with sufficient SQL priveleges.
    Best is to start NBU services with same logon account as SQL services.

Marianne's avatar
Marianne
Level 6
11 years ago

This is your problem:

<16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <87><[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.>

 

First check is to work with the SQL dba to ensure SQL instance is up and running.

Check that all info in SQL backup script is correct.
If Instance and/or database names are specified, check that all are correct.
Carefully check for typo errors. 
Check if Client name is correct in the script.

Lastly, check that NBU Client Service on the SQL server is started as a domain account with sufficient SQL priveleges.
Best is to start NBU services with same logon account as SQL services.