Log backup failed

Question

Log backup failed

klnsuddu

SSCertifiable

Points: 5836
More actions
July 25, 2009 at 8:42 am

#212583

Hi,
We have log backup scheduled to run every hour. I'm seeing the job history and found it failed once with below error and running fine from next log backup onwards.
Error: 3041, Severity: 16, State: 1.
2009-07-24 02:00:10.56 Backup BACKUP failed to complete the command BACKUP Mydb. Check the backup application log for detailed messages.
2009-07-24 02:00:10.56 spid74 Error: 18204, Severity: 16, State: 1.
2009-07-24 02:00:10.56 spid74 BackupDiskFile::OpenMedia: Backup device 'k:\allBackups\Log\mydb_Log20090724020010.trn' failed to open. Operating system error 2(The system cannot find the file specified.).
I did understand the reason for failure at only one time???

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

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

Steve Jones - SSC Editor SSC Guru Points: 736270 More actions · Answer 1

It was an error writing to disk. Is this a local drive? Any issue writing to disk usually causes the backup process to fail; it's why backups to non-local disks are not recommended.

klnsuddu SSCertifiable Points: 5836 More actions · Answer 2

Hi Steve,

Its clustered resource drive. we have installed Active/Passive clustered sql server 2005 EE 64 bit on windows 2003 64 bit recently. We have a sql group, which has D (data), E(log), F(secondary data file), T(tempDb) & K(backup drive).

I have seen the log backup failure to only for one database Mydb Out of 10 databases twice. After that I did not see any errors & everything going smooth.

Now, How can I know all the drives are healthy?

Do I need to report this to Systems Team?

Where can look to find out the reason for the log backup failure for that particular database?

thanks for your help

ps. One Orange Chip Points: 29422 More actions · Answer 3

klnsuddu (7/25/2009)
Now, How can I know all the drives are healthy?

Check out with your SAN team for monitoring the health of the disks. ALso, is your k drive part of san or a network share? Sometimes changing the path of the backup helps!!

Pradeep Singh

klnsuddu SSCertifiable Points: 5836 More actions · Answer 4

all the Drives are on SAN...Its olny faied twice and I want know why its failed those 2 times?

as soon as I see this error, I ran DBCC CHECKDB for all databases & its giving me NO ERRORS.

Steve Jones - SSC Editor SSC Guru Points: 736270 More actions · Answer 5

I think you'll have to have the SAN team dig in. A SAN network error, disk error, any number of things could have caused it. I'd have ignored it, but you said twice, so I suspect you have a problem somewhere. This isn't a SQL error, it's SQL Server reporting an OS error in writing to disk, or likely in this case, opening/creating the file.

You are using separate files for all backups, correct?

Anything common on the two failures? Time, size, load on server?

klnsuddu SSCertifiable Points: 5836 More actions · Answer 6

thank you,

You are using separate files for all backups, correct?

Yes, every hour the log backup writes to a new file.

Anything common on the two failures? Time, size, load on server?

The first failed backup occured at 2:00 AM in the morning & second failed backup at immediate log backup at 3:00 AM. At 2, 3 am there is no activity at all except log backups...