Disaster recovery of a SQL Server

Last published : Apr 02, 2026
Backup Exec provides a quicker method for restoring SQL rather than running the Rebuild Master utility or reinstalling SQL to restart SQL. Using Backup Exec, you can replace the corrupted or missing databases with copies of the master and model databases that Backup Exec automatically creates and updates whenever backups of those databases are run.
If you use Simplified Disaster Recovery (SDR), then during an SDR recovery of drive C, it will automatically replace the damaged databases with the copies of the master and model databases. You can then restart SQL, and restore the latest master database backup and any other databases that are necessary.
The following topics are included in this section:
Do the following to prepare for disaster recovery of SQL:
  • Back up both system and user databases and transaction logs regularly.
Copies of the master and model databases are automatically created by Backup Exec whenever you back up the master and model databases. Backup Exec places these copies in the same directory that the databases are in, where they must remain in order to be updated.
The following table includes information about MS SQL database locations:
The copies of the master and model databases are named:
  • lang=txt Master$4idr
  • lang=txt Mastlog$4idr
  • lang=txt Model$4idr
  • lang=txt Modellog$4idr
  • Back up the system drives that contain SQL instances.
Whenever you back up the system drive that contains a SQL instance, copies of the master and model databases are backed up. Backing up the system drive that SQL is on also backs up all the executables and registry settings needed for SQL to run.
  • Back up the master database whenever any changes are made to SQL.
  • Keep records of any service packs that have been installed.
  • Ensure you are prepared to recover the entire server, not just SQL.
Requirements for SQL disaster recovery
To perform a recovery, you will need the following items:
  • The latest backup of the SQL directory (\Program Files\Microsoft SQL Server\MSSQL), and the Windows registry/System State.
  • The SQL database backups, and differential and log backups.
  • An Administrator logon account (or an Administrator equivalent) during the recovery.
Disaster recovery for an entire SQL Server or for SQL databases
You can restore either the entire server, including the SQL databases, from full system backups, or restore only the SQL databases to a newly installed or other available SQL Server.
Restoring the entire server, including the SQL databases, has the added benefit of recovering other applications and data that may have resided on the server at the time of failure, and can be accomplished using one of the following methods:
  • Manual recovery of the Windows server, and then manual recovery of the SQL databases. This method involves manually restoring the Windows server from full system backups, and then recovering the SQL databases.
  • Simplified Disaster Recovery. This option provides an automated method of restoring the Windows server as well as the SQL databases from full system backups.
See Recovery notes for using Simplified Disaster Recovery with Exchange, SQL, SharePoint, CAS, Hyper-V hosts, and the Deduplication feature.
To restore only the SQL databases, review the following:
  • To restore only the SQL databases to a newly-installed or other available server, the server must be running on the same hardware platform (cross-platform restores are not supported), and the same version of SQL with the same service pack level as the original server.
  • To restore SQL databases to an existing installation of SQL with other active databases, you should redirect the restore.
See Manual recovery of a SQL Server.
More Information
Disaster recovery for an entire SQL Server or for SQL databases