September 16, 2003 at 1:25 am
Hi,
I encounter problem when performing full backup. Anyone could help me on this?
BACKUP failed to complete the command BACKUP DATABASE
[MyDB] TO DISK = N'R:\BackUP\ProductionDB_db_200309160801.BAK'
WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
Internal I/O request 0x7EB5BA08: Op: Write, pBuffer: 0x04790000,
Size: 983040, Position: 49639659008, UMS: Internal: 0x103,
InternalHigh: 0x0, Offset: 0x8EC11600, OffsetHigh: 0xB, m_buf:
0x04790000, m_len: 983040, m_actualBytes: 0, m_errcode: 33,
BackupFile: R:\BackUP\ProductionDB_db_200309160801.BAK
BACKUP failed to complete the command BACKUP DATABASE [MyDB]
TO DISK = N'R:\BackUP\ProductionDB_db_200309160801.BAK
' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
--------------------------------------------------------------------------
BACKUP failed to complete the command BACKUP DATABASE [MyDB]
TO DISK = N'R:\BackUP\ProductionDB backup150903.BAK'
WITH INIT , NOUNLOAD , NAME = N'MyDB backup150903', NOSKIP ,
STATS = 10, NOFORMAT
Internal I/O request 0x63D958E8: Op: Write, pBuffer: 0x07060000, Size: 65536,
Position: 47802095104, UMS: Internal: 0x103, InternalHigh: 0x0, Offset:
0x213A1600, OffsetHigh: 0xB, m_buf:
0x07060000, m_len: 65536, m_actualBytes: 0, m_errcode: 33,
BackupFile: R:\BackUP\ProductionDB
BackupMedium::ReportIoError: write failure on backup device
'R:\BackUP\ProductionDB backup150903.BAK'.
Operating system error 33(The process cannot access the file because
another process has locked a portion of the file.).
Thanks in advances!
September 16, 2003 at 10:33 am
Is this everytime you run a full backup? How are you doing this (EM, code?)
could you have multiple backup jobs scheduled?
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
September 16, 2003 at 6:40 pm
Hi Steven,
I did it from both, EM and Backup maintenance plan. Backup operation failed. Please advise.
September 17, 2003 at 4:08 am
The key may be the "Operating system error 33(The process cannot access the file because
another process has locked a portion of the file.)." message.
It would be worthwhile to check what else may be running, including stuff run by your Windows administrators.
On the DBA side, check if multiple jobs are trying to use the same file.
On the Window side, check if a tape archive is running at the same time as your backup. Also check for anything else that may do a similar lock, such as server imaging running. Also try to create another file in the same folder, or if your file already exists, try to delete it.
If you are sure nothing else is using your file but you cannot delete it, then there is almost certainly a Windows lock on the file. If nothing else clears the lock, reboot the box and try again.
"All information provided is a personal opinion that may not match reality"
All information provided is a personal opinion that may not match reality.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
September 17, 2003 at 5:32 am
If you see the URL below:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes.asp
It clearly mentions that this is a Lock_Violation error...Pls check what other processes have a lock on this file..try using some other file or as Ed said restart the box
Cheers!
Arvind
Arvind
Arvind
September 17, 2003 at 10:23 am
Something else you might want to check, is to see if you have compression set on folder you are backing up to. I had a similar error recently where it would backup the database to 90% and then fail. Once we removed the compression option on the folder, the backup finished successfully. Check the properties of the folder and then the advanced button and make sure "compress contents to save disk space" is not checked.
September 17, 2003 at 10:47 am
I've had this problem with Backup Exec when Backup Exec was backing up the folder/file while the DB backup job was running. The solution was to coordinate the EM/Backup Exec backup times so they did not overlap.
September 18, 2003 at 2:20 am
A slightly OT comment on NTFS compression, at least on NT4...
If you copy a file over 2GB over the network to a NTFS compressed folder it is VERY flaky, failing with an error about incomplete writes many more times than it succeeds.
The really nasty bit is somtimes the failure leaves the NTFS MFT corrupt. You do not notice any problem until you next reboot, which can get as far as a blue screen, or may just hang. Either way, you have to rebuild the box.
All information provided is a personal opinion that may not match reality.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply