R

It's been there for 2 hours! Any ideas?

Hi,

What is your Backup file size, if your log file is very big, srink it first, then take backup, and restore. You can also check your file growth percentage , if it is set to very low percentage, it will slowing the restore process. If you know the old database size then create datafile and logfile as same size as previous.

Thanks

Atanu

|||Any other tips for a restore hanging at 90%? The original database is 'in recovery' mode anyway, so it seems inaccessible.|||

have you varified the backup set... the backup set may have corrupted

use RESTORE VERIFYONLY :

Verifies the backup but does not restore it, and checks to see that the backup set is complete and the entire backup is readable. However, RESTORE VERIFYONLY does not attempt to verify the structure of the data contained in the backup volumes. In Microsoft SQL Server 2005, RESTORE VERIFYONLY has been enhanced to do additional checking on the data to increase the probability of detecting errors. The goal is to be as close to an actual restore operation as practical. For more information, see the Remarks.

Madhu

|||Yes the backup verifies, and it will also restore on another instance of SQL Server. It can then be attached back to the original instance, backed up again, but will hang again on the restore. Restoring with the no recovery option also hangs the process which cannot be killed.|||

Hello,

I am having the same problem. Was this ever resolved?

Thank you,

Keenan

|||In my particular case it was a hardware issue, in that an optical wire connecting the server with a RAID drive was loose, but not disconnected. I could see the drive, but it was causing a problem with the restore process. Once it was plugged in everything worked as expected.