November 20, 2002 at 6:49 am
I am getting this error from a full backup:
BackupMedium::ReportIoError: write failure on backup device 'F:\SQLDUMPS\Customers\Customers_db_200211200740.BAK'. Operating system error 33(error not found).
The drive is compressed.
Does anyone know why this is happening?
I need to fix this urgently as we have not successfully backed up for 3 days!!
November 20, 2002 at 9:55 am
System Error 33 :
The process cannot access the file because another process has locked a portion of the file. ERROR_LOCK_VIOLATION
I'm not sure if you can put a backup on a compressed drive (did the backup ever work?).
Did you also check the available space on the disk?
November 20, 2002 at 2:23 pm
Thanks for your reply.
Yes, it has worked in the past. The space - well there is enough space for it compressed, but does it create it and then compress it? If it needs to do this, then perhaps there isn't enough space.
I would've thought the error message would be more along the lines of insufficiant disk space though
November 20, 2002 at 6:16 pm
Sometimes theses errors are misleading. Check the Event Viewer Logs to see if anything more specific. Also, with the file rename it then try the backup. Most times you can rename a locked file then when you have time bounce the Server and delete the old file when back up, locks occasionally in Windows, especially on compressed drives, can be hung until the OS restarts.
November 22, 2002 at 12:58 am
Many thanks for your replies.
I deleted the only full backup left on the disk, and after that it seemed to work OK. I don't know whether it was VERITAS (the fil was still marked for archive, even though it had been backed up - I checked), or the fact that it is a compressed drive.
The event log only gave the same error message.
The event log only gave the same error message, so no clues there either.
It has now run twice, so it definitely isn't a space problem.
Again thanks to you all
November 22, 2002 at 4:31 am
I think Veritas may have left file locked, do a search on the forums I do believe I saw some complaints on this before.
October 17, 2007 at 4:02 pm
Hmm, have run many(many, many) backups to compressed drives before. I actually suspect that this problem is more to do with Win2k3/SQL2k5 and dumping a somewhat large database to a compressed drive, as I have the same problem (bombs out at about 80Gb - no file post failure). My guess is the lock gets released on the backup file mid-backup long enough for the compression to kick in, and so the file disappears..
Steve
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply