cancel
Showing results for 
Search instead for 
Did you mean: 

SQL Server transaction backup failed

southlend
Level 2

I'm a beginner in netbackup

<Circumstance>

Master server : Redhat 7.3 in VMware ESXi

Client : Windows2012R2 with MSSQL in VMware ESXi

 

<Problem>

Normal backup and Recovery of MSSQL works well except SQL Server transaction log backup

cf)

I changed recovery model from simple to Full

Database is very small

 

I don't know why and what to do

please help me

 

<Job details in activity monitor>

2019. 6. 19 오후 7:13:31 - Info dbclient (pid=2284) INF - BACKUP STARTED USING
2019. 6. 19 오후 7:13:31 - Info dbclient (pid=2284) Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
2019. 6. 19 오후 7:13:31 - Info dbclient (pid=2284) Feb 20 2014 20:04:26 
2019. 6. 19 오후 7:13:31 - Info dbclient (pid=2284) Copyright (c) Microsoft Corporation
2019. 6. 19 오후 7:13:31 - Info dbclient (pid=2284) Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor) 
2019. 6. 19 오후 7:13:31 - Info dbclient (pid=2284) Batch = C:\Veritas\NetBackup\DbExt\MsSql\shopdb_tran.bch, Op# = 1
2019. 6. 19 오후 7:13:31 - Info dbclient (pid=2284) INF - Using backup image SQLSERVER.MSSQL7.SQLSERVER.trx.ShopDB.~.7.001of001.20190618181214..C
2019. 6. 19 오후 7:13:31 - Info dbclient (pid=2284) INF - backup log "ShopDB" to VIRTUAL_DEVICE='VNBU0-2284-2316-1560906735' with no_truncate,  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
2019. 6. 19 오후 7:13:31 - Info dbclient (pid=2284) INF - Number of stripes: 1, Number of buffers per stripe 2.
2019. 6. 19 오후 7:13:31 - Info dbclient (pid=2284) INF - Created VDI object for SQL Server instance <SQLSERVER>. Connection timeout is <300> seconds.
2019. 6. 19 오후 7:18:31 - Info dbclient (pid=2284) ERR - Error in GetConfiguration: 0x80770003.
2019. 6. 19 오후 7:18:31 - Info dbclient (pid=2284)     CONTINUATION: - The api was waiting and the timeout interval had elapsed.
2019. 6. 19 오후 7:18:31 - Info dbclient (pid=2284) DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <4214><[Microsoft][SQL Server Native Client 11.0][SQL Server]?? ?????? ??? ???? BACKUP LOG? ??? ? ????.>.
2019. 6. 19 오후 7:18:32 - Info dbclient (pid=2284) DBMS MSG - SQL Message <3013><[Microsoft][SQL Server Native Client 11.0][SQL Server]BACKUP LOG?(?) ?????? ?????.>
2019. 6. 19 오후 7:18:32 - Info dbclient (pid=2284) ERR - Error found executing <backup log "ShopDB" to VIRTUAL_DEVICE='VNBU0-2284-2316-1560906735' with no_truncate,  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2>.
2019. 6. 19 오후 7:18:32 - Info dbclient (pid=2284) INF - OPERATION #1 of batch C:\Veritas\NetBackup\DbExt\MsSql\shopdb_tran.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 302(302) seconds.
2019. 6. 19 오후 7:18:34 - Info dbclient (pid=2284) INF - Results of executing <C:\Veritas\NetBackup\DbExt\MsSql\shopdb_tran.bch>: 
2019. 6. 19 오후 7:18:34 - Info dbclient (pid=2284) <0> operations succeeded. <1> operations failed.
2019. 6. 19 오후 7:18:34 - Info dbclient (pid=2284) INF - The following object(s) were not backed up successfully.
2019. 6. 19 오후 7:18:34 - Info dbclient (pid=2284) INF - ShopDB

 

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please have a look at this TN: https://www.veritas.com/support/en_US/article.100009247

If this is not your problem, ensure that dbclient log folder exists on the client and ensure logging is set to level 3.
If backup fails again, see if there is anything other than 'Error in GetConfiguration: 0x80770003' in the log.

View solution in original post

3 REPLIES 3

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please have a look at this TN: https://www.veritas.com/support/en_US/article.100009247

If this is not your problem, ensure that dbclient log folder exists on the client and ensure logging is set to level 3.
If backup fails again, see if there is anything other than 'Error in GetConfiguration: 0x80770003' in the log.

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

also there could be an orphaned BACKUP LOG session from a previously failed log backup. If yes, kill it via MS SQL means or restart the instance.

Regards

Michal

Thank you. I found that it;s because there's no full backup