Site sponsored by: Idera Try Idera’s new SQL admin toolset
SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


FAQ Topics

All FAQ's
General DBA
General Developer
DBA Performance Tuning
Developer Performance Tuning
Clustering
Error Messages

SQL Server 2008 - Worth the Wait

SQL Server’s first significant upgrade in three years features a number of envelope-pushing enhancements and improvements. Which will have the greatest impact on SQL administration and development? More...
Latest Articles

Slowly Changing Dimensions in SQL Server 2005
Audit Data Modifications
SQL Server 2008’s Management Data Warehouse
Same Report but Different Methods in SQL Server Reporting Services ...

More     
 
Latest FAQ's

SSIS Lookups are Case Sensitive
Convert Number to Words in SSRS
After installing SP2 on SQL Server 2005 x64, when trying to ...
Remote Name Could not be Resolved in SQL Server Reporting Services ...

More     
   
Latest Software Reviews

SQL Server DBA Dashboard
SwisSQL DBChangeManager
SQLMesh - SQL Server Search Tool
SoftTreeTech SQL Assistant

More     

How do you restore the master database on a SQL Server cluster?


Printer friendly

Question

I have learned a lot from your articles on SQL Server clustering. We are moving towards a clustering environment very soon, but there is one problem that I can't solve before we go live. Restoring a Master database in a clustering environment is a big problem. This is especially important in a disaster scenario where the Master database goes corrupt and we need to restore from a previous backup of Master database. To restore a Master database, this requires the server to be started in a single user mode, and that’s where the problem comes in, since Cluster Administrator is the only place to do any restarts of the server, etc. Surprisingly I couldn’t find anything on this subject on the net, and the DELL engineers we asked were clueless as well.

 

Answer

You would think that an important topic like this would be widely covered, but since it is not, here's the relatively easy and straight-forward solution for SQL Server 7.0 and SQL Server 2000. Just follow these steps.

  1. Identify which node SQL Server is currently running on, such as node1.

  2. From Cluster Administrator, take the SQL Server resources off-line.

  3. Go to the node running SQL Server (see step 1) and start it from the command prompt using:

    sqlservr.exe -c -m

  4. Restore the master database using Query Analyzer or Enterprise Manager.

  5. Quit SQL Server from the command prompt.

  6. Using Cluster Administrator, restart the SQL Server services.

Now you are good to go.



Comments:
Your Name  
Email    
(Emails will not be displayed on the site or used for promotional purposes)
Comment  


Type characters in the image
 
 (case sensitive)

 
 
 







Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | QDPMA Performance Tuning | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views