Setup guide

Backing Up Data
Chapter 6 Backing Up and Restoring Data 53
What the Backup Tool Does Not Do
The cmsbackup script backs up only configuration and data related to a single CMS
server instance. You may need to back up other files to recover from a f ailure
completely, depending on the nat ure of the failure. F or example, if some entries i n
your configuration Directory Server become corrupted then the data backed up by
cmsbackup is sufficient to restore the directory to a previous state. If, however, you
suffer a catastrophic disk failure, you will probably have to reinstall or restore
Certificate Management System, Netscape Console, andNetscapeDirectory Server
binaries and related tools before you use
cmsrestore to recover your previous
configuration.
The following is a list of items which may bepartof your overall CMS deployment,
but which are not backed up by
cmsbackup:
• Other instances of CMS servers in the same server root
Each instance has a copy of the cmsbackup script that backs up only data
related to that instance.
• External PK CS#11 module data
If you use an external PKCS#11 device for key storage, make sure you follow
the vendor’s instructions for backing up its data w henever you back up your
CMS server. It may be possible to extend the
CMSBackup.pl and
CMSRestore.pl Perl scripts to include this data in the archives used by the
CMS backup tools.
• Server binaries, libraries,and tools
These files do not change after installation, and are not backed up. To restore
these files, you can install the software again from the original media. You can
also use a more generic disk backup tool to archive the contents of all
directories beneath the server root.
Running the Backup Tool
Before you run cmsbackup,makesurethat
• You are logged in as a user with permission to run
cmsbackup,torundb2bak
for the LDAP servers, and to write to the output directory; you may need to
become superuser on a UNIX system or Administrator on a Windows NT
system.