Backup and Restore of EncrypTight Manager
2 Start the policyserver on EncrypTight Manager Cluster Node 2 YOU MUST wait for the startup to complete before continuing
3 Start the policyserver on Disaster Recovery Server Node 1 YOU MUST wait for the startup to complete before continuing
4 Start the policyserver on Disaster Recovery Server Node 2 (Assuming DR Servers are also clustered) YOU MUST wait for the startup to complete before continuing
Backing out of an upgrade
Once the upgrade has completed if there are any problems you can back completely out of the upgrade.
•Go to /opt/upgradebackup
•Execute the downgrade.sh
•./downgrade.sh
This will take the server back to the version before the upgrade.
Backup and Restore of EncrypTight Manager
General Guidelines
There are a variety of failure scenarios that can occur in a production environment, and recovering from these scenarios will not always involve the same procedures. The procedures to follow will be specific to what type of failure occurred, and how much data loss there was as a result. The common failure cases, addressed here are:
•
•
•
•
•
disk drive failures
other hardware component failures damage to the ETM software or database other filesystem damage
complete loss of the OS
Every IT organization will have policies or practices related to backing up servers, so we should learn what a given customer does and ensure that they include the ETM servers in their procedures. We should also ensure that their practices include creating, or already having, some form of bootable media (e.g. DVD) so that they can access the disk drives of a ETM server in case some radical damage is done to the OS (such as 'rm
EncrypTight Manager Installation Guide | 25 |