January 22, 2009 at 11:20 am
Hello,
could you tell me the steps to perform to restore
master
model
msdb in clustered sql server 2005
January 22, 2009 at 1:13 pm
unless you've made changes to model there's no point in restoring it. msdb is restored the same as any user database. I have never restored master on a cluster - I'd figure it must be akin to rebuilding it - you might have to evict a node - do a re-install and then add the node back.
I think if anything was that serious on a cluster i'd rebuild it.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
January 22, 2009 at 3:12 pm
thank you.
Suggest the following stategy works or not:
Before SP3 installation :
1.Stop the sql service and Take the mdf and ldf off all the databases including system databases to separate location.
If the SP3 installation fails:
1.Uninstall the instance.
2.install the new instance.
3.Stop the sql service and delete all the mdf and ldf files.
4.Restore the previously copied mdf and ldf file and bring back the sql server instance to previous state, I mean SP2 level.
Plz suggest if Iam wrong or if there are any gochas in this method
January 22, 2009 at 4:16 pm
Ok.. I tested the following scenario..
Before SP3 installation :
1.Stop the sql service and Take the mdf and ldf off all the databases including system databases to separate location.
If the SP3 installation fails:
1.Uninstall the instance.
2.install the new instance.
3.Stop the sql service and delete all the mdf and ldf files.
4.Restore the previously copied mdf and ldf file and bring back the sql server instance to previous state, I mean SP2 level.
But in step 4, I end up with version RTM but not SP2..Is this normal behaviour? or It should come to previous version SP2?
which is correct? plz advice. If this roll back scenario is fine, then we will go head and install SP3 in production and if it is goes bad, we follow the above roll back strategy..and install the SP2 to get back to the previous state...
Any help would be appreciated
January 24, 2009 at 1:32 pm
This method is not supported or recommended - although I've moved mdf and ldf files about similar to this. Don't forget the systemresource database.
I'd probably re-install sp2 as moving the mdfs isn't the same as restoring to sp2, you miss all the install and binaries - a file level backup with sql server stopped would be your absolute bests - then just resore from tape/backup. Done all these things on stand alone servers but not on a cluster, sorry.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
January 24, 2009 at 1:51 pm
hello,
i have worked on many clusters and i have found that the best solution in a case where the system databases have become corrupt is usually to rebuild. If you are able to get it to work then you may have the worries later when you may really need your systems to perform at their best. I would not trust putting a cluster back together like this unless i have done this on a test system or something to that sort. IF you can this could be an ideal time to test your backups and restores 🙂 just my .02
Good Luck...
-D-
DHeath
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply