What the Backup Tool Does
There is a script or batch file installed in the instance directory of every CMS
instance. This file calls the Perl script
<server_root>/bin/cert/tools/CMSBackup.pl
bundled with Certificate Management System).
•
Creates a log file where all backup actions are logged
•
Creates a temporary backup directory
•
Copies CMS and non-CMS certificate and key databases and shared files
•
Copies files required to configure the Netscape Console and Administration
Server
•
Backs up the configuration Directory Server using that server's
utility (if the server is running locally)
•
Backs up the CMS internal database (Directory Server) using that server's
backup utility
db2bak
•
Copies CMS global and local class files
•
Copies CMS user interface files and templates
•
Copies CMS instance configuration files
•
Creates a compressed archive of all files in the backup directory
The log file is in
<server_root>/cert-<instance_id>/logs/cmsbackup.log
You should review the log file after each backup to make sure that all phases of the
backup completed successfully. If all or part of the backup fails it is usually due to
a directory that is missing or not readable by the user running the backup.
The default temporary backup directory is
NT). Ensure that access to this directory is restricted so that no one can intercept
backup files while the archive is being built. You can change the working backup
directory by changing the value of
The CMS database, non-CMS databases and shared files that are backed up are:
•
<server_root>/alias/*
•
<server_root>/shared/config/*.conf
The Administration Server files that are backed up are the following files from
<server_root>/admin-serv/config/
•
, the Administration Server password cache
admpw
(using a Perl 5.005 interpreter
CMSBackup.pl
(Unix) or
/var/tmp
$backup_path_prefix
:
Chapter 7
Backing Up Data
does the following:
backup
db2bak
(Windows
C:\Temp
in
.
CMSBackup.pl
Backing Up and Restoring Data
.
63