Backup problems

Hi,
I'm getting "BackupMedium::ReportIoError: write failure on
backup device 'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK '.
Operating system error 112(error not found)" messages in
the SQL 2000 Server logs when we try to backup our
databases. This is followed by "Internal I/O request
0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
Position: 21632512, UMS: Internal: 0x103, InternalHigh:
0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
112, BackupFile: d:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK " and
then "BACKUP failed to complete the command BACKUP
DATABASE [legal] TO DISK = N'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK ' WITH
INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
messages. The database is around 300Mb and we have 40Gb of
free space on the drive.
The server is Dell PE2600 with a Perc Raid controller
handling 3 drives in Raid 5 config. These are split into
two drives; C: for OS and D: for applications and data.
The smaller system databases back up OK as do the
transaction logs. I've found a reference to writeback
cache but don't know if this is the root cause of the
problem. The OS is Windows 2003 Small Business Server with
SQL Server SP3a.
TIA
Trevor
>
> Hi,
> I'm getting "BackupMedium::ReportIoError: write failure on
> backup device 'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK '.
> Operating system error 112(error not found)" messages in
> the SQL 2000 Server logs when we try to backup our
> databases. This is followed by "Internal I/O request
> 0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
> Position: 21632512, UMS: Internal: 0x103, InternalHigh:
> 0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
> 0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
> 112, BackupFile: d:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK " and
> then "BACKUP failed to complete the command BACKUP
> DATABASE [legal] TO DISK = N'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK ' WITH
> INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
> messages. The database is around 300Mb and we have 40Gb of
> free space on the drive.
> The server is Dell PE2600 with a Perc Raid controller
> handling 3 drives in Raid 5 config. These are split into
> two drives; C: for OS and D: for applications and data.
> The smaller system databases back up OK as do the
> transaction logs. I've found a reference to writeback
> cache but don't know if this is the root cause of the
> problem. The OS is Windows 2003 Small Business Server with
> SQL Server SP3a.
> TIA
> Trevor
>
Hi Trevor,
Are you using a compressed volume? It is possible that you are out of
diskspace.
Compressed volumes are not supported. Also checkout the following article:
INF: SQL Server and Striped Backups
http://support.microsoft.com/?id=325334
Hope this helps,
Eric Crdenas
SQL Server senior support professional
|||Eric Cardenas wrote:

> --
> Hi Trevor,
> Are you using a compressed volume? It is possible that you are out of
> diskspace.
> Compressed volumes are not supported. Also checkout the following
> article:
> INF: SQL Server and Striped Backups
> http://support.microsoft.com/?id=325334
> Hope this helps,
> --
> Eric Cardenas
> SQL Server senior support professional
Eric,
We should have plenty of disk space. The drives aren't compressed as
far as I am aware.
The databases reside on the same drive that we are backing up to.
We are backing up the databases to a folder on the drive using the SQL
Server backup, and then to tape; the actual database files we exclude
from the tape backup.
The server reports around 40Gb of free space on a 60Gb drive, and the
databases that it fails to back up are our main data database which is
around 200Mb to 250Mb in size, and one of the SQL Server system
databases which looks to be only around 25Mb! The other smaller system
databases back up OK.
The drive is on a Raid 5 array which comprises three 60Gb drives.
We can copy and otherwise create large files on the drive without any
problems; we can copy the database files manually with out any problems
(when we shutdown the SQL Server)
It just seems to be the SQL Server backup of the databases that are
reporting an error.
I've seen some references to writeback cache causing a problem like
this, but nothing that I can say "this is how we fix the problem"
I can't believe that the problem is with the raid striping as I would
then expect loads of people to be reporting this.
Trevor