Tuesday, March 27, 2012

Backup Failed

SQL 2K
We are having an issue with our data warehouse database failing on backup
with
2005-01-23 09:53:25.64 spid55 BackupMedium::ReportIoError: write failure
on backup device
'D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_db_20050123 0900.BAK'. Operating
system error 33(The process cannot access the file because another process
has locked a portion of the file.).
2005-01-23 09:53:25.67 spid55 Internal I/O request 0x3D80DAE8: Op: Write,
pBuffer: 0x153C0000, Size: 983040, Position: 47255394816, UMS: Internal:
0x103, InternalHigh: 0x0, Offset: 0xA41A00, OffsetHigh: 0xB, m_buf:
0x153C0000, m_len: 983040, m_actualBytes: 0, m_errcode: 33, BackupFile:
D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_db_200501230 900.BAK
2005-01-23 09:53:25.69 backup BACKUP failed to complete the command
BACKUP DATABASE [INFO_PROD] TO DISK =
N'D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_db_2005012 30900.BAK' WITH INIT ,
NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
Last week we had the same issue and rebooting the server did helped.
Any thoughts on this lock on the backup file.
Thanks
Robert
Are you backing up the file to tape? Could that process be running while
you are trying to backup the database to disk?
Keith
"MS User" <sqlman@.sql.com> wrote in message
news:%23q5TNsiAFHA.3860@.TK2MSFTNGP11.phx.gbl...
> SQL 2K
> We are having an issue with our data warehouse database failing on backup
> with
>
> 2005-01-23 09:53:25.64 spid55 BackupMedium::ReportIoError: write
failure
> on backup device
> 'D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_db_20050123 0900.BAK'. Operating
> system error 33(The process cannot access the file because another process
> has locked a portion of the file.).
> 2005-01-23 09:53:25.67 spid55 Internal I/O request 0x3D80DAE8: Op:
Write,
> pBuffer: 0x153C0000, Size: 983040, Position: 47255394816, UMS: Internal:
> 0x103, InternalHigh: 0x0, Offset: 0xA41A00, OffsetHigh: 0xB, m_buf:
> 0x153C0000, m_len: 983040, m_actualBytes: 0, m_errcode: 33, BackupFile:
> D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_db_200501230 900.BAK
> 2005-01-23 09:53:25.69 backup BACKUP failed to complete the command
> BACKUP DATABASE [INFO_PROD] TO DISK =
> N'D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_db_2005012 30900.BAK' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
>
> Last week we had the same issue and rebooting the server did helped.
> Any thoughts on this lock on the backup file.
> Thanks
> Robert
>
|||Hi
Anti-Virus and Backup software can hold locks on a file. Check that AV
excludes the SQL files (.MDF, LDF, NDF and BAK)
Check if your backup software is still running it's backup (some badly
behaved backup agents don't release locks if the backup aborts).
Regards
Mike
"MS User" wrote:

> SQL 2K
> We are having an issue with our data warehouse database failing on backup
> with
>
> 2005-01-23 09:53:25.64 spid55 BackupMedium::ReportIoError: write failure
> on backup device
> 'D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_db_20050123 0900.BAK'. Operating
> system error 33(The process cannot access the file because another process
> has locked a portion of the file.).
> 2005-01-23 09:53:25.67 spid55 Internal I/O request 0x3D80DAE8: Op: Write,
> pBuffer: 0x153C0000, Size: 983040, Position: 47255394816, UMS: Internal:
> 0x103, InternalHigh: 0x0, Offset: 0xA41A00, OffsetHigh: 0xB, m_buf:
> 0x153C0000, m_len: 983040, m_actualBytes: 0, m_errcode: 33, BackupFile:
> D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_db_200501230 900.BAK
> 2005-01-23 09:53:25.69 backup BACKUP failed to complete the command
> BACKUP DATABASE [INFO_PROD] TO DISK =
> N'D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_db_2005012 30900.BAK' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
>
> Last week we had the same issue and rebooting the server did helped.
> Any thoughts on this lock on the backup file.
> Thanks
> Robert
>
>

No comments:

Post a Comment