Backing up a large '78 GB' database to a compressed folder
gives this error: BackupMedium::ReportIoError: write
failure on backup device '*replaced file name here*.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.). The BAK file size should be about 66 GB. This
backup works if the target is an uncompressed folder on
the same drive, and it did work the first time it was used
to the compressed drive. The system reports over 100 GB
free space on this drive.Have a look at the KB article:
INF: SQL Server Databases Not Supported on Compressed Volumes
# 231347
http://support.microsoft.com/?id=231347
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Warren" <bauerwa@.wsdot.wa.gov> wrote in message
news:00ef01c3d947$a43136e0$a601280a@.phx.gbl...
> Backing up a large '78 GB' database to a compressed folder
> gives this error: BackupMedium::ReportIoError: write
> failure on backup device '*replaced file name here*.BAK'.
> Operating system error 33(The process cannot access the
> file because another process has locked a portion of the
> file.). The BAK file size should be about 66 GB. This
> backup works if the target is an uncompressed folder on
> the same drive, and it did work the first time it was used
> to the compressed drive. The system reports over 100 GB
> free space on this drive.sql
Showing posts with label backupmediumreportioerror. Show all posts
Showing posts with label backupmediumreportioerror. Show all posts
Thursday, March 29, 2012
Backup fails with Operating system error 33
Backing up a large '78 GB' database to a compressed folder
gives this error: BackupMedium::ReportIoError: write
failure on backup device '*replaced file name here*.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.). The BAK file size should be about 66 GB. This
backup works if the target is an uncompressed folder on
the same drive, and it did work the first time it was used
to the compressed drive. The system reports over 100 GB
free space on this drive.Have a look at the KB article:
INF: SQL Server Databases Not Supported on Compressed Volumes
# 231347
http://support.microsoft.com/?id=231347
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Warren" <bauerwa@.wsdot.wa.gov> wrote in message
news:00ef01c3d947$a43136e0$a601280a@.phx.gbl...
gives this error: BackupMedium::ReportIoError: write
failure on backup device '*replaced file name here*.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.). The BAK file size should be about 66 GB. This
backup works if the target is an uncompressed folder on
the same drive, and it did work the first time it was used
to the compressed drive. The system reports over 100 GB
free space on this drive.Have a look at the KB article:
INF: SQL Server Databases Not Supported on Compressed Volumes
# 231347
http://support.microsoft.com/?id=231347
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Warren" <bauerwa@.wsdot.wa.gov> wrote in message
news:00ef01c3d947$a43136e0$a601280a@.phx.gbl...
quote:
> Backing up a large '78 GB' database to a compressed folder
> gives this error: BackupMedium::ReportIoError: write
> failure on backup device '*replaced file name here*.BAK'.
> Operating system error 33(The process cannot access the
> file because another process has locked a portion of the
> file.). The BAK file size should be about 66 GB. This
> backup works if the target is an uncompressed folder on
> the same drive, and it did work the first time it was used
> to the compressed drive. The system reports over 100 GB
> free space on this drive.
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_d
b_200501230900.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
_200501230900.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_200501230900.BAK' WITH INIT ,
NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
Last w
we had the same issue and rebooting the server did helped.
Any thoughts on this lock on the backup file.
Thanks
RobertAre 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_d
b_200501230900.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
_200501230900.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_200501230900.BAK' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
>
> Last w 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 failur
e
> on backup device
> 'D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_d
b_200501230900.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: Writ
e,
> 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
_200501230900.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_200501230900.BAK' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
>
> Last w we had the same issue and rebooting the server did helped.
> Any thoughts on this lock on the backup file.
> Thanks
> Robert
>
>
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_d
b_200501230900.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
_200501230900.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_200501230900.BAK' WITH INIT ,
NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
Last w
we had the same issue and rebooting the server did helped.Any thoughts on this lock on the backup file.
Thanks
RobertAre 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_d
b_200501230900.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
_200501230900.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_200501230900.BAK' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
>
> Last w
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 failur
e
> on backup device
> 'D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_d
b_200501230900.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: Writ
e,
> 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
_200501230900.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_200501230900.BAK' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
>
> Last w
we had the same issue and rebooting the server did helped.> Any thoughts on this lock on the backup file.
> Thanks
> Robert
>
>
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_200501230900.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_200501230900.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_200501230900.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
RobertAre 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_200501230900.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_200501230900.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_200501230900.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_200501230900.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_200501230900.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_200501230900.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
>
>
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_200501230900.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_200501230900.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_200501230900.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
RobertAre 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_200501230900.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_200501230900.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_200501230900.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_200501230900.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_200501230900.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_200501230900.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
>
>
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_d
b_200501230900.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
_200501230900.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_200501230900.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
RobertAre 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_d
b_200501230900.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
_200501230900.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_200501230900.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 failur
e
> on backup device
> 'D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_d
b_200501230900.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: Writ
e,
> 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
_200501230900.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_200501230900.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
>
>
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_d
b_200501230900.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
_200501230900.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_200501230900.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
RobertAre 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_d
b_200501230900.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
_200501230900.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_200501230900.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 failur
e
> on backup device
> 'D:\SqlData\MSSQL$WAREHOUSE1\BACKUP\My_d
b_200501230900.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: Writ
e,
> 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
_200501230900.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_200501230900.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
>
>
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
>
>
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
>
>
Sunday, March 25, 2012
Backup Error
After applying Win2K SP3 earlier this month, our Veritas
tape backups started failing with the following errors:
BackupMedium::ReportIoError: write failure on backup
device 'VNBU0-2000-2912'. Operating system error 995(The
I/O operation has been aborted because of either a thread
exit or an application request.).
Internal I/O request 0x4431FAE8: Op: Write, pBuffer:
0x28A70200, Size: 512, Position: 0, UMS: Internal:
0x65E5A030, InternalHigh: 0x0, Offset: 0x1, OffsetHigh:
0x4862F628, m_buf: 0x00000012, m_len: 1, m_actualBytes: 0,
m_errcode: 995, BackupFile: VNBU0-2000-2912
I also started getting the following error reported around
the same time of day:
The SQL Server cannot obtain a LOCK resource at this time.
Rerun your statement when there are fewer active users or
ask the system administrator to check the SQL Server lock
and memory configuration..
I am able to do a regular dump to disk with no errors.
Any ideas on resolution here?
Thanks for your time.
MilesI think veritas.com will have more helpful info.
Are you using BackupExec to backup SQL databases?
"Miles" <miles.schor@.echostar.com> wrote in message
news:016b01c36742$ecf70520$a401280a@.phx.gbl...
> After applying Win2K SP3 earlier this month, our Veritas
> tape backups started failing with the following errors:
> BackupMedium::ReportIoError: write failure on backup
> device 'VNBU0-2000-2912'. Operating system error 995(The
> I/O operation has been aborted because of either a thread
> exit or an application request.).
> Internal I/O request 0x4431FAE8: Op: Write, pBuffer:
> 0x28A70200, Size: 512, Position: 0, UMS: Internal:
> 0x65E5A030, InternalHigh: 0x0, Offset: 0x1, OffsetHigh:
> 0x4862F628, m_buf: 0x00000012, m_len: 1, m_actualBytes: 0,
> m_errcode: 995, BackupFile: VNBU0-2000-2912
> I also started getting the following error reported around
> the same time of day:
> The SQL Server cannot obtain a LOCK resource at this time.
> Rerun your statement when there are fewer active users or
> ask the system administrator to check the SQL Server lock
> and memory configuration..
> I am able to do a regular dump to disk with no errors.
> Any ideas on resolution here?
> Thanks for your time.
> Miles
tape backups started failing with the following errors:
BackupMedium::ReportIoError: write failure on backup
device 'VNBU0-2000-2912'. Operating system error 995(The
I/O operation has been aborted because of either a thread
exit or an application request.).
Internal I/O request 0x4431FAE8: Op: Write, pBuffer:
0x28A70200, Size: 512, Position: 0, UMS: Internal:
0x65E5A030, InternalHigh: 0x0, Offset: 0x1, OffsetHigh:
0x4862F628, m_buf: 0x00000012, m_len: 1, m_actualBytes: 0,
m_errcode: 995, BackupFile: VNBU0-2000-2912
I also started getting the following error reported around
the same time of day:
The SQL Server cannot obtain a LOCK resource at this time.
Rerun your statement when there are fewer active users or
ask the system administrator to check the SQL Server lock
and memory configuration..
I am able to do a regular dump to disk with no errors.
Any ideas on resolution here?
Thanks for your time.
MilesI think veritas.com will have more helpful info.
Are you using BackupExec to backup SQL databases?
"Miles" <miles.schor@.echostar.com> wrote in message
news:016b01c36742$ecf70520$a401280a@.phx.gbl...
> After applying Win2K SP3 earlier this month, our Veritas
> tape backups started failing with the following errors:
> BackupMedium::ReportIoError: write failure on backup
> device 'VNBU0-2000-2912'. Operating system error 995(The
> I/O operation has been aborted because of either a thread
> exit or an application request.).
> Internal I/O request 0x4431FAE8: Op: Write, pBuffer:
> 0x28A70200, Size: 512, Position: 0, UMS: Internal:
> 0x65E5A030, InternalHigh: 0x0, Offset: 0x1, OffsetHigh:
> 0x4862F628, m_buf: 0x00000012, m_len: 1, m_actualBytes: 0,
> m_errcode: 995, BackupFile: VNBU0-2000-2912
> I also started getting the following error reported around
> the same time of day:
> The SQL Server cannot obtain a LOCK resource at this time.
> Rerun your statement when there are fewer active users or
> ask the system administrator to check the SQL Server lock
> and memory configuration..
> I am able to do a regular dump to disk with no errors.
> Any ideas on resolution here?
> Thanks for your time.
> Miles
Subscribe to:
Posts (Atom)