Endpoint Protection

 View Only

Replication : The Do’s , The Don’t and the Best Practices 

Jan 10, 2011 07:12 PM

Replication : The Do’s , The Don’t and the Best Practices

 

The Do's

  • Replication can only be done with the same version of SEPM
  • The  number of replicated sites should ideally be kept below 5
  • Replication should be done once per day.
  • The value of  “Content revisions to keep” should be set to a  lower value.
  • Disable the Proxy settings  configured in the Primary SEPM .
  • Only replicate logs from the Replication partner

 

The Don'ts

  • The interval of replication should be set in such a way that replication schedules don’t overlap with any other site. This can lead to Database Deadlock and which can in turn cause many issues.
  • Under any circumstance it is not recommended to  go over 20 replicated sites
  • Replication should not overlap with scheduled Liveupdate session
  • Multi-version manager replication should not be done
  • Do not replicate more frequently than once per hour

  

The Best Practices:

 

  • If multiple replication partners are configured, always make sure that the replication schedules don’t overlap. This can lead to Database Deadlock issues.

 

  • If internet connection is present at replication sites, it is advisable to only replicate logs. Content (virus definitions) and install packages need not be replicated as content can be downloaded by the SEPM via liveupdate. For a SEPM to be configured as a replication partner the SEPM version has to be the same in all sites. If SEPM versions are the same, they will have the latest install packages as well.

 

  • Disable the Proxy settings that is configured in the SEPM which is installed on the Primary site. We have seen in SEP version MR4 MP2 and later that this setting conflicts with the replication process.

 

Logs and information required  to troubleshoot replication issues:

Before Collecting the logs set the Log level to finest

 

  • SEPM Tomcat logs from the Primary site and Secondary site using the “CollectLog.cmd” tool which is present in the SEPM\Tools folder.

 

  • SEP Support tool logs from all the sites .A Full data grab is needed.

 

  • If it is a new install of the replication partner, then we will need to collect the SEPM Tomcat logs from the Primary site and the “install error logs” from the Secondary site.

 

  • Network Traces when the replication is failing to check for network issues  ( WireShark or Netmon .)

 

  • The IP Address and Server name of Primary site and the replication partners that are configured is required  . This will help in looking for information in the logs.

 

Statistics
0 Favorited
2 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Oct 22, 2013 09:38 PM

Should still hold true for 12.1

Oct 22, 2013 09:36 PM

Can anyone confirm this? I can't find any relevant documentation relating to replication best practice and 12.1.x

Feb 04, 2012 01:09 AM

Does it holds true for 12.1?

Dec 20, 2011 02:30 AM

Great Article

Feb 18, 2011 06:57 AM

In that case you have to break the replication for a month. We don’t recommend replication between different version because the schema may be different in the replicating SEPM.

Steps that you need to follow

  1. Break the Replication
  2. Upgrade all SEPM’s to Ru6
  3. Enable Replication

Feb 17, 2011 10:03 PM

I have a question about the first Do's:

  • Replication can only be done with the same version of SEPM

We suggest such scenario:

The customer had a MR4 replication SEPM environment which contain three replication partners. They want to migrate to RU6, how should they plan the migration steps? If these three replication partners need to be migrated on one month, then, during this month, some SEPM will be MR4, the other will be RU6. The version will be different during this month of migration.

Any suggest?

Feb 02, 2011 04:18 AM

Thumbs Up...

Jan 26, 2011 03:42 PM

Hey Thanks alot and sorry for the delay  smiley

Jan 26, 2011 03:40 PM

One of the best articles that i have ever seen . It was such an important topic.

Prachand it would have been great if you would have  made it earlier

i remember one of your articles that i liked and give a thums up one was on Epoch and other on Pending file chnages

 

You rock Sir

Related Entries and Links

No Related Resource entered.