Details:
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. After SQL is running again, you can restore the latest copy of the master database using Backup Exec's Automate master database restore option, and then restore any other databases, if needed.

If using SQL 2000 and 2005:


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.

In a default installation of SQL 2000 or 2005, the databases are in:
C:\Program Files\Microsoft SQL Server\MSSQL\Data\*.*.

In a named instance of SQL 2000 or 2005, the databases are in:
C:\Program Files\Microsoft SQL Server\MSSQL$Instance_Name\Data\*.*

The copies of the master and model databases are named:

Master$4idr

Mastlog$4idr

Model$4idr

Modellog$4idr


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.

Make sure you are prepared to recover the entire server, not just SQL

If using SQL 7.0:

Create a copy of the master and model databases, and place the copies in the same directory that the databases are in.

To create copies of the SQL 7.0 master and model databases:

1. Use the SQL Server Service Manager to stop the SQL services.
2. Open a command prompt window, and copy the original master and model databases and their transaction logs to the specified file names. In a default installation of SQL 7.0, the databases are in C:\MSSQL7\Data.
Type the following:
C:\ mssql7\data> copy master.mdf master$4idr
C:\ mssql7\data> copy mastlog.ldf mastlog$4idr
C:\ mssql7\data> copy model.mdf model$4idr
C:\ mssql7\data> copy modellog.ldf modellog$4idr

Back up both system and user databases and transaction logs regularly.

Back up the system drive that contains SQL.

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.

Make sure you are prepared to recover the entire server, not just SQL.

To perform a recovery, you will need:

The SQL database or filegroup backups, and differential and log backups.

An Administrator logon account (or an Administrator equivalent) during the recovery.

The latest backup of the SQL directory (\Program Files\Microsoft SQL Server\MSSQL), and the and System State are good to have but not needed to restore your databases.


If you purchased the Intelligent Disaster Recovery (IDR) option, then during an IDR 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.

NOTE:  

For the Intelligent Disaster Recovery Option to work with SQL 2000, copies are made of the master and model databases. Copies are only made when non-AOFO backups of master and model are run. If you are using AOFO for SQL backups, make at least one backup of the master and model databases without using AOFO.

If SQL 2000 is upgraded, refresh the copies with another non-AOFO backup.

Related Documents:

236240: Disaster recovery of a local Windows 2000 or 2003 computer (includes non-authoritative restore of Active Directory for a domain controller)
 http://support.veritas.com/docs/236240


236286: Disaster Recovery of a remote Windows 2000 or 2003 computer (includes non-authoritative restore of Active Directory for a domain controller)
 http://support.veritas.com/docs/236286


243093: SQL Agent: How to restore the master database within Microsoft SQL Server 2000 Backup Exec for Windows Servers
 http://support.veritas.com/docs/243093


295642: How to perform local and redirected restore of SQL 2000 & 2005 Databases with Backup Exec for Windows Servers (BEWS)
 http://support.veritas.com/docs/295642

---