Endpoint Protection

 View Only

  • 1.  Endpoint Protection 11 to 12 to SQL clustered back end.

    Posted May 19, 2014 02:58 PM

    Hello,

    New to the community forum, and to Endpoint Protection.

    We are presently running, 11.x with the embedded database on a single MS Server 2003.  Our goal is to upgrade to 12.1 and have as a result, a back-ended SQL Server 2012 cluster. 

    Wanting to preserve the import of the managed clients, is there a best practice or recommended KB article? 

    Prelimanary thoughts include:

    1. Backup the current Server 2003 embedded database to a separate folder location (approximate 12GB size).

    1a. Backup the current Server 2003 Endpoint certificates.

    2. Build a SQL 2014 cluster and import the embedded database from step 1 to have the managed clients, etc., from the backup of the embedded database.

    3. Backup the SQL 2014 clustered database.

    4. Build a separate server Endpoint Protection 12.1x on MS Server 2012 (Hyper V or VMware 5.1), (not clustered).

    5. Verify the new Endpoint Protection 12.1x server is connected to the MS SQL 2014 Cluster and verify the success of the managed clients, rules, etc.,

    6. Primarily, we need to preserve the existing managed clients and existing rules while we transistion to a new server and the new back-ended resource.

                                                                                                                                                         

     



  • 2.  RE: Endpoint Protection 11 to 12 to SQL clustered back end.



  • 3.  RE: Endpoint Protection 11 to 12 to SQL clustered back end.

    Posted May 19, 2014 03:52 PM

    1) upgrade to 12.x. Follow Disaster recovery

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

    http://www.symantec.com/business/support/index?page=content&id=TECH160736

    install sepm on new server



  • 4.  RE: Endpoint Protection 11 to 12 to SQL clustered back end.

    Posted May 19, 2014 04:17 PM

    Thank you, _Brian,

     

    In reading this, it seems that first we would:

    1. Prepare for the original SEP server (running 11.x under Server 2003), backup the database and certificate keys.

    2. Follow the "How to move Symantec Endpoint from one machine to another" using a second machine with a different hostname and IP address.  Two follow up questions here please to verify, the second machine of that different hostname and IP address (the second machine to have Server 2012 R2) will have to have not only the same version of Endpoint (in this case 11.x) but will also have to be configured with an embedded database? Will SEP 11.x install on MS Server 2012 R2?  Then perform the two server replication.

    3. After confirming that replication is successful and managed by machine two on the MS Server 2012, then follow the "Moving from the embedded database to Microsoft SQL Server" to MS SQL Server 2012.

    4. Finally, then after step 3, is confirmed successfully, upgrade from SEP 11.x to 12.1.

    5. End result then will be the desired goal: a single SEP 12.1 based on SQL 2012 Cluster on a separate back-ended server cluster, both SEP and SQL running separately on MS Server 2012 R2 platform OS'es.

    -much obliged, Brian in PA.

     

    Have now:  SEP 11.x on Server 2003 with embedded database and thousands of managed clients.

    Desired goal: SEP 12.x on Server 2012 R2 with a back feed from SQL Server 2012 running on MS Server 2012 R2 cluster and containing the replication of the original thousands of managed clients.