Backup and Restore of EncrypTight Manager
•
•
Backup Server scp User Backup Server scp Password
Also note that the ETM root dir is /opt/jboss/server/policyserver, and that the /opt/scripts directory is a symlink to /opt/jboss/server/policyserver/scripts, so that directory will be backed up. It contains the config files that were used during installation.
Files in /etc/init.d are not included in this tar, so those should be backed up separately, after installation. They should never change after installation.
Whether or not the backup is scp'd to a remote host, a copy will be left in the /opt/jboss/server/ policyserver/log dir, and can be downloaded via the browser from the
The names are of the following format:
<host ip
Procedure 4. Restoring the ETM software and data
To restore from a ETM server backup, obtain the backup that was taken for the particular host (note that the ip address of the host is part of the backup file name), scp it to the ETM host, and untar it. (The application server should be stopped before doing this: /etc/init.d/policyserver stop) For example:
scp
cd /
gunzip
At this point, the database backup that is located in /opt/jboss/server/policyserver/log can be used (only if necessary) to restore the database. See procedure 6. Once completed, the application server can be restarted, /etc/init.d/policyserver start. See notes below on details related to cluster nodes and DR servers.
Procedure 5. Backing up the ETM database
To backup the just the ETM database, navigate to the
Procedure 6. Restoring the ETM database
To restore the database from a backup, scp the backup to the host being restored, and execute the db- import.sh script. For example:
scp
cd /opt/filestore
gunzip
EncrypTight Manager Installation Guide | 29 |