Timeout restoring big SQL Databases ?

[Guest_imported]

hi,
i'm trying to restore one of our MS SQL Server 7 Databases using Backup Exec 7.3 Rev 2371.
I only need a couple houndred records from a week ago, therefore i want to restore the DB into a temporary DB on a different drive and then copy the records.
Following steps did not work with the actually needed DB, size ~16GB:
- Creating new Database, default options
- Creating restore job in Backup Exec
Restore in Database: Name of newly created DB
SQL Tab Restore Database: Yes
Replace Databases or Filegroups: Yes
Default Drive: Local, other than original
Replace all files on Default Drive: Yes

Funny thing is, with these options, restoring other DBs than the one i actually need works flawless *sigh*. I get following error after about 25 minutes:
"Connection to Restoretarget lost. Restore cancelled" (german: Verbindung zum Wiederherstellungsziel ging verloren. Vorgang abgebrochen.).
I've tried to restore from different tapes, none works. The fact that DB's that are backuped before or after the one i need can be restored, leads me to believe that it isn't a data corruption problem.

Could this be a timeout due to the large size of DB ? Is it possible to restore only the raw .mdf and attach it later on to a DB ? Any hints are very appreciated. The thought that our main and mission critical DB we use for 1.5 years cannot be restored in worst case makes me feel kinda...sick.

Thanks in advance



Server Info:
Dual PIII 500Mhz
768MB Ram
NT4, Servicepack 6a
Backup Exec 7.3 Rev 2371^
Onstream 30GB ADR Tape
Microsoft SQL Server 7 SP2
Enough space (25GB) on Restoretarget

 

[Zelandakh]

Are you running the SQL server agent? Do you back up the live server or do you dump to disk and back that up?

 

[Guest_imported]

thanks for the reply zelandakh. after a long journey thru this newsgroup:

http://support.veritas.com/menu_ddProduct_BEWNT.htm

i finally found the solution:

http://news.support.veritas.com/dne...backupexec.windowsnt.english&item=28336&utag=

after the described changes:
--->"Had to change registry value in:
HKeyLocalMachine\Software\Veritas\BackupExec\Engine\SQLServer. Changed the
ForceNamedPipeBackup/Restore value data to 1 instead of 0. Apparently, the
installation for version 7.3 does not set the registry correctly. If you
upgraded from version 6, the registry setting was already correct, but if
you perform a clean install of version 7.3, you have to manually change this
registry value. Backups and restores all working now. &quot;<---

...restoring worked like a breeze.

u forget all the trouble and swearing once a problem is solved...

regards,

qeffect