Highlighted

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 SQL server 2008

Netbackup version: 7.6.0.1

I have attached the dbclient log (dbclient_log.doc) and the output from from the job (servertest.doc)

We have other W2008 server with SQL server 2008 where netbackup is working.

Any help is appreciated.

//Lasse

 

1 Solution

Accepted Solutions
Accepted Solution!

This is your problem: <16>

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.

View solution in original post

9 Replies
Accepted Solution!

This is your problem: <16>

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.

View solution in original post

Hav u tried bpclntcmd -sv and

Hav u tried bpclntcmd -sv and bpclntcmd -pn from client side. please share output.

Hi   C:\Program

Hi

 

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd.exe -sv
7.6

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd.exe -pn
expecting response from server gov-netbackup3
servertest.sew.de servertest.sew.de 11.16.10.15 59268

 

gov-netbackup3 is our master.

servertest.sew.de is the client.

/Lasse

 

 

Please have a look at my post

Please have a look at my post dated 25 June.

Make sure the account running

Make sure the account running the NetBackup Client service has sysadmin rights on the SQL server, be aware the SYSTEM no longer automatically has this right

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

if backup runs successfully

if backup runs successfully when u execute batch file from client, then try following:

use domain accout having admin privilages to start netbackup client service and netbackup legacy network services.

Also create a role in MS SQL with sysadmin privilages and connect to instance to backup SQL objects using this user and then try to run the backup.

@lafo stopped responding on

@lafo stopped responding on 30 June...

Hi all The issue is

Hi all

The issue is solved.

It was a permission problem

Thanks fpr all help

 

Regards

Lasse

Re: Hi allThe issue is

Hi Lafo,

Am currently experiencing this issue right now. All troubleshooting steps has yield no solution.

Can you please advise how it was resolve at your end? What kind of permmission was fixed?