SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Backup Set List Not Populating


Backup Set List Not Populating

Author
Message
James Mace
James Mace
Valued Member
Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)

Group: General Forum Members
Points: 74 Visits: 112
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
Attachments
ListedBackupSets.jpg (7 views, 82.00 KB)
NoBackupSets.jpg (6 views, 58.00 KB)
WolfgangE
WolfgangE
SSC-Addicted
SSC-Addicted (479 reputation)SSC-Addicted (479 reputation)SSC-Addicted (479 reputation)SSC-Addicted (479 reputation)SSC-Addicted (479 reputation)SSC-Addicted (479 reputation)SSC-Addicted (479 reputation)SSC-Addicted (479 reputation)

Group: General Forum Members
Points: 479 Visits: 792
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search