Full System Recovery: SQL Server Agent
A full system recovery of SQL Server client involves the following phases:
Preparing for a Full System Recovery
Before you begin a disaster recovery, make sure to plan for disaster recovery as follows:
- Build a standby server for quick recovery and ensure that the standby database is always kept in a near ready state. If you plan to adopt this method follow the steps described in Replication Using Warm Database Restore.
- As a best practice, group databases into multiple subclients as follows:
- Add larger databases into separate subclients.
- Add small databases together into one or more subclients. This is important for the following reasons:
- During Disaster recovery, when you have to quickly rebuild the entire instance, you can concurrently restore all the subclients together.
- During Backup failures, the backup will restart from the beginning of the database instead of from the beginning of the entire instance. Similarly, this will ensure that large database backups are not affected by restarts from a smaller database.
- Once the subclients are created, schedule frequent backups for dynamic data and regular backup schedules for static data in the SQL Server.
Recovering the SQL Database
To recover the SQL database in the event of a disaster, perform the following tasks:
- Rebuilding the Operating System
- Rebuilding the SQL Server Instance
After rebuilding the operating system, if the SQL Server Instance does not start, you need to 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.
- Restoring the SQL Server Instance