Restore of 100Gb database fail with Backupexec9.1

[nb45]

Hi;
When i try to restore with Veritas BackupExec 9.1 the sql database after 1hr and 30 minutes, we see the following error in the SQL Errorlog:

2006-09-24 13:37:08.19 spid54 BackupMedium::ReportIoError: read failure on backup device 'AF_00__a951399e_0cc9_44cf_b7d5_5eb2c78ac536_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
2006-09-24 13:37:08.19 spid54 Internal I/O request 0x7EC23810: Op: Read, pBuffer: 0x18BA0400, Size: 512, Position: 7680, UMS: Internal: 0x0, InternalHigh: 0x0, Offset: 0x0, OffsetHigh: 0x0, m_buf: 0x00000000, m_len: 0, m_actualBytes: 0, m_errcode: 995, BackupFile: AF_00__a951399e_0cc9_44cf_b7d5_5eb2c78ac536_

Over the Enterprise manager, we see the SPID of the restore with the waiting type NETWORKIO.

How i can fixed this behavior?. Whit small database the restore process working fine.

 

[Spirit]

Try redirecting the restore to a local drive rather than over the network.

Then move the file manually to the SQL drectory and remount it that way.

Iain

 

[steveot]

That wont work re-direct. You have to restore to an active SQL server you cant just restore the mdf/ldf files. You will have to have a local instance of SQL installed with that much space. Run the restore, then move the files over manually after unattaching the database. That 995 error is coming right from the os. net helmsg 995 = The I/O operation has been aborted because of either a thread exit or an application request.).

Is there enough disk space? Have you tried restoreing using Namedpipes?

http://support.veritas.com/docs/194680

This applied to all version of SQl not just 7.0 as suggest. If you look up named pipe on symantec support you can see if resolve alot of connection issues

 

[nb45]

Actually we try changing the named pipe value, but the result is the same. How much space aditional we need for the restore procedure? We don´t recive any notification about space problems.

We apply the doc number 1946980, with the same result.