Best Practice for Doing a Cluster Migration for Symantec Endpoint Encryption

Article:TECH189202  |  Created: 2012-05-21  |  Updated: 2012-07-31  |  Article URL http://www.symantec.com/docs/TECH189202
Article Type
Technical Solution


Environment

Issue



Best practice that needs to be followed for doing the Cluster Migration in the SEE 8.X


Error



NA


Environment



Applicable to all the environments either performing upgrade or new install using the version 8.X onwards.


Solution



 Step 1:- Take the Back Up of the existing SQL server

Step 2:- Set Up the New SQL server
Step 3:- Restore the Database to the New SQL server
Step 4:- Re configure the Existing SEE server to connect to the new remote SQL server.
Step 5:- Make sure that this works before we move forward
Step 6:- Then, Install the new SEE server
Step 7:- Configure it to connect the same SQL server,using the same Database
Step 8:- Verify the New SEE server is able to see the existing data
Step 9:- Then we would verify if the clients reporting to the new server are visible in the old server
This would prove if everything is working fine
Also, if what you are looking for is a Fail over set up then you would need to make sure the server keys are the same.Or else the Clients will only connect to the server they were installed from or had the OTP key changer run from
 Multiple Management Servers can be configured into an NLB cluster for hot fail over capability. Clustering provides additional assurance that Symantec Endpoint Encryption client computers will maintain contact with Management Server at all times
The Install doc "Symantec Endpoint Encryption Management Server Clusters" on page 113 talks about this.



Article URL http://www.symantec.com/docs/TECH189202


Terms of use for this information are found in Legal Notices