November 3, 2003 at 3:31 am
Does anyone have experience of:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC SQL Server Driver][SQL Server]Write on '<\\network path>' failed, status = 64. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.
From the error log these mssages are found:
BackupMedium::ReportIoError: write failure on backup device '<path>'. Operating system error 64(The specified network name is no longer available.).
Internal I/O request 0x75ECEF08: Op: Write, pBuffer: 0x169C0000, Size: 983040, Position: 179705344, UMS: Internal: 0x0, InternalHigh: 0xF0000, Offset: 0xAB61600, OffsetHigh: 0x0, m_buf: 0x169C0000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile: <path>
I have replaced the network cards already. And checked for similar problems on technet. It happens frequently but randomly to 2 or 3 databases included in a maintenance plan. I have updated our Windows 2000 sp to sp4 and the SQL 2000 Service pack to sp3 with the latest patches. Help very much appreciated!
November 6, 2003 at 8:00 am
This was removed by the editor as SPAM
November 6, 2003 at 9:33 am
Backing up across the network isn't supported because SQL doesn't have tolerance for slow writes. A file copy will wait and retry, but since SQL is writing quickly, if there is any hiccup it fails.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
November 6, 2003 at 9:59 am
Thanks very much for the reply. I suppose the backups will have to be made locally and then copied accross in another step. Its a shame maintenance plans can't be extended so easily, as I'll have to seperate all these into seperate jobs. Thanks again.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply