spid52 BackupMedium::ReportIoError: write failure on backup device 'D:.bck'. Operating system error 33(The process...
cannot access the file because another process has locked a portion of the file.). Spid52 Internal I/O request 0x071BCB00: Op: Write, pBuffer: 0x07430000, Size: 983040, Position: 34304170496, UMS: Internal: 0x103, InternalHigh: 0x0, Offset: 0xFCB01A00, OffsetHigh: 0x7, m_buf: 0x07430000, m_len: 983040, m_actualBytes: 0, m_errcode: 33, BackupFile: D:.bck BACKUP failed to complete the command BACKUP DATABASE [EISWEBNEW] TO DISK = N'D:.bck' WITH INIT , NOUNLOAD , NAME = N'EISWEBNEW backup', NOSKIP , STATS = 10, NOFORMAT spid52 Starting up database
I would issue a simple backup, such as the following, to test the backup process and to make sure there is not another problem.
BACKUP DATABASE EISWEBNEW TO DISK = 'D:EISWEBNEW_FULL.bck'
Do you have comments on this Ask the Expert Q&A? Let us know.
Related Q&A from Greg Robidoux
Find out how to restore data from a corrupt database.continue reading
Back up tables from a SQL Server database to a file with these commands.continue reading
Restore backups in SQL Server 2000 and SQL Server 2005 with this command.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.