Using the Manual Join Process when the PGP Server backups are large (larger than 5GBs) - Symantec Encryption Management Server

Products

• Encryption Management Server
• Gateway Email Encryption

Issue/Introduction

Creating an Encryption Management Server cluster from the management console under System / Clustering may fail if the sponsor's database size is over 2 GB.

If the backups listed under System / Backups in the management console of the sponsor node are larger than 2 GB then a manual cluster join is almost certainly required.

Environment

Symantec Encryption Management Server 10.5 and above.

Cause

The management console uses the standard replication service to copy the database from the sponsor cluster node to the joiner. The replication service is designed to copy changes between cluster members.

However, adding a cluster node to an existing Encryption Management Server requires that almost the whole database be copied. The replication service may not be the best way of accomplishing this if the database is large.

Resolution

Please contact technical support for assistance in carrying out a manual cluster join.

Additional Information

154069 - Best Practices: Environmental Requirements for Symantec Encryption Management Server clustering (AKA PGP Server)

153721 - Creating a Cluster with Symantec Encryption Management Server

153476 - How many PGP Servers are supported in a cluster (Symantec Encryption Management Server)?

153412 - Troubleshooting: Symantec Encryption Management Server Clustering

163930 - Using the Manual Join Process to add cluster when the PGP Server backups are large (larger than 5GBs) - Symantec Encryption Management Server

222372 - Encryption Management Server clustering and replication uses network Interface 1

EPG-29920