Backup fail SQL server 2005

I keep running into error messages while trying to run a backup using SQL server 2005. Running the backup task is working alright but when I try to run a backup of the transaction logs I keep running into errors.

Here's the error messages.

Error: 18210, Severity: 16, State: 1.
2008-10-21 13:42:11.68 spid51      BackupMedium::ReportIoError: write failure on backup device 'F:\Backup\%mybackupfile%.trn'. Operating system error 1117(The request could not be performed because of an I/O device error.).
2008-10-21 13:42:11.68 Backup      Error: 3041, Severity: 16, State: 1.
2008-10-21 13:42:11.68 Backup      BACKUP failed to complete the command BACKUP LOG %mybackuplog%. Check the backup application log for detailed messages.
bkort1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Daniel WilsonCommented:
Is the f: disk full?  Or close enough to full that the free space < the size of the LDF file?
0
bkort1Author Commented:
No the f: drive has plenty of room, we tried other locations as well with no success.  Any suggestions?
0
Daniel WilsonCommented:
In your System Event Log, are you logging any other disk-related problems?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

grayeCommented:
The fact that the error message contains "%mybackupfie%" is a bit suspicious to me... it looks like it's not evaluating the environmental variable.
... or did  you just do that for posting it here?
0
bkort1Author Commented:
Actually I put "%mybackupfie%" just for posting here.

I am pretty sure that the problem has been solved, since the last two backups have been successful.
One of the databases was set to "simple" in the recovery model, I changed it to "full", and made sure they were all set at the right compatibility level.  Its working alright for now.
0
Daniel WilsonCommented:
>>I am pretty sure that the problem has been solved

Cool.  Would you share the solution so we all learn?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.