backup error

Configuration: Windows Server 2003, SQL Server 2000 SP3A on xSeries 225 with
1.5 GB RAM
The backup is part of database maintenance plan. Most of the values are set
to default. All time schedules are default.
Transaction log backups are ending normally.
I selected 3 databases for full backup. Backup is on network drive on IBM
server. Full backup of first database always ends with error, and for next
two it finishes normally.
This is the part of the ERRORLOG:
2004-08-22 02:11:45.56 spid54 BackupMedium::ReportIoError: write failure
on backup device
'\\Qs655cb5b\MYDOC\MSSQL_Backup\kpdbnova_db_200408220200.BAK'. Operating
system error 64(error not found).
2004-08-22 02:11:45.56 spid54 Internal I/O request 0x4FCE4C50: Op: Write,
pBuffer: 0x13550000, Size: 983040, Position: 19218432, UMS: Internal: 0x0,
InternalHigh: 0xF0000, Offset: 0x1254000, OffsetHigh: 0x0, m_buf:
0x13550000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\Qs655cb5b\MYDOC\MSSQL_Backup\kpdbnova_db_200408220200.BAK
2004-08-22 02:11:45.56 backup BACKUP failed to complete the command
BACKUP DATABASE [kpdbnova] TO DISK = N'\\Qs655cb5b\MYDOC\MSSQL_Backup\kpdbnova_db_200408220200.BAK' WITH INIT ,
NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2004-08-22 02:11:45.62 spid54 BackupDiskFile::RequestDurableMedia:
failure on backup device
'\\Qs655cb5b\MYDOC\MSSQL_Backup\kpdbnova_db_200408220200.BAK'. Operating
system error 64(error not found).
--Hi -
The problem here is SQL Server is Writting the Backup file directly onto
the Network Drive. During this time there might be Packet Loss or Network
Slow in which
the Backup job has higher chances of Failing.
The Best Option would be to take the Backup on the Local Disk. And create a
job to copy the Backup job from physical/Local disk to the Network Drive.
Let me know if it works.
Thanks
"D." wrote:
> Configuration: Windows Server 2003, SQL Server 2000 SP3A on xSeries 225 with
> 1.5 GB RAM
> The backup is part of database maintenance plan. Most of the values are set
> to default. All time schedules are default.
> Transaction log backups are ending normally.
> I selected 3 databases for full backup. Backup is on network drive on IBM
> server. Full backup of first database always ends with error, and for next
> two it finishes normally.
> This is the part of the ERRORLOG:
> 2004-08-22 02:11:45.56 spid54 BackupMedium::ReportIoError: write failure
> on backup device
> '\\Qs655cb5b\MYDOC\MSSQL_Backup\kpdbnova_db_200408220200.BAK'. Operating
> system error 64(error not found).
> 2004-08-22 02:11:45.56 spid54 Internal I/O request 0x4FCE4C50: Op: Write,
> pBuffer: 0x13550000, Size: 983040, Position: 19218432, UMS: Internal: 0x0,
> InternalHigh: 0xF0000, Offset: 0x1254000, OffsetHigh: 0x0, m_buf:
> 0x13550000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\Qs655cb5b\MYDOC\MSSQL_Backup\kpdbnova_db_200408220200.BAK
> 2004-08-22 02:11:45.56 backup BACKUP failed to complete the command
> BACKUP DATABASE [kpdbnova] TO DISK => N'\\Qs655cb5b\MYDOC\MSSQL_Backup\kpdbnova_db_200408220200.BAK' WITH INIT ,
> NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
> 2004-08-22 02:11:45.62 spid54 BackupDiskFile::RequestDurableMedia:
> failure on backup device
> '\\Qs655cb5b\MYDOC\MSSQL_Backup\kpdbnova_db_200408220200.BAK'. Operating
> system error 64(error not found).
> --
>
>|||> Hi -
> The problem here is SQL Server is Writting the Backup file directly onto
> the Network Drive. During this time there might be Packet Loss or Network
> Slow in which
> the Backup job has higher chances of Failing.
> The Best Option would be to take the Backup on the Local Disk. And create
> a
> job to copy the Backup job from physical/Local disk to the Network Drive.
> Let me know if it works.
> Thanks
> "D." wrote:
I'll try to do so. Thank you.