October 31, 2013 at 4:46 am
I have a 100GB backup to test restore. After 4+ hours and 90% done, I received the below error:
Restore failed for Server 'MyServer'. (Microsoft.SqlServer.SmoExtended)
Additional information:
System.Data.SqlClient.SqlError: Read on "Mypath\backupName.bak" failed: 6(The handle is invalid.) (Microsoft.SqlServer.Smo)
When I google this error, I find plenty of references to it in regards to backing up a database, but no references for what it might mean when restoring a database. So if anyone could clarify what this means during a restore, I would greatly appreciate it.
October 31, 2013 at 9:37 am
As you have probably figured out, something happened, and the server lost sight of the backup file. When that happened, it could not continue with the restore. Is "MyPath" by chance a network share?
October 31, 2013 at 10:12 am
When possible I prefer to copy the BAK file to a local or SAN drive before restoring. I wouldn't trust a network connection for this operation, expecially with such a large file size.
October 31, 2013 at 10:44 am
MyPath is a SAN drive on another server. I'd love to copy the backup file over to the server that I'm going to be restoring to, but I don't have access to that box. I only have SQL Server access.
I've seen other network errors when trying to restore and backup, but I've never seen the invalid handle one. If that's all this is, then I'm not going to sweat it. I was worried it might be something worse.
October 31, 2013 at 11:23 am
Too bad you don't have access to the box itself...
If you did have access, and this is a one-time operation you could download and install a trial edition of Litespeed (maybe, SQL Backup also - don't know). Litespeed has built in some retry parameters for network backup/restore operations that could get around these types of issues.
And - Litespeed will restore native SQL backups so you don't have to perform a Litespeed backup. With that said, if you could get the backup done using Litespeed it definitely would improve the restore process.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 1, 2013 at 6:57 am
Having used Litespeed before I know it wouldn't help with this backup because it's a native SQL backup.
November 3, 2013 at 5:14 pm
Just to add my 2 cents as from time to time we are getting same error:
First, IMO restoring 100GB backup for 4+ hours and did not finished- it's pretty slow. In my case 200+ GB database restored remotely in 1 hour
Second, try to use not single backup file but multiple (we use 4)
Third, we use Retry option (up to 3 attempts) in case of restore failure
Hope this can help
November 5, 2013 at 6:23 am
try checking that you have instant file initialisation enabled
http://bradmcgehee.com/2010/07/21/instant-file-initialization-speeds-sql-server/
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply