Appendix B Backing Up and Restoring Data

Each instance of Netscape Certificate Management System (CMS) uses an instance of Netscape Directory Server version 4.x for storing its persistent objects and an ASCII file named CMS.cfg for storing its configuration information. This appendix explains how to back up the CMS data and configuration information and how to use the backups to restore data if there is a need.

• Before Backing Up and Restoring Data
• Backing Up the CMS Configuration and Data
• Restoring the CMS Configuration and Data

An archive or backup is a copy of all or some portion of the data that Certificate Management System manages; this data is vital to the functioning of the server. More specifically, a backup is a copy of one or more files used by Certificate Management System and any supporting data that you might need in order to restore those files.

Why You Should Back up Data

All the information or data needed by Certificate Management System is stored in its internal database (explained in "Configuring the Internal Database"). If this data becomes corrupt or inaccessible--for example, as a result of program errors, a disk crash, a power outage, or a disaster that damages your entire facility--the server will not function properly. It is therefore strongly recommended that you back up the internal database periodically.

Here are guidelines to follow in preparation for backing up CMS data:

• Plan your backup schedule.
• Choose the appropriate backup media.
• Check the size of the internal database and configuration files, and make sure that the media has sufficient storage space for creating your backup.
• Decide whether you want to back up the internal database and configuration files to separate media. For example, if you plan to back up the internal database to another directory, you will have to copy the configuration files to another media.
• Verify data consistency.
• Use the appropriate server modes for both Certificate Management System and Netscape Directory Server.
• Estimate the time required for a backup, and ensure that an operator is available.
• If the backup media is tape, label the tapes appropriately.

The process of restoring data from backups in the event of a data loss is called a restore. During a restore, you copy the data from the backup medium to the internal database of Certificate Management System.

If the data managed by Certificate Management System becomes corrupt or inaccessible (for example, as a result of program errors, a disk crash, or a disaster that damages your entire facility), the server will not function properly. To restore Certificate Management System to its original state, you need to use the data backups that you created.

Here are some guidelines that will help you restore your Certificate Management System internal database:

• Choose the appropriate backup media.
• Decide on the type of restore.
• Verify your internal database configuration and schema.
• Perform the restore.

• Step 1. Back Up the Configuration Files
• Step 2: Back up the Key Pairs
• Step 3. Back Up the Internal Database

http://home.netscape.com/eng/server/cms

Step 1. Back Up the Configuration Files

You can back up the configuration information pertaining to a CMS instance to any backup media, such as a tape or the file system of a computer designated for backing up important files. The following procedure explains how to back up the configuration information of a CMS instance to the file system of a machine used for backups. If your backup media is a tape or any other backup unit, follow the instructions that came with it.

1. Shut down the CMS instance whose configuration information you want to back up; see "Stopping Certificate Management System".
2. In the file system of the machine used for backups, create a back up directory for storing the configuration information.
3. Copy the complete config directory contents.

You can find this directory at this location:

<server_root>/cert-<instance_id>/...

<server_root> is the directory where the CMS binaries are kept. You first specified this directory during installation.

<instanec_id> is the ID for this instance of Certificate Management System. You first specified this when you installed this server.

Because the destruction of a private key in a disk crash or similar event can be disastrous if you are depending upon that key for a hierarchy of certificate authorities, backing up your key data is commensurately important. If you do make copies of your keys, however, you must protect your backups with the same level of security that you use for protecting your original keys.

You can back up the internal database in the following ways:

• By using the LDIF conversion built into the Directory Server window
• By using the db2bak command-line script
• By manually copying the internal database directly to a backup directory

1. In Netscape Console, locate the internal database instance you want to back up.
2. Select the instance and click Open.

The Directory Server window appears with the Tasks tab open.



3. Click "Back Up the Directory Server."

The Backup Directory dialog box appears.



4. Choose a directory name where you want the backup stored.

You can either choose a new directory or use the default directory that the server provides.

Directory. Type the full path to the directory in which you want the server to store the backup file, or click the Browse button to select an existing directory.

Use default. Click this button if you want the server to suggest a path for you. If you choose this option, the server stores the backup file in this location:

<server_root>/slapd-<cms_instance_id>/bak/<backup_name>

<server_root> is the directory where the binaries for this instance of Certificate Management System are kept. You first specified this directory during installation.

<cms_instance_id> is the ID for this instance of Certificate Management System. You first specified this when you installed this server.

bak is the directory to which files are backed up.

<backup_name> is a directory-specified name for the backup. By default, the backup name identifies the date and time when the backup was created in the format YYYY_MM_DD_HH_mm_SS; the date and time has YYYYMMDD (year, month, day) and HHmmSS (hour, minute, second) forms, in that order. For example, a backup created on March 23, 1999 at 11:38:56 a.m. is named 1999_03_23_11_38_56.

5. Click OK.

The backup process begins.

http://home.netscape.com/eng/server/cms