Ms sql 2005 backup fails, interrupted by 60%

[Ivan_Levkin]

Hello, please help!

- There is a server Netbackup 6.5 on SLES 11 is connected to the tape drive

- There is a MS SQL Server 2005 Ent 64x in which multiple databases

- Backing up the database size of 300 GB run at night, but for some reason today it was slow and interrupted by 60%

Here is a piece of log from the client C:\Program Files\Veritas\NetBackup\logs\dbclient

07:38:59.425 [3040.3704] <4> CODBCaccess::LogODBCerr: INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]60 percent processed.>.

08:33:38.454 [3040.6580] <16> writeToServer: ERR - send() to server on socket failed:

08:33:38.454 [3040.6580] <16> dbc_put: ERR - failed sending data to server

08:33:38.454 [3040.6580] <4> closeApi: INF - EXIT STATUS 6: the backup failed to back up the requested files

08:33:38.564 [3040.6580] <16> VxBSASendData: ERR - Could not do a bsa_put().

While a good log looks like this:

06:11:41.874 [4100.5960] <4> CODBCaccess::LogODBCerr: INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]90 percent processed.>.

06:17:57.434 [4100.4248] <4> finishTarImage: INF - FractionalObjectBytes: 55771623

Can you tell where you can try to find the cause of the failure?

[Manjunath_Rajan]

Refer the below technote :

http://www.symantec.com/business/support/index?page=content&id=TECH37307

[Marianne]

Please post entire dbclient log as File attachement (rename to dbclient.txt).

We also need to know if comms was received on the media server side. For this we need to see the following 2 logs on the media server:
bptm and bpbrm. 
(also rename these files to txt files and post as File attachments.)

[Ivan_Levkin · Accepted solution]

Hello again, as it turned out, the DBA must manually stop the backup, and a long run time was due to the fact that at the same time set up a DBA database reindexing task is very much her ??loads.

Thanks for the quick response!

[Marianne]

Good point - if a backup is failing that used to work before, START with the DBA!