Take a complete copy of an Encryption Management Server

book

Article ID: 226068

calendar_today

Updated On:

Products

Gateway Email Encryption Encryption Management Server

Issue/Introduction

You may need to take a complete copy of an Encryption Management Server if, for example, you are moving to a new data center.

Environment

Symantec Encryption Management Server 10.5 and above.

Resolution

If Encryption Management Server is running on dedicated physical hardware, please do the following:

  1. Follow the steps in article 211876 because the process of upgrading from a release prior to 10.5 to release 10.5 and above entails installing from ISO and restoring from a backup file.
  2. However, note that when you restore the backup, the networking details of the original server will be restored. This includes its IP address, hostname and default gateway.
  3. Therefore if the original server is still connected to the network, you will need to restore the backup to a server that is on a separate network segment to the original server.
  4. You will also need a workstation with a web browser that can connect to the restored server. You may need to add a secondary IP address to the workstation in order to connect to the restored server.
  5. Login to the management console of the restored server and, if necessary, navigate to System / Network and change the network settings.

If Encryption Management Server is running as a Virtual Machine on VMware, you can copy the files that comprise the VM into a new directory on the VMware DataStore and create a new VM. You will probably need to power down the original server before doing this. However, the same considerations apply regarding the network settings so you would probably need to assign the VM to a different virtual network before powering it up.

If you are making a clone of the server for testing or backup purposes and the original server is still running, you are strongly advised to do the following:

  1. Locate the cloned server on completely isolated network segment.
  2. Remove it from any cluster. Navigate to System / Clustering and delete all cluster members.
  3. Update or delete the SMTP settings under Mail / Proxies and under Mail / Mail Routes.
  4. Monitor the log files for potential problems.
  5. Only relocate it to a different network segment when you are confident that it will not cause problems by communicating with other hosts on the network.