August 1, 2013 at 11:14 am
I have posted this on Amazon's Developer Forum, but I have also seen this happen at other times.
I have a Windows 2008 server with SQL Server installed (image_1) on Amazon EC2. I create an image of that machine, then I launch the newly created AMI (image_2). When I go into (image_2)'s Management Studio to perform a database restore, I noticed that all of my backup result sets are not displaying, yet they are on disk.
What it does look like: NoBackupSets.jpg
What it should look like: ListedBackupSets.jpg
What I was hoping that would happen is I could fire up image_2, then using the Management Studio's GUI, restore a database from a point in time. This would speed up the process greatly over having to do it all individually by script.
My question is, when the backup set list is not populated, is there a way to populate it or do I have to run my restore manually from script?
Thank you in advance,
Jim
August 3, 2013 at 12:59 pm
James Mace (8/1/2013)My question is, when the backup set list is not populated, is there a way to populate it or do I have to run my restore manually from script?
Thank you in advance,
Jim
Hello Jim,
if not populated, yes, you have to restore manually.
The backup history is stored in msdb database, not in the backup files itself. This means, when creating your image, get sure you include the msdb-database.
If you don't want to overwrite the msd-database on the target server you can read out the backup history from the msdb database to get all the information you need for restoring your database.
Have a look at the system tables of the msdb database. Find details of it here.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply