Backing Up Data
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 CMS user interface files and templates are the files used to create the forms end
entities and agents 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
purposes are:
•
CMS.cfg
•
CMS.cfg.*
configuration.
•
*.db
•
*.ldif
•
pwcache.db
All of the data to be backed up is copied to the temporary backup directory. After
all of the data has been copied, the script archives the entire backup directory into a
compressed archive using
<server_root>/bin/cert/tools/zip
once the zip archive is created.
46
Netscape Certificate Management System Command-Line Tools Guide • March 2002
, the current master configuration file for the instance.
, previous configuration files, available for reverting to an earlier
, the server instance key and certificate databases.
, ldif-format files that describe objects in the configuration database.
, the server instance password cache.
zip
. The specific files and their
(a copy of
is installed in
zip
). The script deletes the backup directory