Restoring Microsoft Sql Server 2005 Master Databases; Working With Certificate Services - HP BB118BV - StorageWorks Data Protector Express Package User's Manual & Technical Reference

Restoring Microsoft SQL Server 2005 master databases

A damaged master database is evident by the failure of the SQL Server to start, by segmentation faults or
input/output errors or by a report from DBCC. An example of an error might be damage caused by
media failure in the area in which master database is stored.
The procedure used to recover a damaged master database is different from the procedure used to
recover user databases. If the master database becomes unusable, it must be restored from a previous
dump. All changes made to the master database after the last dump are lost when the dump is reloaded
and therefore must be reapplied.
It is strongly recommended that the master database be backed up each time it is changed. This is best
accomplished by prohibiting the creation of user-defined objects in the master database and by being
aware of the statements and system procedures, and the equivalent actions in SQL Server Management
Studio, that modify it.
Please refer to the documentation for Microsoft SQL Server 2005 for information on the proper way to
restore the master databases.
Working with Certificate Services
You can override the backup modes that jobs specify for backing up certificate services.
Force modes
example, if you specify Full for the Incremental mode, Data Protector Express will run a full backup even
though a backup job specifies an incremental mode.
NOTE:
This is only applicable for backing up a server that has certificate services installed, e.g., Certificate
Authority installed on Windows.
Set the modes to use when a job specifies Full, Differential, and Incremental modes For
User's Guide and Technical Reference
291