May 25, 2012 at 4:57 am
Hello
I'm using SQL server 2008 R2 and have set-up my maintenance plans which appear to be running fine performing a full back-up overnight with 2 hourly transaction log back-ups, I've checked that the back-up files are being generated on the correct network location and that e-mail notifications are working everything seemed fine, I've come to perform a restore and this is where I've hit my problem.
Using the restore wizard I select the database I want to restore then ok to perform the restore I get the following message.
"Restore failed for server 'InstanceName' (Microsoft.SqlServer.SmoExtended)
Additional Information:
System.Data.SqlClient.SqlError: Cannot open backup device
'{FBF49089-7555-9AFD-FC0E1B820512}-10'. Operating system error 2 (Failed to retrieve text for this error. Reason 15105). (Microsoft.SqlServer.Smo)"
Which suggests the restore action can't see the network location I've tried to restore from a previous day with the same problem but I noticed that the Full database backup is using 'User Name' 'NT Authority\System' which explains why it's having problems accessing a network resource, I've checked that the jobs are owned by accccounts that have access to the network resource and also that the SQLServer and SQLServer Agent services are running as domain accounts with access to the network resource which they all are.
I can not tell why the Full Backup is showing the user NTAuthority/System, I've copied a backup file locally and restored from the file fine so there is no issue with the backups themselves.
Any assistance greatfully recieved.
May 25, 2012 at 5:02 am
Are you using UNC paths or have you mapped a drive to the network share?
May 25, 2012 at 5:05 am
I'm using a unc path.
January 22, 2014 at 10:51 am
Did you find a resolution to your restore problem. I am having the exact same issue. This worked fine for years, just noticed it in the last month or so.
January 23, 2014 at 2:28 am
Unfortunately I never got to the bottom of this problem, so I've changed my restore procedure to copy the files from the remote location to the server and restoring from the local file, not ideal but I couldn't find the reason for this problem.
January 24, 2014 at 7:30 am
I found in our event viewer on the server a whole bunch of back up errors un-related to my SQL backup. I had done some digging and found that it could be related to our VMware backups. Out network admin turned off the quiesce feature of our VMware backups. I have no more errors in the event viewer and the full backup now has it's proper name and user_name, and can be restored, without the error. Not sure if this applies to your situation, but I wanted to put our resolution out here.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply