System Recovery Planning

Updated: November 15, 2006

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

System failures occur for many different unplanned reasons: hardware failures, floods, power surges, software errors, and so on. A successful deployment includes plans for quickly recovering your system in the event of failure. In an RMS system, the primary requirement for protecting RMS capabilities is to regularly back up the server private key and the RMS databases, especially the configuration database. This practice preserves the rights policy templates, keys, and other data that is required to provide access to previous licenses and published content. If your existing RMS installation becomes unavailable, you can install RMS on other servers, and then provision RMS by specifying the backup configuration database as the database to be used. The new backup installation will be identical to the previous installation at the time that it was last backed up.

This section covers:

Community Additions