This article describes how to prevent disruptions with Symantec Endpoint Protection (SEP) clients when moving Symantec Endpoint Protection Manager (SEPM) to another server. These steps also help prevent the loss of client policies, group memberships, and historical reporting data.
The method used to replace the 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 best practices for your SEPM version. Make sure that you gather the database backup and recovery file(s) from your existing manager, and restore the database and recovery files to the new SEPM.