July 11, 2008 at 4:05 am
The Problem:
I'm trying to backup a SQL2000 cluster over the network using 2 maintenance plans, one for 'simple' recovery DB's and one for 'Full'.
However for different databases I'm getting a mix of the following problems:
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID: 17055
Date:10/07/08
Time:20:04:48
User:xxxx.xxxxx\SQLAdmin
Computer:xxxxxSQLSVRxx
Description:
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxxxxxx\d$\SQL_Backups\xxxxxQLSVRxx\FirstClass\FirstClass_db_200807102001.BAK'. Operating system error 64(error not found).
and
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(6)
Event ID:17055
Date:10/07/08
Time:20:04:48
User:xxxx.xxxxx\SQLAdmin
Computer:xxxxxSQLSVRxx
Description:
3041 :
BACKUP failed to complete the command BACKUP DATABASE [exchangeDB] TO DISK = N'\\xxxxxx\d$\SQL_Backups\xxxxSQLSVRxx\exchangeDB\exchangeDB_db_200807102001.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
and
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17055
Date:10/07/08
Time:20:04:48
User:xxxx.xxxxxx\SQLAdmin
Computer:xxxxSQLSVRxx
Description:
18210 :
BackupMedium::ReportIoError: write failure on backup device '\\xxxxxxx\d$\SQL_Backups\xxxxSQLSVRxx\exchangeDB\exchangeDB_db_200807102001.BAK'. Operating system error 64(error not found).
Once I've censored the local details of the SQL log I'll post that as well.
Some of the (smaller) DB's covered by the same plans are in deed backing up nicely, which adds to my confusion. I think the errors are stopping the job from continuing so that the clean-up process of deleting older files isn't running for any DB's.
My System:
Windows 2003 Enterprise Sp2 Cluster
Running SQL 2000 Enterprise sp4
2 Nodes - Using a FC connected 'HP MSA1500' as shared storage, trying to copy to a Windows 2003 Enterprise sp1 server using a local attached SCSI array.
Neither SQL nodes are running any AV products.
What I have tried so far:
Split the maintenance plans between 'simple' & 'full' recovery mode DB's. I know they can be a bit bugged when covered by the same maintenance plan.
Ensured that the 'SQLAdmin' account has full control on the destination files & folders.
Found & then discounted the following KB article as the version of the Hot Fix has been superseded by a later Service Pack.
I haven't tried creating a Share on the backup server, I was going to try that next to see if that made any difference.
If anyone can dispense some wisdom to try & solve this I would be Hugely Grateful.
Thank you in advance.
July 11, 2008 at 4:11 am
This is going to look ugly, you may find it easier to read by coping 'n' pasting the below into 'Notepad' or similar. Thanks again for your attention to this.
2008-07-09 20:00:29.94 backup Database backed up: Database: Contacts, creation date(time): 2008/06/29(15:39:57), pages dumped: 195, first LSN: 157:253:1, last LSN: 157:255:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Contacts\Contacts_db_200807092000.BAK'}).
2008-07-09 20:00:29.94 backup Database backed up: Database: EUR, creation date(time): 2008/06/29(15:40:22), pages dumped: 141, first LSN: 54:609:1, last LSN: 54:611:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\EUR\EUR_db_200807092000.BAK'}).
2008-07-09 20:00:39.20 backup Database backed up: Database: distmodel, creation date(time): 2008/06/29(14:28:20), pages dumped: 290, first LSN: 14:439:1, last LSN: 14:441:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\distmodel\distmodel_db_200807092000.BAK'}).
2008-07-09 20:05:17.98 spid91 BackupMedium::ReportIoError: write failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\exchangeDB\exchangeDB_db_200807092000.BAK'. Operating system error 121(error not found).
2008-07-09 20:05:17.98 spid93 BackupMedium::ReportIoError: write failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\FirstClass\FirstClass_db_200807092000.BAK'. Operating system error 64(error not found).
2008-07-09 20:05:17.98 spid93 Internal I/O request 0x484BAED0: Op: Write, pBuffer: 0x0D560000, Size: 983040, Position: 138286592, UMS: Internal: 0x0, InternalHigh: 0xF0000, Offset: 0x83E1600, OffsetHigh: 0x0, m_buf: 0x0D560000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile: \\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\FirstClass\FirstClass_db_200807092000.BAK
2008-07-09 20:05:17.98 spid91 Internal I/O request 0x23388EE8: Op: Write, pBuffer: 0x0D740000, Size: 983040, Position: 114824704, UMS: Internal: 0x0, InternalHigh: 0xF0000, Offset: 0x6D81600, OffsetHigh: 0x0, m_buf: 0x0D740000, m_len: 983040, m_actualBytes: 0, m_errcode: 121, BackupFile: \\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\exchangeDB\exchangeDB_db_200807092000.BAK
2008-07-09 20:05:17.98 backup BACKUP failed to complete the command BACKUP DATABASE [exchangeDB] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\exchangeDB\exchangeDB_db_200807092000.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:05:17.98 backup BACKUP failed to complete the command BACKUP DATABASE [FirstClass] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\FirstClass\FirstClass_db_200807092000.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:05:18.00 spid93 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\FirstClass\FirstClass_db_200807092000.BAK'. Operating system error 64(error not found).
2008-07-09 20:05:18.00 spid91 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\exchangeDB\exchangeDB_db_200807092000.BAK'. Operating system error 64(error not found).
2008-07-09 20:07:03.14 spid91 BackupDiskFile::CreateMedia: Backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\ExpenditureRequest2\ExpenditureRequest2_db_200807092005.BAK' failed to create. Operating system error = 64(error not found).
2008-07-09 20:07:03.14 spid93 BackupDiskFile::CreateMedia: Backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\gdp\gdp_db_200807092005.BAK' failed to create. Operating system error = 64(error not found).
2008-07-09 20:07:03.14 backup BACKUP failed to complete the command BACKUP DATABASE [ExpenditureRequest2] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\ExpenditureRequest2\ExpenditureRequest2_db_200807092005.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:07:03.14 backup BACKUP failed to complete the command BACKUP DATABASE [gdp] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\gdp\gdp_db_200807092005.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:08:09.53 backup Database backed up: Database: GEOM, creation date(time): 2008/06/29(15:42:24), pages dumped: 514, first LSN: 415:1924:1, last LSN: 415:1926:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\GEOM\GEOM_db_200807092008.BAK'}).
2008-07-09 20:11:33.37 spid91 BackupMedium::ReportIoError: write failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Progress\Progress_db_200807092008.BAK'. Operating system error 121(error not found).
2008-07-09 20:11:33.37 spid91 Internal I/O request 0x6F47CCF8: Op: Write, pBuffer: 0x0DA10000, Size: 983040, Position: 174660096, UMS: Internal: 0x0, InternalHigh: 0xF0000, Offset: 0xA691A00, OffsetHigh: 0x0, m_buf: 0x0DA10000, m_len: 983040, m_actualBytes: 0, m_errcode: 121, BackupFile: \\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Progress\Progress_db_200807092008.BAK
2008-07-09 20:11:33.37 backup BACKUP failed to complete the command BACKUP DATABASE [Progress] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Progress\Progress_db_200807092008.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:11:33.37 spid93 BackupMedium::ReportIoError: write failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\HCCS\HCCS_db_200807092008.BAK'. Operating system error 64(error not found).
2008-07-09 20:11:33.37 spid93 Internal I/O request 0x6F493180: Op: Write, pBuffer: 0x0D650000, Size: 983040, Position: 105059840, UMS: Internal: 0x0, InternalHigh: 0xF0000, Offset: 0x6431600, OffsetHigh: 0x0, m_buf: 0x0D650000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile: \\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\HCCS\HCCS_db_200807092008.BAK
2008-07-09 20:11:33.37 backup BACKUP failed to complete the command BACKUP DATABASE [HCCS] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\HCCS\HCCS_db_200807092008.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:11:33.37 spid91 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Progress\Progress_db_200807092008.BAK'. Operating system error 64(error not found).
2008-07-09 20:11:33.39 spid93 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\HCCS\HCCS_db_200807092008.BAK'. Operating system error 64(error not found).
2008-07-09 20:14:59.07 backup Database backed up: Database: Intranet_Bespoke, creation date(time): 2008/06/29(15:43:35), pages dumped: 412, first LSN: 201:51:1, last LSN: 201:53:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Bespoke_db_200807092014.BAK'}).
2008-07-09 20:15:02.90 backup Database backed up: Database: SurfControl_mobileFilter, creation date(time): 2008/06/29(15:45:39), pages dumped: 1411, first LSN: 2766:78:1, last LSN: 2766:80:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\SurfControl_mobileFilter_db_200807092014.BAK'}).
2008-07-09 20:16:40.35 spid93 BackupMedium::ReportIoError: write failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Rhythmyx\Intranet_Rhythmyx_db_200807092015.BAK'. Operating system error 64(error not found).
2008-07-09 20:16:40.35 spid93 Internal I/O request 0x8DB10AA0: Op: Write, pBuffer: 0x0D100000, Size: 983040, Position: 34412032, UMS: Internal: 0x0, InternalHigh: 0xF0000, Offset: 0x20D1600, OffsetHigh: 0x0, m_buf: 0x0D100000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile: \\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Rhythmyx\Intranet_Rhythmyx_db_200807092015.BAK
2008-07-09 20:16:40.35 backup BACKUP failed to complete the command BACKUP DATABASE [Intranet_Rhythmyx] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Rhythmyx\Intranet_Rhythmyx_db_200807092015.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:16:40.35 spid93 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Rhythmyx\Intranet_Rhythmyx_db_200807092015.BAK'. Operating system error 59(error not found).
2008-07-09 20:17:31.57 backup Database backed up: Database: Intranet_Search, creation date(time): 2008/06/29(15:44:11), pages dumped: 91, first LSN: 10:468:1, last LSN: 10:470:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Search\Intranet_Search_db_200807092016.BAK'}).
2008-07-09 20:26:56.10 spid91 BackupMedium::ReportIoError: write failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\SurfControl_WebFilter\SurfControl_WebFilter_db_200807092015.BAK'. Operating system error 121(error not found).
2008-07-09 20:26:56.10 spid91 Internal I/O request 0x26258D68: Op: Write, pBuffer: 0x0DA10000, Size: 983040, Position: 377559552, UMS: Internal: 0x0, InternalHigh: 0xF0000, Offset: 0x16811A00, OffsetHigh: 0x0, m_buf: 0x0DA10000, m_len: 983040, m_actualBytes: 0, m_errcode: 121, BackupFile: \\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\SurfControl_WebFilter\SurfControl_WebFilter_db_200807092015.BAK
2008-07-09 20:26:56.10 backup BACKUP failed to complete the command BACKUP DATABASE [SurfControl_WebFilter] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\SurfControl_WebFilter\SurfControl_WebFilter_db_200807092015.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:26:56.10 spid91 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\SurfControl_WebFilter\SurfControl_WebFilter_db_200807092015.BAK'. Operating system error 64(error not found).
2008-07-09 20:26:56.29 spid93 BackupMedium::ReportIoError: write failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\RejCleanse\RejCleanse_db_200807092017.BAK'. Operating system error 64(error not found).
2008-07-09 20:26:56.29 spid93 Internal I/O request 0x82E98D78: Op: Write, pBuffer: 0x0D380000, Size: 983040, Position: 332600832, UMS: Internal: 0x0, InternalHigh: 0xF0000, Offset: 0x13D31600, OffsetHigh: 0x0, m_buf: 0x0D380000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile: \\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\RejCleanse\RejCleanse_db_200807092017.BAK
2008-07-09 20:26:56.29 backup BACKUP failed to complete the command BACKUP DATABASE [RejCleanse] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\RejCleanse\RejCleanse_db_200807092017.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:26:56.29 spid93 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\RejCleanse\RejCleanse_db_200807092017.BAK'. Operating system error 64(error not found).
2008-07-09 20:31:27.60 spid93 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Vacancies\Vacancies_db_200807092028.BAK'. Operating system error 64(error not found).
2008-07-09 20:31:27.60 spid91 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Ultrasound\Ultrasound_db_200807092028.BAK'. Operating system error 64(error not found).
2008-07-09 20:31:27.61 backup BACKUP failed to complete the command BACKUP DATABASE [Vacancies] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Vacancies\Vacancies_db_200807092028.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:31:27.61 backup BACKUP failed to complete the command BACKUP DATABASE [Ultrasound] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Ultrasound\Ultrasound_db_200807092028.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:36:00.61 spid93 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\VHR_DATASQL\VHR_DATASQL_db_200807092031.BAK'. Operating system error 64(error not found).
2008-07-09 20:36:00.68 backup BACKUP failed to complete the command BACKUP DATABASE [VHR_DATASQL] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\VHR_DATASQL\VHR_DATASQL_db_200807092031.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 20:41:07.75 spid93 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\VHR_DEMOSQL\VHR_DEMOSQL_db_200807092036.BAK'. Operating system error 64(error not found).
2008-07-09 20:41:07.83 backup BACKUP failed to complete the command BACKUP DATABASE [VHR_DEMOSQL] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\VHR_DEMOSQL\VHR_DEMOSQL_db_200807092036.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 23:00:02.67 backup Log backed up: Database: EUR, creation date(time): 2008/06/29(15:40:22), first LSN: 54:609:1, last LSN: 54:614:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\EUR\EUR_tlog_200807092300.TRN'}).
2008-07-09 23:00:09.89 backup Log backed up: Database: FirstClass, creation date(time): 2008/06/29(15:41:42), first LSN: 62668:10404:1, last LSN: 62668:10411:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\FirstClass\FirstClass_tlog_200807092300.TRN'}).
2008-07-09 23:00:24.03 backup Log backed up: Database: gdp, creation date(time): 2008/06/29(15:42:03), first LSN: 4655:143:1, last LSN: 4666:922:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\gdp\gdp_tlog_200807092300.TRN'}).
2008-07-09 23:00:27.32 backup Log backed up: Database: GEOM, creation date(time): 2008/06/29(15:42:24), first LSN: 415:1911:1, last LSN: 415:1929:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\GEOM\GEOM_tlog_200807092300.TRN'}).
2008-07-09 23:00:36.82 backup Log backed up: Database: HCCS, creation date(time): 2008/06/29(15:43:09), first LSN: 31777:372:1, last LSN: 31781:874:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\HCCS\HCCS_tlog_200807092300.TRN'}).
2008-07-09 23:00:39.07 backup Log backed up: Database: Intranet_Bespoke, creation date(time): 2008/06/29(15:43:35), first LSN: 201:51:1, last LSN: 201:56:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Bespoke\Intranet_Bespoke_tlog_200807092300.TRN'}).
2008-07-09 23:16:58.00 spid90 BackupMedium::ReportIoError: write failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Rhythmyx\Intranet_Rhythmyx_tlog_200807092300.TRN'. Operating system error 64(error not found).
2008-07-09 23:16:58.00 spid90 Internal I/O request 0xB9004728: Op: Write, pBuffer: 0x0D100000, Size: 983040, Position: 1035709952, UMS: Internal: 0xB90040A8, InternalHigh: 0xB90040C8, Offset: 0x3DBBAE00, OffsetHigh: 0x0, m_buf: 0x0D100000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile: \\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Rhythmyx\Intranet_Rhythmyx_tlog_200807092300.TRN
2008-07-09 23:16:58.00 backup BACKUP failed to complete the command BACKUP LOG [Intranet_Rhythmyx] TO DISK = N'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Rhythmyx\Intranet_Rhythmyx_tlog_200807092300.TRN' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
2008-07-09 23:16:58.05 spid90 BackupDiskFile::RequestDurableMedia: failure on backup device '\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Rhythmyx\Intranet_Rhythmyx_tlog_200807092300.TRN'. Operating system error 64(error not found).
2008-07-09 23:20:19.52 backup Log backed up: Database: Intranet_Search, creation date(time): 2008/06/29(15:44:11), first LSN: 10:468:1, last LSN: 10:473:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Intranet_Search\Intranet_Search_tlog_200807092320.TRN'}).
2008-07-09 23:20:23.00 backup Log backed up: Database: RejCleanse, creation date(time): 2008/06/29(15:45:14), first LSN: 95092:10606:1, last LSN: 95092:10620:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\RejCleanse\RejCleanse_tlog_200807092320.TRN'}).
2008-07-09 23:20:30.49 backup Log backed up: Database: Vacancies, creation date(time): 2008/06/29(15:47:05), first LSN: 7134:421:1, last LSN: 7134:423:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\Vacancies\Vacancies_tlog_200807092320.TRN'}).
2008-07-09 23:20:36.22 backup Log backed up: Database: VHR_DATASQL, creation date(time): 2008/06/29(15:47:53), first LSN: 45989:4539:1, last LSN: 45989:5401:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\VHR_DATASQL\VHR_DATASQL_tlog_200807092320.TRN'}).
2008-07-09 23:20:38.36 backup Log backed up: Database: VHR_DEMOSQL, creation date(time): 2008/06/29(15:48:20), first LSN: 45975:5562:1, last LSN: 45975:5607:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\xxbackupsvrxx\d$\SQL_Backups\xxxxSQLSVRxx\VHR_DEMOSQL\VHR_DEMOSQL_tlog_200807092320.TRN'}).
July 11, 2008 at 9:45 am
I believe these would add credence to why backing up over the network is not recommended. It's definitely network connectivity or loss there of.
Can you backup local and then copy to the remote server?
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b325487
http://www.sqlteam.com/Forums/topic.asp?TOPIC_ID=38909
-- You can't be late until you show up.
July 11, 2008 at 10:23 am
Terry has it correct. The backup process is optimized to throw pages out as quickly as possible and it has no tolerance for IO delays. So if the network hiccups at all, it cancels the process.
July 14, 2008 at 3:59 am
Thanks for your feedback gents, it sounds like I'm in a battle I can't win here.
Oh well, more, bigger local SAN disks it is then.
Ta.
July 15, 2008 at 10:15 pm
hi,
I dont think, it would be an issue to backup the database from the server to the san filer directly.
I too get some times the OS error 64, but the only thing we need to look into it is, the filer should be allways available 24*7. If there is a disconnection between the filer and backup plan even for 1 sec, when backup is running we will run out of the issue.
The other factors is to consider the backup to run in local drive, due to time delay for the backup job to complete.
July 16, 2008 at 3:33 am
Hi,
I have the same problem.
Found something about a hotfix voor windows 2003 SP1, but since I'm on SP2 it's of no use to me.
When I run the job, I see that the backup file is placed on the specific location on the network.
I see the file grow and grow, and then all of a sudden it disappears and the job ends with failure.
During the backup I had a ping running that scripts to a file and there didn't seem to be any hiccup in the result.
Backup to local disk is no option, since the database is too big.
Any help would be appreciated.
Thanks,
Vera
July 16, 2008 at 3:48 am
July 16, 2008 at 6:20 am
The true issue is network connectivity and somehow I don't think a hotfix is going to cure that. One blip in the connection/Nic and the backup is worthless. Can you afford missing a backup here and there? I can't. If I need to get to a certain day/PIT and can't because of a network issue, who are they going to blame, the network admin or me? If local disk permits, backup local and copy across the network (or to tape). If local disk doesn't permit, add more disk or look at third party tools that'll compress the backups by about 75% (search this site for the various vendors and comments by posters). That's the recommended, and safest approach. Again, I cannot take a chance missing a backup, can you?
-- You can't be late until you show up.
July 17, 2008 at 6:19 am
We just replaced 2 clustered servers that were running W2K and SQL 2000 with 2 new clustered servers running Win 2003 and SQL 2000. Since these servers were replaced, all of our previous scheduled jobs to backup to a disk location on one of the clustered servers started failing.
BackupDiskFile::RequestDurableMedia: failure on backup device '\\sqlXXXX\backups\SysBkups\XXX\20080707_010603_XXXX_XXXX_Db.bak'. Operating system error 64(The specified network name is no longer available.).
We worked with MS to resolve. And the tech said that it was caused by the SQL server sending the packets not receiving the responses in time so it was perceived that there was a problem with the network. What resolved our problem was to add a SessTimeout setting with the DWORD value as 360 to the Win 2003 or Win2K registry on the SQL servers that the backups are failing. By adding this setting the server waits longer for the response. See this article for info on how to add.
https://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/58909.mspx?mfr=true
Hope this helps
July 17, 2008 at 7:05 am
HeyJudee,
That looks like an excellent workaround. Just to confirm; it was the setting on the source SQL server(s) you changed, not the destination server(s)? Or was it both??
July 18, 2008 at 4:29 am
HeyJudee,
Your suggestion has certainly seen a difference overnight.
I only got an error on the largest database this time. You could be on to a winner here.:smooooth:
I've increased the "SessTimeout" by another 60 seconds, and we'll see how we do again this evening.
I'll post an update Monday.
July 18, 2008 at 6:05 am
Glad I could help. FYI - since we had multiple servers backing up at the same time (all starting at 1:00 a.m), the MS tech also suggested that we stagger the backups so that there was less load put on the backup location at one time.
July 21, 2008 at 8:05 am
After increasing the 'SessTimeout' value to 360 (6minutes), I've had great success over the weekend, with 3/3 backups working beautifully, including the largest of the databases.:w00t:
Thank you HeyJudee, you're a ruddy hero. 😀
September 15, 2008 at 8:23 am
Hello,
When adding\increasing the sesstimeout reg key, do you require a reboot for the change to take effect?
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply