spid52 BackupMedium::ReportIoError: write failure on backup device 'D:.bck'. Operating system error 33(The process...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
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
Synchronize databases on separate servers without using SANs. Learn options for server failover in SQL Server including log shipping, database ...continue reading
Restore backups in SQL Server 2000 and SQL Server 2005 with this command.continue reading
Avoid restoring your SQL Server database to solve the SQL Server error message "server out of memory." The problem could be the memory settings.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.