Moving the Symantec Endpoint Protection Manager from one computer to another without breaking client communications or losing data

Article:TECH171767  |  Created: 2011-10-13  |  Updated: 2014-06-11  |  Article URL http://www.symantec.com/docs/TECH171767
Article Type
Technical Solution


Issue



You need to replace an existing Symantec Endpoint Protection Manager (SEPM) computer without causing a disruption for your existing Symantec Endpoint Protection (SEP) clients or losing client policies, group memberships, or historical reporting data.


Solution



The method used to replace your Symantec Endpoint Protection Manager (SEPM) will vary depending on whether the SEPM is a member of a site using a Microsoft SQL Server database, or an embedded database site.

 

For embedded databases

Follow the disaster recovery steps for your version of SEPM, making sure to gather the database backup and recovery file(s) from your existing manager, and restore the database and recovery files to the new manager.

Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

Symantec Endpoint Protection 11.x: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

For Microsoft SQL server databases

  1. Gather the recovery file from the existing manager. For more information on SEPM recovery files, see Symantec Endpoint Protection Manager recovery file content details.
  2. Decommission the existing manager, making sure it is no longer able to connect to the Microsoft SQL server hosting the SEPM database.
  3. Ensure the new manager has the same hostname as the existing manager.
    1. If desired, configure the new manager with the same IP address as the existing manager.
  4. Install the SEPM to the new manager making sure the match the version of SEPM to the existing server.
  5. Use the following step In the Management Server Configuration Wizard (MSCW):
    1. On the Welcome screen, select Install an additional management server to an existing Site.
    2. Check use a recovery file to restore communication with previously deployed clients.
    3. Browse for the recovery file you exported from the existing manager in step 1 of this process. and click Next.
    4. Ensure the name in the Server name field matches what was entered for the existing server exactly, including all capitalization and punctuation marks.
    5. Click Next.
    6. Follow the rest of the prompts in the MSCW, providing the correct Microsoft SQL server configuration and authentication information, allow the MSCW to update the SEPM database.

 





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


Terms of use for this information are found in Legal Notices