Setup guide

Before Upgrading
18 Netscape Certificate Management System Command-Line Tools Guide May 2002
Backing Up Your Previous CMS Instance
You must backup your existing CMS 4.2, 4.5, or 6.0 instance before you can
upgrade to CMS 6.01.
For instructions to back up a CMS 4.2 or 4.5 i nstance, check the CMS
Command-Line Tools Guide that was provided with the product; open the
<server_root>/manual/en/cert/tools_guide/backup.htm file. You can
also find the CMS 4.5 documentation at this site:
http://enterprise.netscape.com/docs/cms/index.html
Forinstructionstoback up aCMS 6.0 instance,seeChapter 6,“BackingUp and
Restoring Data.”
Locating Your Previous Security Databases
Each instance of Certificate Management Syst em uses a set of key pairs and
certificates, which can be maintained in an internal/software token or a hardware
token, or a combination of both. These tokens contain public keys, private keys,
and r elevant PKCS #11 compatible drivers. For more information a bou t tokens,
check CMS Installation and Setup Gu ide.
As a part of the upgrad e process, you will be required later to import your existing
key pairs and certificates to the new CMS instance. If you used hardware tokens,
keep those tokens and the corresponding passwords handy. If you used software
tokens, make a note of the following for your CMS instance, where
<4x_server_root> is the location of your CMS 4.2 or 4.5 instance and
<60_server_root> is the location of your CMS 6.0 instance:
Public keys and the corresponding certificates are stored in the certificate
database, this file:
<4x_server_root>/cert-<instance_id>/config/cert7.db
<60_server_root>/alias/cert-<instance_id>-<machine_name>/cert7.d
b
Private keys are stored in the key database, this file:
<4x_server_root>/cert-<instance_id>/config/key3.db
<60_server_root>/alias/cert-<instance_id>-<machine_name>/key3.db
PKCS # 11 drivers are stored in the security database, this fil e:
<4x_server_root>/admin-serv/config/secmod.db
<60_server_root>/alias/secmod.db