Table of Contents
Advertisement
The following is a list of items which may be part of your overall CMS deployment,
but which are not backed up by
•
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 PKCS#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 whenever you back up your
CMS server. It may be possible to extend the
Perl scripts to include this data in the archives used by the
CMSRestore.pl
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
•
You are logged in as a user with permission to run
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.
•
There is plenty of disk space in the output directory; the size of the backup
archive will vary with the amount of data in your system, so you will learn
from experience how much space you require.
The configuration that you back up, of course, will use all of your current
passwords. You will need to remember the current passwords if you restore this
data after you change some passwords.
To run
:
cmsbackup
Log in to the machine where your CMS instance is running and open a
1.
command shell.
:
cmsbackup
, make sure that
Chapter 6
and
CMSBackup.pl
, to run
cmsbackup
Backing Up and Restoring Data
Backing Up Data
db2bak
47
Advertisement
Table of Contents
