X hits on this document





119 / 200



Disaster recovery

This topic contains information and instructions on restoring the Microsoft SQL Server in a disaster recovery scenario.

Preparing for disaster recovery of SQL Server

When you are developing your SQL Server disaster recovery plan you will need to plan for how to recover from corruption of the master database as well as loss of your host machine. If the master database has been corrupted, then SQL Server will not start. When this happens you will need to use the SQL Server rebuild master (rebuildm.exe) utility to start the SQL Server service. This utility, however, does not recreate the schema information of your application databases. To recover your database schema use the NetBackup SQL Server agent to restore your latest backup of the master database.

As a starting point, disaster recovery of SQL Server assumes that you have already put in place a strategy to recovery from other sorts of data loss such as disk, software, and human error. To prepare for disaster recovery you will need to make frequent backups of the master database, minimally, after you have added or dropped databases or carried out other operations that may result in schema definitions.

Disaster recovery of SQL Server

SQL Server corrects itself automatically from temporary or minor problems. However, most disasters are beyond the scope of the automatic recovery feature. For example, if a database becomes severely corrupted, or there is a catastrophic failure, recovery must be initiated by the system administrator.

User-initiated recovery could entail either restoring the entire server, including the SQL Server databases, from full system backups, or restoring only the SQL Server databases to a newly-installed or other available SQL Server.

Document info
Document views359
Page views359
Page last viewedThu Oct 27 16:41:29 UTC 2016