Endpoint Protection

Having Symantec enterprise protection manager replication issues with SEP, Merging two sites, one with + 40gig SQL DB, the server a brand new empty SEP Site. Im Going across an OC48 peering point spanning 1000 miles between data centers. Keeps failing on transaction log full errors after 18 hours of repications.   Ith create 

The replication Dir, and the DB actualy get create before the crash, after the crash the sepm service will not start on the down stream replication partner, but the dB is there.

Also the main up stream SEPM shows the other site has successfuly registered with it, but could not connect.

Site are the smae version 11.0.6000.550

   Hi,

  Considerations: Before setting up replication.

1. Network Bandwidth and Link
2. Network Latency.
3. Database Size on the Primary site.
4. If any Firewall, Proxy, Router, etc. exists between 2 sites.
5. Does these Firewall or Routers have packet scanning mechanism built in, as this can strip the zip file that is passed on the link.

Considerations: Adding a new Site to an existing replication partner.

1. Make sure the replication Schedule is not set to “Automatic”.
2. Make sure Liveupdate schedule is NOT set to “Continuous” or “Every 4 hours”.
3. Lower the count of Content revisions in the Liveupdate settings.
4. Purge SEPM Logs.

 Database supported for SQL:

1. Sybase adaptive server anywhere (ASA) 9.0
2. Microsoft SQL 2000 Server with SP4
3. Microsoft SQL 2005 Server with SP2
4. Microsoft SQL 2008 Server (RU5 onwards)

Best Practices

      1.      Versions of the Policy Manager have to be the same.

      2.      Replication schedules should not overlap.

      3.        If replicating over WAN, only replicate the logs.

      4.  Delete Replication Partners when:

1. Upgrading the Policy Manager.
2. If any CRT Approved tools need to executed.
3. Software / Hardware maintenance on the Policy Manager.
4. Backing up database manually.

Please check Tomcat logs from Site 1 and “Install Error” logs from New Site, if the initial replication fails

shrink the DB as well set teh transaction log table to be unlimited till the replication completes.