Setup guide

Backing Up Data
52 Netscape Certificate Management System Command-Line Tools Guide • May 2002
These CMS global and local class files are Java classes for custom plug-ins used by
CMS servers. To back up this data, all files and subdirectories in the following
directories are backed up:
•
<server_root>/bin/cert/classes
• <server_root>/cert-<instance_id>/classes
The following CMS global configuration files, which are used for access control
and the certificate mapping, are also backed up:
•
<server_root>/adminacl
• <server_root>/httpacl
• <server_root>/userdb
The CMSuser interfacefiles andtem plates are thefiles used tocreate theforms end
entities and age nts use to interact with CMS servers. All of these files for the
instance you are backing up are in
•
<server_root>/cert-<instance_id>/web-apps
• <server_root>/cert-<instance_id>/emails
The CMS configuration files that get backed up are in
<server_root>/cert-<instance_id>/config. The specific files and their
purposes are:
•
CMS.cfg, the current master configura tion file for the instance.
•
CMS.cfg.*, previous configuration files, available for reverting to an earlier
configuration.
•
*.db, the server i nstance key and certificate datab ases.
•
*.ldif, ldif-format files that describe objects in the configuration database.
•
pwcache.db, the server in stance password cache.
All of the data t o be backed up is copied to the temporary backup directory. After
all ofthe data hasbeen copied, the scriptarchives the entirebackup directoryintoa
compressed archive using
zip (a copy of zip is installed in
<server_root>/bin/cert/tools/zip). The script deletes the backup directory
once the zip archive is created.