Endpoint Protection

 View Only
Expand all | Collapse all

SEPM configuration is stucked on Replicating Database

  • 1.  SEPM configuration is stucked on Replicating Database

    Posted Apr 07, 2011 05:23 AM

    Hi All,

    We have the Central SEPM site SEP RU6 MP2. Another addtional site is installed with RU6 MP3. While configuring the same as an additional site the replication wizard is still running since yesterday. Is this because of version mismatch?

    Can anybody please suggest.

    Thanks in advance.

    Sabyasachi



  • 2.  RE: SEPM configuration is stucked on Replicating Database

    Broadcom Employee
    Posted Apr 07, 2011 05:30 AM

    For replication this is better that both Managers are in the same version.

    Please migrate SEPM RU6 MP2 to RU6 MP3:

    Migrating to Symantec Endpoint Protection 11.0.6300 (RU6 MP3)
    http://www.symantec.com/business/support/index?page=content&id=TECH155655



  • 3.  RE: SEPM configuration is stucked on Replicating Database
    Best Answer

    Broadcom Employee
    Posted Apr 07, 2011 06:25 AM

     

      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



  • 4.  RE: SEPM configuration is stucked on Replicating Database

    Trusted Advisor
    Posted Apr 07, 2011 10:12 AM

    Hello,

    Your Answer could be answered by this Symantec Knowledgebase Article below:

     

     

    1) Does Symantec Endpoint Protection Manager support replication between sites running different versions?
     
    http://www.symantec.com/business/support/index?page=content&id=TECH92235
     
    2) About Maintaining Consistency of Software Versions throughout a SEP 11 Organization
     
    http://www.symantec.com/business/support/index?page=content&id=TECH131660
     
     
    Hope that answers all your Doubts.
     
     


  • 5.  RE: SEPM configuration is stucked on Replicating Database

    Posted Apr 07, 2011 10:27 AM

    Hi... 

    why do you suggest  "Make sure Liveupdate schedule is NOT set to “Continuous” or “Every 4 hours”."     I understand not setting this for "Continuous",  but why not do LiveUpdate every 4 hours?

    Doug



  • 6.  RE: SEPM configuration is stucked on Replicating Database

    Broadcom Employee
    Posted Apr 07, 2011 10:57 AM

    Hi DougAuto,

    When we do replacation first time we don't know how much time it will take to replicate, how much exact data will get replicate. So it may take more than 4 hours so to be on safer side do not set it to every 4 hours. So there would be less posibility of replication failure on initial stage.

    To determine a good frequency for replication observe how long it takes for a replication to complete by reviewing the System: Server Activity logs (SEPM -> Monitors -> Logs tab -> Log type: System -> Log content: Server Activity -> Time range: Past week -> View Log button). In these logs the time of replication start and completion is logged and timestamped. Make sure that this time from start to finish is always well below your configured replication interval.



  • 7.  RE: SEPM configuration is stucked on Replicating Database

    Posted Apr 07, 2011 11:29 AM

    I have 2 comments:

    1) The original statement said not to set LiveUpdate to 4 hours... not replication.    

    2)  In the server replication partner settings you have no real choice on how often to replicate.   Its either Hourly,   Daily or Weekly... you have no option to set replication for say, every 6 hours.

    If we are talking about replication then... if it takes my SEPMS 1 hour and 15 minutes to replicate, I would have to set my SEPMS to replicate daily (which is too long an interval). 

    I think this is a weakness in the SEP replication configurations that could be enhanced (giving me more flexibility in the replciation schedule)

    Doug



  • 8.  RE: SEPM configuration is stucked on Replicating Database

    Broadcom Employee
    Posted Apr 07, 2011 11:34 AM

    I agree with you that the replication schedule does not give us too much flexibility. For that I raised the idea:

    https://www-secure.symantec.com/connect/ideas/replication-schedule

    Please vote if you agree/disagree



  • 9.  RE: SEPM configuration is stucked on Replicating Database

    Broadcom Employee
    Posted Apr 07, 2011 12:20 PM

    Hi DougAuto,

    I am agreed with you, base concept is Liveupdate schedule and Replication should not overlap with each other.



  • 10.  RE: SEPM configuration is stucked on Replicating Database

    Posted Apr 07, 2011 01:39 PM

    You got my vote!



  • 11.  RE: SEPM configuration is stucked on Replicating Database

    Posted Apr 19, 2011 01:26 AM

    Hi,

    I cancelled the replication. Degraded the version of replication partner to the version of the Central SEPM. Tried to join that as a replication partner again. After putting  the credential while configuration, the site name of the replication partner reflects at Cental Site which was not happened previously. This time the replication of database was going on for an hour & completed.

    Thanks a lot for your cooperation.

    Regards,

    Sabyasachi