SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


How to troubleshoot error 3041? "BACKUP failed to complete the command BACKUP DATABASE XXXXX. Check...


How to troubleshoot error 3041? "BACKUP failed to complete the command BACKUP DATABASE XXXXX. Check the backup application log for detailed messages."

Author
Message
Marios Philippopoulos
Marios Philippopoulos
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53806 Visits: 3784
My backups have been failing and I noticed the following in the SQL ERRORLOG


2011-09-21 22:13:49.70 Backup Database backed up. Database: ...
2011-09-21 22:13:50.68 Backup Database backed up. Database: ...
2011-09-21 22:13:51.86 Backup Database backed up. Database: ...
2011-09-21 22:29:25.51 Backup Error: 3041, Severity: 16, State: 1.
2011-09-21 22:29:25.51 Backup BACKUP failed to complete the command BACKUP DATABASE XXXXX. Check the backup application log for detailed messages.


There is no other information as to what might be causing this.
Where is the backup application log??

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables
Persisting SQL Server Index-Usage Statistics with MERGE
Turbocharge Your Database Maintenance With Service Broker: Part 2
george sibbald
george sibbald
SSC Guru
SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)

Group: General Forum Members
Points: 96622 Visits: 13710
thats a darn good question and I don't know why its been made harder to find out something important such as why a backup failed, all the info should be in the errorlog. I can only think that they mean any associated errors that might be in the errorlog (such as OS error 112) or they mean any log file you might have your backup job writing to (log file from a maintenance plan for example).

Otherwise there is in fact no such thing as a 'backup application log'

---------------------------------------------------------------------
Lynn Pettis
Lynn Pettis
SSC Guru
SSC Guru (401K reputation)SSC Guru (401K reputation)SSC Guru (401K reputation)SSC Guru (401K reputation)SSC Guru (401K reputation)SSC Guru (401K reputation)SSC Guru (401K reputation)SSC Guru (401K reputation)

Group: General Forum Members
Points: 401427 Visits: 43425
Are you using native SQL Server backups or are you running a third party backup application (LiteSpeed, et. al.)?

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Marios Philippopoulos
Marios Philippopoulos
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53806 Visits: 3784
george sibbald (9/22/2011)
thats a darn good question and I don't know why its been made harder to find out something important such as why a backup failed, all the info should be in the errorlog. I can only think that they mean any associated errors that might be in the errorlog (such as OS error 112) or they mean any log file you might have your backup job writing to (log file from a maintenance plan for example).

Otherwise there is in fact no such thing as a 'backup application log'


I wanted to say this but didn't originally: makes for a fancy error message with no meaning... :-)

Very frustrating...

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables
Persisting SQL Server Index-Usage Statistics with MERGE
Turbocharge Your Database Maintenance With Service Broker: Part 2
Marios Philippopoulos
Marios Philippopoulos
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53806 Visits: 3784
Lynn Pettis (9/22/2011)
Are you using native SQL Server backups or are you running a third party backup application (LiteSpeed, et. al.)?


I'm using native backups.

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables
Persisting SQL Server Index-Usage Statistics with MERGE
Turbocharge Your Database Maintenance With Service Broker: Part 2
GilaMonster
GilaMonster
SSC Guru
SSC Guru (919K reputation)SSC Guru (919K reputation)SSC Guru (919K reputation)SSC Guru (919K reputation)SSC Guru (919K reputation)SSC Guru (919K reputation)SSC Guru (919K reputation)SSC Guru (919K reputation)

Group: General Forum Members
Points: 919780 Visits: 48854
Job history?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Marios Philippopoulos
Marios Philippopoulos
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53806 Visits: 3784
GilaMonster (9/22/2011)
Job history?


The history log of the failure is not very helpful:

Message
Executed as user: xxxx\xxxx. ..._Content', file 'xxxx' on file 1. [SQLSTATE 01000] (Message 4035) Processed 68 pages for database 'xxxx', file 'xxxx_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP DATABASE successfully processed 3892612 pages in 713.620 seconds (44.685 MB/sec). [SQLSTATE 01000] (Message 3014) Processed 10720 pages for database 'xxxx', file 'xxxx' on file 1. [SQLSTATE 01000] (Message 4035) Processed 7 pages for database 'xxxx', file 'xxxx_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP DATABASE successfully processed 10727 pages in 4.367 seconds (20.121 MB/sec). [SQLSTATE 01000] (Message 3014) Processed 12136 pages for database 'xxxx', file 'xxxx' on file 1. [SQLSTATE 01000] (Message 403... The step failed.


However, I had turned on logging to a txt file for the job step, and that gave me the answer.

We are using a routine to prune old backup files before backing up a database, and the pruning step failed because it was unable to delete a backup file that was locked by another process; I am suspecting that our file-system backup is the "other process" that was locking the file.

Lesson from this: turn on job-step logging, as it will provide more info than the SQL ERRORLOG or job history. :-)

Thanks all for your responses!

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables
Persisting SQL Server Index-Usage Statistics with MERGE
Turbocharge Your Database Maintenance With Service Broker: Part 2
george sibbald
george sibbald
SSC Guru
SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)SSC Guru (96K reputation)

Group: General Forum Members
Points: 96622 Visits: 13710
Marios Philippopoulos (9/22/2011)
GilaMonster (9/22/2011)
Job history?


The history log of the failure is not very helpful:

Message
Executed as user: xxxx\xxxx. ..._Content', file 'xxxx' on file 1. [SQLSTATE 01000] (Message 4035) Processed 68 pages for database 'xxxx', file 'xxxx_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP DATABASE successfully processed 3892612 pages in 713.620 seconds (44.685 MB/sec). [SQLSTATE 01000] (Message 3014) Processed 10720 pages for database 'xxxx', file 'xxxx' on file 1. [SQLSTATE 01000] (Message 4035) Processed 7 pages for database 'xxxx', file 'xxxx_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP DATABASE successfully processed 10727 pages in 4.367 seconds (20.121 MB/sec). [SQLSTATE 01000] (Message 3014) Processed 12136 pages for database 'xxxx', file 'xxxx' on file 1. [SQLSTATE 01000] (Message 403... The step failed.


However, I had turned on logging to a txt file for the job step, and that gave me the answer.

We are using a routine to prune old backup files before backing up a database, and the pruning step failed because it was unable to delete a backup file that was locked by another process; I am suspecting that our file-system backup is the "other process" that was locking the file.

Lesson from this: turn on job-step logging, as it will provide more info than the SQL ERRORLOG or job history. :-)

Thanks all for your responses!


so I was right then!

---------------------------------------------------------------------
Marios Philippopoulos
Marios Philippopoulos
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53806 Visits: 3784
george sibbald (9/22/2011) so I was right then!


Yes! ;-)

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables
Persisting SQL Server Index-Usage Statistics with MERGE
Turbocharge Your Database Maintenance With Service Broker: Part 2
rao2506
rao2506
Valued Member
Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)

Group: General Forum Members
Points: 53 Visits: 339
The problem here is the backup file was locked, we need to close the file.

Steps to close the file:

Computer Management-->>System Tools-->Shared Folders-->>Open Files-->(here we can see our back up file)-->>right click-->>Close Open file

Now take backup, if backup doesn't go through then we need stop the services of client scheduler and client Acceptor

Computer Management-->>Services and Applications-->>Services-->>find the client acceptor and scheduler, stop the services go to backup folder and delete the file, start the services back and take a backup

Cheers...!!!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum









































































































































































SQLServerCentral


Search