Restore fails - by TiborK

Status : 

 


7
0
Sign in
to vote
ID 1374515 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 5/27/2015 2:50:45 PM
Access Restriction Public

Description

The restore GUI fails if there was a snapshot produced on the machine. The snapshot is seen by SQL Server as a full backup and the restore GUI will generate restore commands based on this "backup". The restore command will be something like: RESTORE DATABASE dbname FROM <guid>. And, of course a GUID is not a valid source for a restore command. We need to be able to exclude backups from the restore GUI (like the recovery advisor). Who doesn't snap virtual machines nowadays?
Sign in to post a comment.
Posted by Jonathan Brauer on 11/10/2016 at 10:29 AM
This is very annoying. Our Virtual Machine backup solution is breaking our ability to do restores (at least from SSMS) as the "snapshot" backups show up as "copy only" backups to virtual device GUIDs and are unable to be used as a restore basis for following transaction logs though SSMS still tries to use them.
Posted by TiborK on 3/28/2016 at 12:13 PM
That would be great, Ken. I assume a fix would be for the VS 20015 hosted SSMS...
Posted by Ken Van Hyning [MSFT] on 3/25/2016 at 9:02 PM
It's a great blog post. I looked into this a bit last weekend. No promises yet but it seems very reasonable to do.
Posted by TiborK on 3/18/2016 at 2:05 AM
Here's a blog post I wrote with some more details: http://sqlblog.com/blogs/tibor_karaszi/archive/2016/03/17/restoreability-and-ssms.aspx