A full system recovery of the SQL Server client involves several phases for the preparations of a recovery and for the recovery of the SQL databases.
Preparing for a Full System Recovery
Before you begin a disaster recovery, plan for the disaster recovery:
-
Build a standby server for quick recovery and always keep the standby database in a near-ready state. Follow the steps described in Hot Standby Server Restore.
-
As a best practice, group databases into multiple subclients:
-
Add larger databases into separate subclients.
-
Add small databases together into one or more subclients. During Backup failures, the backup will restart from the beginning of the database instead of from the beginning of the entire instance. This will ensure that large database backups are not affected by restarts from a smaller database.
-
After the subclients are created, schedule frequent backups for dynamic data and regular backup schedules for static data in the SQL Server.
-
Recovering the SQL Databases
To recover the SQL database in the event of a disaster, you must perform the following tasks:
-
Rebuild the SQL Server Instance.
After rebuilding the operating system, if the SQL Server Instance does not start, rebuild the instance, and then restore it to the current state. You can rebuild the instance by rebuilding the master database or by reinstalling each instance:
-
Rebuilding the Master Database (Quick Rebuild)
-
Rebuilding Each SQL Server Instance (When Quick Rebuild does not work)
-