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
4220 Views 5 Replies Latest reply: Feb 15, 2011 3:28 AM by JoeBidgood RSS
DC-SG Apprentice 69 posts since
Feb 16, 2010
Currently Being Moderated

Feb 4, 2011 9:59 AM

SADR (SuperAgent Distributed Repository)

Greetings All,

 

I read an article about SADR somewhere. (I think it’s in McAfee KB though I cannot find the article anymore). That article showed the number of clients versus # of SADR and traffic time. I remember that the article did not show any SADR if an ePO server supporting less than 1000 clients, partiuclarly in a non-WAN environment. My network is just a LAN.  It also has only about 250 clients. All clients are in the same building though they are on different floors. 

 

Now I would like to ask you 3 questions:

 

Q1: Do I need to have a SADR based on the number of clients my ePO server supports and the network is not a WAN?

 

Q2: Currently, my ePO server (vesion 4.0, HIPS 7.0) does not have a SADR. If I have to implement SADR (due to some new requirements), what is the impact of the newly created SADR on the current clients? Although I have a very good client organization for my ePO, few subnets have only 2 or 3 clients due to their physical locations (I.E. on different floors).

 

Q3: Still suppose that I have to implement SADR, should I wait until I upgrade my ePO to 4.5 (which I predict that I have to it soon)?

 

Thank you very much in advance for your adices and comments.

 

Best Regards,

 

DC-SG

  • JoeBidgood McAfee SME 2,868 posts since
    Sep 11, 2009
    Currently Being Moderated
    1. Feb 4, 2011 10:15 AM (in response to DC-SG)
    Re: SADR (SuperAgent Distributed Repository)

    From what you describe here, I would think a distributed repository (of any kind - not just a superagent) is not required. The time you would start to need a distributed repo would be if the number of client machines updating from the master repo was adversely affecting the ePO server itself.

     

    HTH -

     

    Joe




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



  • joeleisenlipz Champion 194 posts since
    Oct 18, 2010
    Currently Being Moderated
    3. Feb 14, 2011 12:38 PM (in response to DC-SG)
    Re: SADR (SuperAgent Distributed Repository)

    Super Agents basically enable two functions:

    1. Distributed repository (glorified file share)
    2. Broadcast wake-up call (minor traffic-saving function)

     

    The broadcast wake-up call only saves on out-bound traffic from the ePO server--NOT the return traffic, which is the substantially larger traffic anyway.

     

    In your case, the ePO server would direct your single Super Agent to broadcast to it's segment, all the agents in that segment would then Collect&Send Props back to ePO, and any uncovered segments would blissfully continue (not communicating) until their regular communication interval rolls around.

     

    Most people just send a normal, direct wake-up call to the system they care about. 99% of the people never even know about the broadcast wake-up, and that's the part where the segments matter.

  • JoeBidgood McAfee SME 2,868 posts since
    Sep 11, 2009
    Currently Being Moderated
    5. Feb 15, 2011 3:28 AM (in response to DC-SG)
    Re: SADR (SuperAgent Distributed Repository)

    (Two Joes - very confusing )

     

    This is exactly correct. In reality about the only time that the superagent wakeup call / subnet stuff becomes relevant is if  you have Global Updating enabled, as it's one of the mechanisms GU uses.

     

    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 (0)

Legend

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