Strange error while doing backups - Error: 3041

Question

Strange error while doing backups - Error: 3041

Marios Philippopoulos

SSC Guru

Points: 57190
More actions
January 30, 2010 at 11:55 am

#218705

I am doing backups of a SQL-2008 database-engine instance and I'm getting the following very unhelpful message in the SQL ERRORLOG;
Anyone know how to troubleshoot this?
2010-01-29 22:52:51.96 Backup Error: 3041, Severity: 16, State: 1.
2010-01-29 22:52:51.96 Backup BACKUP failed to complete the command BACKUP DATABASE xxxxxxxxxxx. Check the backup application log for detailed messages.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

3rd party backup tool? Check that application's log.

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 SSC Guru Points: 57190 More actions · Answer 2

It's a native backup using the compression feature (SQL 2008 SP1 Enterprise Ed., v. 10.0.2531).

What is the backup application log?

Here is the full command:

BACKUP DATABASE [xxxx] TO DISK='....\xxx.BAK' WITH NOFORMAT, INIT,

NAME='...', , SKIP, NOREWIND, NOUNLOAD, COMPRESSION, STATS = 10

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

vstitte SSCarpal Tunnel Points: 4475 More actions · Answer 3

vstitte

SSCarpal Tunnel

Points: 4475

January 30, 2010 at 6:04 pm

#1111261

Mario,

Is that the entire error message?

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

If it's a job, are you logging the job output? Might be in there.

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

vstitte SSCarpal Tunnel Points: 4475 More actions · Answer 5

Since you are backing up to a DISK, NOUNLOAD and NOREWIND can be excluded.

Also, it looks like you have an extra comma (,) before SKIP.

Do you get the error when you run the the BACKUP manually? Are you having issue with a specific database or all database?

Marios Philippopoulos SSC Guru Points: 57190 More actions · Answer 6

Thanks all for the responses.

The command is syntactically correct, has run to completion many times before.

I may have missed a comma or two in my earlier post, as I tried to glean the code from the stored procedure we use to automate our backups.

It turns out that COMMVAULT backups to tape were running at the same time as our backups, and COMMVAULT may have been locking the folder containing the backup files. At least that is my theory at the moment.

I have asked our storage team to push the COMMVAULT backups to a starting time just after our db backups are completed, and we will see if this issue re-occurs.

__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]