Video Screencast Help

SQL backup is failing

Created: 09 Jan 2013 • Updated: 09 Jan 2013 | 27 comments
RohitNayal's picture

 

Hi All ,
 
I am trying to configure the SQL backup on our SQL server which is in SQL Cluster .
 
NBU Master \ NBU Media -- Windows 2008 R2 \ NBU 7.5.0.4
 
Client -- Windows 2008 R2 \ NBU 7.5.0.4
 
Netbackup client service is running with one of the AD account and that account is added from Windows as well as SQL end , from Windows end that account is added into Administrator group and in the SQL Logins user id is having dbcreator and sysadmin roles , attaching the dbclient and bphdb logs , also I check there is no multiple dbchecx process are running 
 

Comments 27 CommentsJump to latest comment

Nagalla's picture

 

16:01:54.259 [15948.16636] <2> do_pbx_service: [vnet_connect.c:2116] via PBX bprd CONNECT FROM 10.66.30.4.55971 TO 10.66.30.11.1556 fd = 1256
16:01:54.259 [15948.16636] <2> async_connect: [vnet_connect.c:1644] connect async CONNECT FROM 10.66.30.4.55971 TO 10.66.30.11.1556 fd = 1256
16:01:54.259 [15948.16636] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO whbrtwnbu01 10.66.30.11 bprd VIA pbx
16:01:54.259 [15948.16636] <2> logconnections: BPRD CONNECT FROM 10.66.30.4.55971 TO 10.66.30.11.1556 fd = 1256
16:01:54.259 [15948.16636] <2> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:843] Assuming no VxSS for DB Agents 0 0x0
16:01:56.349 [15948.16636] <16> writeToServer: ERR - send() to server on socket failed:
16:01:56.349 [15948.16636] <16> dbc_RemoteWriteFile: ERR - could not write progress status message to the NAME socket

 

Looks like its not able to communicate with master server.

what is the below command output in Client, it will tell you if client able to connet the master server or not

bpcltncmd -pn

if it did not return anyting..

you may need to check your hosts and registory entiries.

 

RohitNayal's picture

 

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -pn
expecting response from server XXXXXXXX
XXXXXXX YYYYYY  10.66.x.x 55281
 
 
Also I would like to mentioned that File system backup is running fine , facing issue only with SQL Backups.

Regards,

Rohit

Will Restore's picture

Check your setup

 

16:12:56.476 [4364.4464] <16> CDBbackrec::CDBbackrec: USER - Verify that an active SQL Server policy exists for this client

16:12:58.582 [4364.4464] <8> VxBSADeterminePolicy: WARNING - NBBSA_CLIENT_HOST name= <WHBRTWSQLBC01> differs from NBU config name= <whbrtwssc01>
 

 

You may need to create this file on your Master server

C:\Program Files\Veritas\NetBackup\db\altnames\No.Restrictions

 

Will Restore -- where there is a Will there is a way

RohitNayal's picture

Issue still persist after creating the file 

Regards,

Rohit

Marianne's picture

Please show us your backup script.

Which hostname is physical nodename and which one is virtual hostname? (WHBRTWSQLBC01 / whbrtwssc01 )
Which hostname is defined in backup policy?

Seems these errors can be ignored:

 

16:01:56.349 [15948.16636] <16> writeToServer: ERR - send() to server on socket failed:
16:01:56.349 [15948.16636] <16> dbc_RemoteWriteFile: ERR - could not write progress status message to the NAME socket

See TN: http://www.symantec.com/docs/TECH182435

Other errors in dbclient log:

 

 <16> CDBbackrec::InitDeviceSet_Part2(): ERR - Error in GetConfiguration: 0x80770003.

 

<16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3201><[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'VNBU0-15948-9352-1357747320'. Operating system error 0x80070002(The system cannot find the file specified.).>.

 

<16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.>

These errors look like SQL errors - not NBU. 
Have you checked Event Viewer Application log as well as SQL Error log?

I always recommend to run NBU Client Service account with the same logon account that is used for SQL services.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

RohitNayal's picture

Physcial Host name : whbrtwssc01

 

SQL Cluster Name : WHBRTWSQLBC01 

 

Attching the backup script also , due to security reason we cann't run the SQL services and NBU services from the same account .

 

Also attching the Event vwr logs

AttachmentSize
full2.txt 1.04 KB
Event Vwr Log.txt 1.24 KB

Regards,

Rohit

Marianne's picture

Script looks good.

Please ask your SQL dba to have a look at the error in Application log. This is not NBU error...

They should also check SQL Error and VDI logs.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

RohitNayal's picture

Un fortunately as per SQL team issue is with NBU , could you please let me know where I have to point that needs to be taken into considerations by SQL team

Regards,

Rohit

Mark_Solutions's picture

Just a few basics here to make sure things were right from the start ...

1. On the client have you opened the NBU SQL Agent GUI and set the authentication to the SQL Database - it is this that gets used rather than the client service when doing the backup - I am guessing that you have as the script has been produced but wanted to double check

2. Can the client communicate with the Master Server properly - all file system backups only communicate with the Media Servers - SQL backups are different as they communicate directly with the Master before they communicate with the Media Servers

3. As Marianne says check the clients event logs - unusual for 2008R2 to have such issues but worth checking it is up to date with all patches / hotifxes from Microsoft etc.

4. Your first posted log also indicates that a connection is forcibly closed - it effectively times out after 5 minutes whilst preparing the script - please increase the client read timeout on your Master and Media Servers - the log indicates it is set to 300 so try 1800 for now

5. In view of the client name difference shown i am wondering if this is a clustered server? If so have you set the Agent GUI authentication on both nodes? Does the policy use the Virtual name?

Hope this helps / guides you

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Marianne's picture

Have a look at this Microsoft forum discussion - especially George M Jones with W2008 and SQL 2005 in 2-node cluster:

http://social.msdn.microsoft.com/forums/en-US/sqldatabaseengine/thread/2df560fe-0c4d-4ce6-a651-3abfcbf62574 

See how he managed to fix the problem in his last post...

No idea if this is applicable to your environment, but try to convince the SQL DBAs that you need to work together to find a solution.
Check SQL Error and VDI logs for additional info.

Have you tried to log into SQL GUI interface as the same user used for NBU services, and do a backup to local disk? Is that working fine?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

bharatgangawane's picture

Please check the with DBA team the path are exist on destination server where u doing a restoration.

As we check the dbclient log it shows the below error.

"<16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3201><[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'VNBU0-15948-9352-1357747320'. Operating system error 0x80070002(The system cannot find the file specified.).>." 

 

Regards

Bharat

Will Restore's picture

== update ==

OK, try this

NetBackup Management > Host Properties

Action > Configure Client

  enter the physical client name

Client Properties > Client name

  enter the virtual computer name

OK

 

Run the backup job again

 

Will Restore -- where there is a Will there is a way

RohitNayal's picture

Hi All ,

 

I just found that the nslookup forward and backward is running fine for the Virtual cluster name , but when I try to connect the host property of the virtual server its showing , connection refused , but both my physical host are able to connect with the client host property 

Regards,

Rohit

Will Restore's picture

sorry, try my updated directions above

Will Restore -- where there is a Will there is a way

RohitNayal's picture

Backup is still failing with EC 59 , 

Regards,

Rohit

Nagalla's picture

backup is failing with EC 59?

are you able to make the file system backups?

do you have the correct server entires made in registory of client

please provide the bpcd log.

if you dont have the log.

create a bpcd directory in client /installpath/veritas/netbackup/logs/bpcd 

and then try backup, and provide the bpcd log 

RohitNayal's picture

Hi Nagalla,

 

As I mentioned earlier File system backup is running fine only problem I am facing is that configuring the SQL backup via the virtual cluster name , from master server (media server also) I can ping the virtual cluster name and connect on vnetd port only issue is I am facing is that the when ever I kick start the SQL backup its getting failed , even I checked on both the physical machine registry settings master server name is available .

Regards,

Rohit

Will Restore's picture

Attach current logs, please: bphdb, bpclient, bpcd

 

Will Restore -- where there is a Will there is a way

Dyneshia's picture

WR -> you should probably create a seperate thread for you issue.

Will Restore's picture

I am asking Rohit to provide currrent logs.  Doesn't make sense to open new thread for ongoing issue.

Will Restore -- where there is a Will there is a way

Will Restore's picture

As for Status 59, please revisit requirements

 

NetBackup status code: 59

Message: access to the client was not allowed

 

Explanation: The master or the media server tries to access the client, but the

client does not recognize the server as a valid server.

 

If the server is a valid server, verify that it is in the server list on the client. If

necessary add it as follows:

■ On Windows clients: Add the server on the Server to use for backups and

restores drop-down in the Specify NetBackup Machines and Policy Type

dialog box. To display this dialog box, start the Backup, Archive, and Restore

interface on the client. Then click SpecifyNetBackupMachinesandPolicy

Type on the File menu.

 

Will Restore -- where there is a Will there is a way

RohitNayal's picture

Hi All ,

 

Issue is resolved as client is instead of using the backup LAN for connecting the master \media server , using  the Management network , due to which backup is failing .

 

Want to say thanks all of them for providing me valuable feedback and suggestion 

 

Regards,

Rohit

Marianne's picture

First time you mentioned backup LAN?

If we knew from the start we would've referred you to this section in NBU for SQL manual:

 

About using SQL Server in a cluster with a multi-interface network connection (multi-NIC)
 
This section contains detailed instructions and examples.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

RohitNayal's picture

Apology Mariane , I forgot to add this information in my query . but still I am not clear as in our environment DNS is available,  forward and reverse lookup is also running fine then why I need to add the master server entry  on the client machine , but after adding those it works 

Regards,

Rohit

Marianne's picture

then why I need to add the master server entry  on the client machine

Where did you need to add master server entry?
In hosts file?

Did you test forward and reverse lookup for backup NICs / IPs?
Are there different hostnames for the backup IPs in DNS?

Did you go through the section in the manual to config cluster backups for backup network?

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

RohitNayal's picture

I need to add the entry of the master server into the both physical client , yes I test the forward and reverse lookup and the thing which I am missing that on forward lookup its showing the IP of primary network not backup network , so when I explicitly add the master server backup IP into the host file of client now communication from client to master server is running through backup interface .

 

I agree I need to look on those small things even I missed those messages on bpcd logs .

Regards,

Rohit

Marianne's picture

..... the thing which I am missing that on forward lookup its showing the IP of primary network not backup network ...

This means that backup network was not added to DNS. 

That is why it is working after you added it to hosts file.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links