Write failure on backup device

paul-wpaul-w Posts: 2
edited September 19, 2006 7:34AM in SQL Backup Previous Versions
Hi

We sometimes get the following error when performing an overnight backup to another server on our LAN:

Event ID 17055

18210 :
BackupMedium::ReportIoError: write failure on backup device '\\SERVER1\BACKUP\BACKUP_20060822.BAK'. Operating system error 121(error not found).


The backup file is fairly large - 15 gb.

Has anyone else come across this error? Can't see anything of note in the SQL Backup log files but in the SQL 2000 errorlog file I see the following error messages:

2006-08-23 00:09:14.15 spid54 BackupMedium::ReportIoError: write failure on backup device '\\SERVER1\BACKUP\BACKUP_20060822.BAK'. Operating system error 121(error not found).
2006-08-23 00:09:14.15 spid54 Internal I/O request 0x54E98A00: Op: Write, pBuffer: 0x0AE90000, Size: 983040, Position: 2978616832, UMS: Internal: 0x0, InternalHigh: 0xF0000, Offset: 0xB18A1600, OffsetHigh: 0x0, m_buf: 0x0AE90000, m_len:983040, m_actualBytes: 0, m_errcode: 121, BackupFile: \\SERVER1\BACKUP\BACKUP_20060822.BAK
2006-08-23 00:09:14.21 spid54 BackupDiskFile::RequestDurableMedia: failure on backup device '\\SERVER1\BACKUP\BACKUP_20060822.BAK'. Operating system error 64(error not found).


I had a look at the MS knowledgebase and found the following in relation to Operating system error = 64 messages:
http://support.microsoft.com/kb/843515/
This problem occurs if a client Server Message Block (SMB) redirector connection on the Windows Server 2003-based computer that is running the SMB service is not initialized correctly.

Comments

  • Hello,

    I'd assume it's either a DNS name resolution problem to the share or there is a permissions problem. Keep in mind scheduled jobs from this version of SQL Backup run in the security context of the SQL Agent Service, which probably doesn't have writes to the share.
Sign In or Register to comment.