By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,086 Members | 1,460 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,086 IT Pros & Developers. It's quick & easy.

SQL Server Backup Failure

P: n/a
nt
I am having a problem with a regular backup of an SQL Server (MSDE
2000) database to a local drive. I initiate the backup once a week, by
issuing the required T-SQL, via ADO. In this case, the T-SQL is:

BACKUP DATABASE GPRS_Dimensioning_Archive TO local_backup WITH
RETAINDAYS=21, NAME='GDA_20040706'

Note that "local_backup" is a file sitting on the same physical drive
as the database itself, and has > 80 GB free. It is not a RAID device.

The database that I am backing up is 1.6 GB. Oddly, the backup of
another database to the same file was successful; it was ~900 MB.

Even more strangely, I also back these databases up to a network
drive, which has been running successfully for a number of weeks now
(longer than the local backup), and continues to work without any
trouble. The resultant backup file is much larger than the one sitting
on the local drive (6.8 GB on the network drive vs ~4 GB locally) This
network drive has less space (~50 GB) and is configured as RAID 0. It
is a Linux box, using Samba to present the drive to the Windows
network.

Any ideas?? I am completely stumped. Obviously, Microsoft
documentation has been particularly unhelpful.

The excerpt below is taken from the SQL server error log, covering a
couple of attempts.

Any help would be greatly appreciated!!!

Nick Tompson.

2004-07-06 09:56:01.99 spid54 BackupMedium::ReportIoError: write
failure on backup device 'C:\Front End\Local Backup\DB_Backup.bak'.
Operating system error 112(error not found).
2004-07-06 09:56:02.01 spid54 Internal I/O request 0x02672360: Op:
Write, pBuffer: 0x02890000, Size: 65536, Position: 4294914560, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFFF3200, OffsetHigh:
0x0, m_buf: 0x02890000, m_len: 65536, m_actualBytes: 0, m_errcode:
112, BackupFile: C:\Front End\Local Backup\DB_Backup.bak
2004-07-06 09:56:02.01 backup BACKUP failed to complete the command
BACKUP DATABASE GPRS_Dimensioning_Archive TO local_backup WITH
RETAINDAYS=21, NAME='GDA_20040706'
2004-07-06 09:56:17.08 spid54 Starting up database
'GPRS_Dimensioning_Archive'.
2004-07-06 09:56:33.11 spid54 BackupMedium::ReportIoError: write
failure on backup device 'C:\Front End\Local Backup\DB_Backup.bak'.
Operating system error 112(error not found).
2004-07-06 09:56:33.11 spid54 Internal I/O request 0x02674360: Op:
Write, pBuffer: 0x028A0000, Size: 65536, Position: 4294914560, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFFF3200, OffsetHigh:
0x0, m_buf: 0x028A0000, m_len: 65536, m_actualBytes: 0, m_errcode:
112, BackupFile: C:\Front End\Local Backup\DB_Backup.bak
2004-07-06 09:56:33.11 backup BACKUP failed to complete the command
BACKUP DATABASE GPRS_Dimensioning_Archive TO local_backup WITH
RETAINDAYS=21, NAME='GDA_20040706'
Jul 20 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
nt******@excite.com (nt) wrote in message news:<ba**************************@posting.google. com>...
I am having a problem with a regular backup of an SQL Server (MSDE
2000) database to a local drive. I initiate the backup once a week, by
issuing the required T-SQL, via ADO. In this case, the T-SQL is:

BACKUP DATABASE GPRS_Dimensioning_Archive TO local_backup WITH
RETAINDAYS=21, NAME='GDA_20040706'

Note that "local_backup" is a file sitting on the same physical drive
as the database itself, and has > 80 GB free. It is not a RAID device.

The database that I am backing up is 1.6 GB. Oddly, the backup of
another database to the same file was successful; it was ~900 MB.

Even more strangely, I also back these databases up to a network
drive, which has been running successfully for a number of weeks now
(longer than the local backup), and continues to work without any
trouble. The resultant backup file is much larger than the one sitting
on the local drive (6.8 GB on the network drive vs ~4 GB locally) This
network drive has less space (~50 GB) and is configured as RAID 0. It
is a Linux box, using Samba to present the drive to the Windows
network.

Any ideas?? I am completely stumped. Obviously, Microsoft
documentation has been particularly unhelpful.

The excerpt below is taken from the SQL server error log, covering a
couple of attempts.

Any help would be greatly appreciated!!!

Nick Tompson.

2004-07-06 09:56:01.99 spid54 BackupMedium::ReportIoError: write
failure on backup device 'C:\Front End\Local Backup\DB_Backup.bak'.
Operating system error 112(error not found).
2004-07-06 09:56:02.01 spid54 Internal I/O request 0x02672360: Op:
Write, pBuffer: 0x02890000, Size: 65536, Position: 4294914560, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFFF3200, OffsetHigh:
0x0, m_buf: 0x02890000, m_len: 65536, m_actualBytes: 0, m_errcode:
112, BackupFile: C:\Front End\Local Backup\DB_Backup.bak
2004-07-06 09:56:02.01 backup BACKUP failed to complete the command
BACKUP DATABASE GPRS_Dimensioning_Archive TO local_backup WITH
RETAINDAYS=21, NAME='GDA_20040706'
2004-07-06 09:56:17.08 spid54 Starting up database
'GPRS_Dimensioning_Archive'.
2004-07-06 09:56:33.11 spid54 BackupMedium::ReportIoError: write
failure on backup device 'C:\Front End\Local Backup\DB_Backup.bak'.
Operating system error 112(error not found).
2004-07-06 09:56:33.11 spid54 Internal I/O request 0x02674360: Op:
Write, pBuffer: 0x028A0000, Size: 65536, Position: 4294914560, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFFF3200, OffsetHigh:
0x0, m_buf: 0x028A0000, m_len: 65536, m_actualBytes: 0, m_errcode:
112, BackupFile: C:\Front End\Local Backup\DB_Backup.bak
2004-07-06 09:56:33.11 backup BACKUP failed to complete the command
BACKUP DATABASE GPRS_Dimensioning_Archive TO local_backup WITH
RETAINDAYS=21, NAME='GDA_20040706'


This is a guess, but what is the filesystem of the drive you're
backing up to? You mention that the current backup file is 4GB, and
that's the file size limit on FAT32, so if the backup would result in
a larger file, then it will fail. You also didn't mention your
operating system - if it's Windows 98, then you're stuck with that
limit; if it's Windows 2000, then you can convert your filesystem to
NTFS (which is recommended anyway).

Simon
Jul 20 '05 #2

P: n/a
nt
sq*@hayes.ch (Simon Hayes) wrote in message news:<60**************************@posting.google. com>...
nt******@excite.com (nt) wrote in message news:<ba**************************@posting.google. com>...
I am having a problem with a regular backup of an SQL Server (MSDE
2000) database to a local drive. I initiate the backup once a week, by
issuing the required T-SQL, via ADO. In this case, the T-SQL is:

BACKUP DATABASE GPRS_Dimensioning_Archive TO local_backup WITH
RETAINDAYS=21, NAME='GDA_20040706'

Note that "local_backup" is a file sitting on the same physical drive
as the database itself, and has > 80 GB free. It is not a RAID device.

The database that I am backing up is 1.6 GB. Oddly, the backup of
another database to the same file was successful; it was ~900 MB.

Even more strangely, I also back these databases up to a network
drive, which has been running successfully for a number of weeks now
(longer than the local backup), and continues to work without any
trouble. The resultant backup file is much larger than the one sitting
on the local drive (6.8 GB on the network drive vs ~4 GB locally) This
network drive has less space (~50 GB) and is configured as RAID 0. It
is a Linux box, using Samba to present the drive to the Windows
network.

Any ideas?? I am completely stumped. Obviously, Microsoft
documentation has been particularly unhelpful.

The excerpt below is taken from the SQL server error log, covering a
couple of attempts.

Any help would be greatly appreciated!!!

Nick Tompson.

2004-07-06 09:56:01.99 spid54 BackupMedium::ReportIoError: write
failure on backup device 'C:\Front End\Local Backup\DB_Backup.bak'.
Operating system error 112(error not found).
2004-07-06 09:56:02.01 spid54 Internal I/O request 0x02672360: Op:
Write, pBuffer: 0x02890000, Size: 65536, Position: 4294914560, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFFF3200, OffsetHigh:
0x0, m_buf: 0x02890000, m_len: 65536, m_actualBytes: 0, m_errcode:
112, BackupFile: C:\Front End\Local Backup\DB_Backup.bak
2004-07-06 09:56:02.01 backup BACKUP failed to complete the command
BACKUP DATABASE GPRS_Dimensioning_Archive TO local_backup WITH
RETAINDAYS=21, NAME='GDA_20040706'
2004-07-06 09:56:17.08 spid54 Starting up database
'GPRS_Dimensioning_Archive'.
2004-07-06 09:56:33.11 spid54 BackupMedium::ReportIoError: write
failure on backup device 'C:\Front End\Local Backup\DB_Backup.bak'.
Operating system error 112(error not found).
2004-07-06 09:56:33.11 spid54 Internal I/O request 0x02674360: Op:
Write, pBuffer: 0x028A0000, Size: 65536, Position: 4294914560, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0xFFFF3200, OffsetHigh:
0x0, m_buf: 0x028A0000, m_len: 65536, m_actualBytes: 0, m_errcode:
112, BackupFile: C:\Front End\Local Backup\DB_Backup.bak
2004-07-06 09:56:33.11 backup BACKUP failed to complete the command
BACKUP DATABASE GPRS_Dimensioning_Archive TO local_backup WITH
RETAINDAYS=21, NAME='GDA_20040706'


This is a guess, but what is the filesystem of the drive you're
backing up to? You mention that the current backup file is 4GB, and
that's the file size limit on FAT32, so if the backup would result in
a larger file, then it will fail. You also didn't mention your
operating system - if it's Windows 98, then you're stuck with that
limit; if it's Windows 2000, then you can convert your filesystem to
NTFS (which is recommended anyway).

Simon


Thanks! You were exactly right. The machine is brand new (P4, Windows
XP). It didn't even occur to me that the file system wouldn't be NTFS.
Jul 20 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.