Backup yielding Operatin System Error 33?

A little help please?
I have a 14.2 GB database that has stopped backing up and yields the
following errors in the Event log and SQL Server Log respectively:
Application Event Log
18210 :
BackupMedium::ReportIoError: write failure on backup device 'C:\Program
Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Manual.bak'.
Operating system error 33(The process cannot access the file because another
process has locked a portion of the file.).
SQL Server Error Log:
Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\enDataWH_db_200601042204.BAK
Is there any reasonable way to fix this?
Thanks in advance for your help.
I've seen that message when trying to backup to a compressed volume.
If that's the case, this may help :-
http://support.microsoft.com/?id=231347
HTH. Ryan
"Dave Smith" <DaveSmith@.discussions.microsoft.com> wrote in message
news:255EB00C-6217-4471-BC1B-ECAC8E935F03@.microsoft.com...
>A little help please?
> I have a 14.2 GB database that has stopped backing up and yields the
> following errors in the Event log and SQL Server Log respectively:
> Application Event Log
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device 'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Manual.bak'.
> Operating system error 33(The process cannot access the file because
> another
> process has locked a portion of the file.).
> SQL Server Error Log:
> Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
> 983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
> Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft
> SQL
> Server\MSSQL\BACKUP\enDataWH_db_200601042204.BAK
> Is there any reasonable way to fix this?
> Thanks in advance for your help.
>
|||Dave,
You can try to identify the process that has locked the file. It is
possible that a third party software like tape backup has acquired a read
lock on the file.
1) use "net file " command to see open files
"net file id /close " to close a open file
2) Use third party tools like filemon from sysinternals to do the same
You can also see if there are no active sql server processes or agent jobs
that may be accessing the file.
Another workaround is to rename the existing file and try the backup again
assuming that you are able to rename and there is space for additional backup.
"Dave Smith" wrote:

> A little help please?
> I have a 14.2 GB database that has stopped backing up and yields the
> following errors in the Event log and SQL Server Log respectively:
> Application Event Log
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device 'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Manual.bak'.
> Operating system error 33(The process cannot access the file because another
> process has locked a portion of the file.).
> SQL Server Error Log:
> Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
> 983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
> Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\enDataWH_db_200601042204.BAK
> Is there any reasonable way to fix this?
> Thanks in advance for your help.
>
|||Way to go Ryan!!
That was exactly the problem. Out MSSQL\BACKUP folder was set to be
compressed.
FYI, the job does a DBCC CHECKDB, Full Backup, and Verify. It used to fail
after 38 to 44 minutes. it just succeeded in 18:03!!
YOU are the man!
Thanks a bunch,
Dave Smith
"Ryan" wrote:

> I've seen that message when trying to backup to a compressed volume.
> If that's the case, this may help :-
> http://support.microsoft.com/?id=231347
> --
> HTH. Ryan
>
> "Dave Smith" <DaveSmith@.discussions.microsoft.com> wrote in message
> news:255EB00C-6217-4471-BC1B-ECAC8E935F03@.microsoft.com...
>
>