cancel
Showing results for 
Search instead for 
Did you mean: 

Does Super-Agent require a Replication task?

Guys, not sure aout the exact community to post the question , so posting here.

I am using superagents in our environment from a quite long time now and we use the procedure of changing policy that converts an agent to Super agent.

We use lazy caching option as well and provides the path of the repository folder in the policy.

There is no server task that is created for repository replication. But all the superagnts are updated with latest DAT packages everyday.

Now while I was checking the repository replication report, it shows the logs as below:

    

NameTypeStatusLast Replication Time
ePOSA_1DistributedLast replication succeeded10/22/2014 12:47
ePOSA_2DistributedLast replication succeeded10/22/2014 14:42
ePOSA_3DistributedLast replication succeeded10/22/2014 11:40
ePOSA_4DistributedLast replication succeeded10/22/2014 11:41
ePOSA_5DistributedLast replication succeeded10/22/2014 13:40
ePOSA_6DistributedLast replication succeeded10/22/2014 14:00
ePOSA_7DistributedLast replication succeeded10/22/2014 10:57
ePOSA_8DistributedLast replication succeeded10/22/2014 11:00
ePOSA_9DistributedLast replication succeeded10/22/2014 10:47
ePOSA_10DistributedLast replication succeeded10/22/2014 11:35
ePOSA_11DistributedLast replication succeeded10/22/2014 11:31
ePOSA_12DistributedLast replication succeeded10/22/2014 11:25
ePOSA_13DistributedLast replication succeeded10/22/2014 11:22
ePOSA_14DistributedLast replication succeeded10/22/2014 11:26
ePOSA_15DistributedLast replication succeeded10/22/2014 11:45
ePOSA_16DistributedLast replication succeeded10/22/2014 11:40
ePOSA_17DistributedLast replication succeeded10/22/2014 12:16
ePOSA_18DistributedLast replication succeeded10/22/2014 11:30
ePOSA_19DistributedLast replication succeeded10/22/2014 11:29
ePOSA_20DistributedLast replication succeeded10/22/2014 11:38
ePOSA_21DistributedLast replication succeeded10/22/2014 11:41
ePOSA_22DistributedLast replication succeeded10/22/2014 11:28
ePOSA_23DistributedLast replication succeeded10/22/2014 11:13
ePOSA_24DistributedLast replication succeeded10/22/2014 11:34
ePOSA_25DistributedLast replication succeeded10/22/2014 11:35
ePOSA_26DistributedLast replication succeeded10/22/2014 11:19
ePOSA_27DistributedLast replication succeeded10/22/2014 11:45
ePOSA_28DistributedLast replication succeeded10/22/2014 11:18
ePOSA_29DistributedLast replication succeeded10/22/2014 11:17
ePOSA_30DistributedLast replication succeeded10/22/2014 12:44
ePOSA_31DistributedLast replication succeeded10/22/2014 11:27
ePOSA_32DistributedLast replication succeeded10/22/2014 11:26
ePOSA_33DistributedLast replication succeeded10/22/2014 11:14
ePOSA_34DistributedLast replication succeeded10/22/2014 11:30
ePOSA_35DistributedLast replication succeeded10/22/2014 11:32
ePOSA_36DistributedLast replication succeeded10/22/2014 11:10
ePOSA_37DistributedLast replication succeeded10/22/2014 11:38
ePOSA_38DistributedLast replication succeeded10/22/2014 11:20
ePOSA_39DistributedLast replication succeeded11/25/2014 9:40
ePOSA_40DistributedLast replication succeeded11/25/2014 9:46
ePOSA_41DistributedLast replication succeeded11/4/2014 12:27
ePOSA_42DistributedLast replication succeeded10/22/2014 11:14
ePOSA_43DistributedLast replication succeeded10/22/2014 11:12
ePOSA_44DistributedLast replication succeeded10/22/2014 10:51
ePOSA_45DistributedLast replication succeeded10/22/2014 12:54
ePOSA_46DistributedLast replication succeeded10/22/2014 11:56
ePOSA_47DistributedLast replication succeeded10/22/2014 11:41
ePOSA_48DistributedLast replication succeeded10/22/2014 11:17
ePOSA_49DistributedLast replication succeeded10/22/2014 11:25
ePOSA_50DistributedLast replication succeeded10/22/2014 11:28
ePOSA_51DistributedLast replication succeeded10/22/2014 11:09
ePOSA_52DistributedLast replication succeeded11/12/2014 9:58
ePOSA_53DistributedLast replication succeeded11/25/2014 10:35
ePOSA_54DistributedLast replication succeeded10/22/2014 11:59
ePOSA_55DistributedLast replication succeeded10/22/2014 11:22
ePOSA_56DistributedLast replication succeeded10/22/2014 11:29
ePOSA_57DistributedLast replication succeeded10/22/2014 12:21
ePOSA_58DistributedLast replication succeeded10/22/2014 11:12
ePOSA_59DistributedLast replication succeeded10/22/2014 12:00
ePOSA_60DistributedLast replication succeeded10/22/2014 11:46
ePOSA_61DistributedLast replication succeeded10/22/2014 11:35
ePOSA_62DistributedLast replication succeeded11/25/2014 9:26
ePOSA_63DistributedLast replication succeeded10/22/2014 10:47
ePOSA_64DistributedLast replication succeeded10/22/2014 10:50
ePOSA_65DistributedLast replication succeeded10/22/2014 11:23
ePOSA_66DistributedLast replication succeeded10/22/2014 11:01
ePOSA_67DistributedLast replication succeeded11/25/2014 9:26
ePOSA_68DistributedLast replication succeeded10/22/2014 10:51
ePOSA_69DistributedLast replication succeeded10/22/2014 11:03
ePOSA_70DistributedLast replication succeeded10/22/2014 10:55
ePOSA_71DistributedLast replication succeeded10/22/2014 11:04
ePOSA_72DistributedLast replication succeeded10/22/2014 10:53
ePOSA_73DistributedLast replication succeeded10/22/2014 10:52
ePOSA_74DistributedLast replication succeeded10/22/2014 10:48
ePOSA_75DistributedLast replication succeeded10/22/2014 11:10
ePOSA_76DistributedLast replication succeeded10/22/2014 11:12
ePOSA_77DistributedLast replication succeeded10/22/2014 10:48
ePOSA_78DistributedLast replication succeeded10/22/2014 10:51
ePOSA_79DistributedLast replication succeeded10/22/2014 10:53
ePOSA_80DistributedLast replication succeeded10/22/2014 11:09
ePOSA_81DistributedLast replication succeeded10/22/2014 10:49
ePOSA_82DistributedLast replication succeeded10/22/2014 11:30
ePOSA_83DistributedLast replication succeeded10/22/2014 11:12
ePOSA_84DistributedNeeds first update
ePOSA_85DistributedLast replication failed
ePOSA_86DistributedNeeds first update
ePOSA_87DistributedNeeds first update
ePOSA_88DistributedNeeds first update
ePOSA_89DistributedLast replication failed7/29/2014 9:12
ePOSA_90DistributedLast replication failed3/6/2014 14:33
ePOSA_91DistributedNeeds first update
ePOSA_92DistributedLast replication failed
ePOSA_93DistributedLast replication failed7/29/2014 10:21
ePOSA_94DistributedLast replication failed3/6/2014 14:46
ePOSA_95DistributedNeeds first update
ePOSA_96DistributedNeeds first update
ePOSA_97DistributedNeeds first update
ePOSA_98DistributedNeeds first update
99DistributedNeeds first update

Am I missing something here? Do I need to create the replication task? We have migrated the ePO console from 4.6 to 5.1 recently. So is it like that the task was created previously but got deleted during migration?

9 Replies
Reliable Contributor exbrit
Reliable Contributor
Report Inappropriate Content
Message 2 of 10

Re: Does Super-Agent require a Replication task?

You would never get help with this in Community Interface Help so I have moved it to Business > ePO for better support.

----

Peter

Moderator

Re: Does Super-Agent require a Replication task?

Thank You Ex_Brit !!

rackroyd
Level 16
Report Inappropriate Content
Message 4 of 10

Re: Does Super-Agent require a Replication task?

Lazy Cache is asynchronous, per the product guide:

"Lazy Caching feature allows SuperAgents to retrieve data from ePolicy Orchestrator servers only when requested by a local agent node."

So when lazy cache is enabled you don't (and indeed should not actually make) a replication task for those SuperAgent Repositories.

vidrine
Level 9
Report Inappropriate Content
Message 5 of 10

Re: Does Super-Agent require a Replication task?

Outside of lazy caching, though.  You would want need a server tasks created/enabled to trigger the replication to distributed repos.

Screen Shot 2015-01-21 at 5.42.25 PM.png

Re: Does Super-Agent require a Replication task?

Hi @shwetimaverma


Did you get an answer to this? If provided the correct answer could you please mark this discussion as 'Answered' so other could benifit from your question.

Many Thanks

Rich
Volunteer Moderator

Re: Does Super-Agent require a Replication task?

Hi , We have same policy configured as has mentioned. But I need a firm clarification if the task is required or not? Are there any kind of bandwidth consumption that is why Lazy caching is all good?

Regards,

SV

Reliable Contributor ansarias
Reliable Contributor
Report Inappropriate Content
Message 8 of 10

Re: Does Super-Agent require a Replication task?

Hello,

It is required because sometimes SuperAgent repository listing does not accurately list the contents of a SuperAgent folder. I'll prefer to remove LazyCache option in all Super Agent policy.

When selecting a SuperAgent Distributed Repository in ePolicy Orchestrator (ePO) 4.6 (that has Lazy Cache enabled), the Master Repository contents are listed. While the contents of the Master Repository are available (on demand) to the clients, this can be misleading. When using Lazy Cache, only content requested by agents is downloaded to the SuperAgent repository folder and not the whole contents of the Master Repository.

Hope this will clear your doubts.

Highlighted
ajha1
Level 9
Report Inappropriate Content
Message 9 of 10

Re: Does Super-Agent require a Replication task?

Hi shetimatmaverma,

As per the details provided by you, It looks like there is server task that it replicating Super Agent Distributed Repository. Else you will not see SA Distributed Repository in th he repository replication report.

Please check Menu - Automation - Server Task and see if there is any Server task that is configured to Replicate SA Distributed Repository. If you are not able find the Server task, and need assistance, then create a SR with McAfee Support and a Support Engineer will assist you further.

As rackroyd mentioned when lazy cache is enabled you don't (and indeed should not actually make) a replication task for those SuperAgent Repositories.


Please check the below youtube video to understand '' How Lazy caching works'


https://www.youtube.com/watch?v=4ZCu18I58uA


You can also check the below community link


Regards,

- AJ

Re: Does Super-Agent require a Replication task?

Hi Ajaykant.. thanks for your reply. I searched for the server tasks and couldnot found any.

While browsing over internet, I read somewhere that when we upgrade ePO from 4.6 to 5.1 some server tasks get deleted. Is it the issue that now I cannot see the task ?

Regards,

Sv

More McAfee Tools to Help You

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community