Please enter search query. Search <product_name> all support & community content...
Last Published: 2019-04-15
Ratings: 5 14
Backup job fails with STATUS CODE: 6 " the backup failed to back up the requested files"
<16> writeToServer: ERR -send() to server on socket failed: An existing connection was forcibly closed bythe remote host.
<16>dbc_put: ERR - writeToServer() failed when sendingkeepalive
Status code 6 can be caused by socket failed errors during client to server and server to client communications. The server could not complete the connection to the client. The accept system call timed out after 60 seconds.
- Follow all steps within the VERITAS NetBackup Troubleshooting Guide or the NetBackup Troubleshooter within the Activity Monitor for this status code before continuing.
- Confirm hardware and software compatibility before continuing. A list of compatible hardware and software may be obtained within the VERITAS NetBackup Release Notes or on the Support Web site.
* If troubleshooting does not resolve the issue, continue with the following:
Look for the following log messages:
Client Log Files:
02:31:51.167 [9012.10256] <16> writeToServer: ERR - send() to server on socket failed: An existing connection was forcibly closed by the remote host.
02:31:51.167 [9012.10256] <16> dbc_put: ERR -writeToServer() failed when sending keepalive
02:31:51.167 [9012.10256]<4> closeApi: entering closeApi.
02:31:51.167 [9012.10256] <4>closeApi: INF - EXIT STATUS 6: the backup failed to back up the requested files
02:26:18 [9012,10164] <4>InitPipeInfo: INF - Using backup image'pasql1.MSSQL7.PASQL1.db.DBNAME~.0.001of001.20050111022618..C'.
02:26:18[9012,10164] <4> Dbbackrec::PerformNBOperation: INF - backup database"DBNAME" to VIRTUAL_DEVICE='VNBU0-9012-10164' with blocksize = 512,maxtransfersize = 65536, buffercount = 1
02:26:18 [9012,10164] <4>Dbbackrec::PerformNBOperation: INF - #Stripes: 1, #Bufs per stripe 1, To:NetBackup on MASTERSERVER
02:26:18 [9012,10164] <4>CDBbackrec::InitDeviceSet(): INF - Created VDI object for SQL Server instance<*DEFAULT*>.
02:31:52 [9012,10256] <32> DBthreads::dbclient: ERR- <VxBSASendData> failed with error <1>. The textfollows:
02:31:52 [9012,10256] CONTINUATION: - Unknown XBSAError
02:31:52 [9012,10256] <32> CDBbackrec::ProcessVxBSAerror: ERR -<ProcessVxBSAError> failed with error <6>. The textfollows:
02:31:52 [9012,10256] CONTINUATION: - The system cannot find the file specified.
02:31:52 [9012,10256] <32>DBthreads::dbclient: ERR - <VxBSAEndData> failed with error <6>. Thetext follows:
02:31:52 [9012,10256] CONTINUATION: - The handle used to associate this call with a previous VxBSAInit() call is invalid.
02:31:53 [9012,10164] <16> CODBCaccess::LogODBCerr: DBMS MSG -ODBC message. ODBC return code <-1>, SQL State <37000>, Message Text<[Microsoft][ODBC SQL Server Driver][SQL Server]Write on'VNBU0-9012
-10164' failed, status = 995. See the SQL Server error log for more details.>
02:31:53 [9012,10164] <16> CODBCaccess::LogODBCerr:DBMS MSG - <[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.>
02:31:53 [9012,10164] <32>Dbbackrec::PerformNBOperation: ERR - Error found executing <backup database"DBNAME" to VIRTUAL_DEVICE='VNBU0-9012-10164' with blocksize = 512,maxtransfersize = 65536,
buffercount = 1>
02:31:54 [9012,10164]<32> CDBbackrec::FreeDeviceSet(): ERR - Error in VDS->Close:0x80770004. The text follows:
02:31:54 [9012,10164] CONTINUATION: - An abort request is preventing anything except termination actions.
02:31:54 [9012,10164] <4> Dbbackrec::Perform: INF - OPERATION#36 of batch Pa_SQL.bch FAILED with STATUS x (0 is normal). Elapsed time =336(336) seconds.
NBSUPPORT Network Statistics:
Failed Connection Attempts = 6325
Segments Received = 3646716382
Segments Retransmitted =1510483
Looking at the TCP statistics above, note that the reset connection is 6629, and the segment retransmitted are at 1510483. Since the default setting for TCPMAXDATARETRANSMISSIONS is 5, it would be reasonable to expect that a 5 to 1ratio or higher would indicate that there are resets because of retransmitted data. Resets are normal and can be expected from either end, given specific circumstances. However, a stable network is essential when backing up software.
It is recommended that the value of TCPMAXDATARETRANSMISSIONS be increased from its default settings. By increasing this value to something like 10 will minimize the occurrence of this issue.
To tune the TCPIP parameters in the registry, use the following procedures:
WARNING:Using Registry Editor incorrectly can cause serious problems that may require that you reinstall your operating system. Microsoft cannot guarantee that problems that result from the incorrect use of Registry Editor can be solved.Use Registry Editor at your own risk. For information about how to edit theregistry, see the "Changing Keys and Values" Help topic in Registry Editor( Regedit.exe) or the "Add and Delete Information in the Registry" and"Edit Registry Data" Help topics in Regedt32.exe. Microsoft recommends that you back up the registry before you edit it. If you are running Windows NTor Windows 2000, Microsoft also recommends that you update your Emergency Repair Disk (ERD).
- Change the TcpMaxDataRetransmissions andTcpMaxConnectRetransmissions to the values below:
- On the Edit menu, click Add Value, and then add the following registry value:
Value Name: TcpMaxDataRetransmissions
Value Name: TcpMaxConnectRetransmissions
Data Type: REG_DWORD
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):