Skip navigation
McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams
This discussion is archived
1397 Views 6 Replies Latest reply: Nov 30, 2012 11:13 AM by JoeBidgood RSS
random543 Newcomer 4 posts since
Jul 9, 2012
Currently Being Moderated

Nov 27, 2012 6:31 PM

Partial repository replication

Hi,

we're running ePO 4.5.4 with multiple UNC distributed repositories. Currently our repository replication takes up to 4.5 hours and slows our WAN considerably. The majority of this daily transfer is the avvdat-nnnn.zip file. Of course most of the users in the remote branch sites are on the network daily so rarely refer to this file but rather receive incremental DAT updates.

 

  • Can we exclude the large avvdat-nnnn.zip from daily replication?
  • Can it be replicated on weekends/after hours only? - but the incremental replicated immediately
  • If an endpoint was rebuilt and required an entirely new DAT would it grab a avvdat-nnnn.zip DAT which is a few days old and then perform incrementals or will it simply fail as the avvdat-nnnn.zip as stated in the avvdat.ini does not exist? Failing this will it fall-back to the master repository?

 

Any help to reduce the distributed repository replication would be gratefull.

 

Thanks.

  • mischaboender The Place at McAfee Member 105 posts since
    Oct 3, 2011
    Currently Being Moderated
    1. Nov 28, 2012 1:24 AM (in response to random543)
    Re: Partial repository replication

    You might want to look into the LazyCaching feature of McAfee Agent 4.6.

     

    Here's what the ePO 4.6 Product Guide says about LazyCaching:

     

    How the cache works

     

    When a client system first requests content, the SuperAgent assigned to that system caches that content. From that point on, the cache is updated whenever a newer version of the package requested is available in the Master Repository.

     

    The SuperAgent is guaranteed only to store content required by the agents assigned to it because it does not pull any content from the McAfee ePO server until requested from a client. This minimizes traffic between the SuperAgent and the McAfee ePO server. While the SuperAgent is retrieving content from the Master Repository, client system requests for that content are paused.

  • mischaboender The Place at McAfee Member 105 posts since
    Oct 3, 2011
    Currently Being Moderated
    2. Nov 28, 2012 1:45 AM (in response to random543)
    Re: Partial repository replication

    Here's a nice YouTube video that explains the LazyCaching:

     

  • Tristan Veteran 790 posts since
    Dec 8, 2009
    Currently Being Moderated
    4. Nov 29, 2012 4:06 AM (in response to random543)
    Re: Partial repository replication

    If your looking at a way of managing DAT bandwidth usage to low bandwidth sites and your ePO server is on Windows 2008/2008r2 then the policy based QoS bandwidth management you have within group policy is a possible solution.

     

    You can specify the total amount of bandwidth the server will 'serve' to a specific IP range/subnet/protocol/port range.

     

    http://technet.microsoft.com/en-us/library/cc771283.aspx

     

    http://technet.microsoft.com/en-us/library/dd919203(v=ws.10).aspx

     

    Replication might take longer but the network hit will be less. The other option is to replicate your repos at night an not during the day

     

    Message was edited by: Tristan on 29/11/12 10:05:53 GMT

     

    Message was edited by: Tristan on 29/11/12 10:06:22 GMT
  • JoeBidgood McAfee SME 2,868 posts since
    Sep 11, 2009
    Currently Being Moderated
    6. Nov 30, 2012 11:13 AM (in response to random543)
    Re: Partial repository replication

    If I were to use the lazycaching option I'm not sure if the entire 'package' will be transferred at first request, not just the .gem and ini files. Remeber that the large avvdat-nnnn.zip file is part of the full DAT package.

     

    Just to clarify this point, the caching is done at the file level - so if none of the clients on the site need the full zip, then it will not be downloaded. Only those files that the clients request are pulled over and cached.

     

    HTH -

     

    Joe




    (Please post questions to the forum, as I am unable to respond to private messages. Thanks!)



More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • Correct Answers - 5 points
  • Helpful Answers - 3 points