Filter
Top Products
EncrypTight Manager Upgrade of an Existing ETM Instance
EncrypTight Manager Installation Guide 17
> /etc/init.d/policyserver stop
Once that is down you can see that the disaster recovery picks up rekeys by viewing the DR logs on the
DR Machine:
> tail -f /opt/jboss/server/policyserver/log/server.log
To bring the Main Site back up use the init.d script again on the Main Site machine:
> /etc/init.d/policyserver start
\
EncrypTight Manager Upgrade of an Existing
ETM Instance
The following information covers upgrading an existing EncrypTight Manager instance.
CAUTION
The ordering of actions is important when upgrading EncrypTight Manager. When performing an upgrade
on an existing EncrypTight Manager instance, first stop the policy servers on all machines. Next, upgrade
the main site first, and wait for the upgrade to complete. After the upgrade of the main site is completed, if
there is a disaster recovery server being utilized, you must upgrade the disaster recovery site last.
NOTE
• Requires ETM 3.0 or higher
• All instructions must be executed from the ETM server Command Line while logged in as root/pserver
Upgrade Non-Cluster Instance of ETM
EncrypTight Manager can be installed either as a single node server or as a Cluster. These instructions are
for how to upgrade a Non-Clustered ETM Instance. Upgrading a ETM Cluster is very different from
upgrading a ETM Non-Cluster instance. Instruction for both are provided below.
SCP upgrade file to ETM (Non-Cluster)
CAUTION
These instructions load the upgrade executable in the directory /opt/upgrade on the ETM server, /opt/
upgrade is only a suggested path.
• Download the policyserver-upgrade-<VERSION>.bin executable to your local machine
• scp the .bin file to your ETM server as root (default UID/PWD is root/pserver) to /opt/upgrade
# scp policyserver-upgrade-<VERSION>.bin root@192.168.X.X