After You Finish A Backup - Netscape MANAGEMENT SYSTEM 6.0 - COMMAND-LINE Manual

Backing Up Data
• 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
Log in to the machine where your CMS instance is running and open a
1.
command shell.
Change to the CMS server instance directory in the server root. For example, if
2.
your server root is
you want to back up is
# cd /usr/netscape/servers/cert-cmsinstance
Execute the backup script: either
3.
Windows NT systems. For example,
# ./cmsbackup
The script will run. Control returns to the command prompt when the script has
finished.

After You Finish a Backup

Immediately after running the backup tool, you should check the log file to make
sure that all systems were archived successfully. The log file is
<server_root>/cert-<instance>/logs/cmsbackup.log
If the any part of the backup was not successful, there will be a message labeled
WARNING
of directories or files that are missing or inaccessible to the user running
cmsbackup
zip archive in the output directory, and run
Once you have a successful zip archive, you should secure it. The output directory
is probably accessible to any user on the system, and it may be on the same
physical disk as the server instance itself. You want to make sure the archive is not
accessible to unauthorized users and that you can use the archive if there is a
system hardware failure. Remember, the archive contains a database of private
keys. Although it is not easy to extract a key from the database without the correct
passwords, you do not want anyone to have the opportunity to try.
48 Netscape Certificate Management System Command-Line Tools Guide • March 2002
:
cmsbackup
/usr/netscape/servers
cmsinstance
or that tells you why. Most of the time, the problems are the result
ERROR
. If necessary, change the permissions on the required files, delete the
and the instance ID of the server
:
on UNIX or
cmsbackup
again.
cmsbackup
on
cmsbackup.bat