hi,
mcafee superagent in some branch doesn't work properly. these agents not flush Replica.log files and repository folders exceed quota size but old files not removed.
i've also defined Repository Replication task to replicate DAT files in midnight. i use these versions:
epo version 5.3.2
Agent Version 5.5.1
is there any problem whith using Lazy Caching & Repository Replication together?
thanks and sorry for bad english.
Solved! Go to Solution.
Yes, there is definitely a problem using replication and lazy caching together. If both are enabled, it can lead to file locks, which can result in replication failures, the issue you are experiencing, failed downloads by clients, etc. Use one or the other and you may need to restart the server or at least agent services once lazy caching is disabled to remove the lock from the files.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Yes, there is definitely a problem using replication and lazy caching together. If both are enabled, it can lead to file locks, which can result in replication failures, the issue you are experiencing, failed downloads by clients, etc. Use one or the other and you may need to restart the server or at least agent services once lazy caching is disabled to remove the lock from the files.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
thanks for your reply.
is there any pre-requirement for superagent in WAN communication (e.x minimum bandwidth or delay)?
if i disable Lazy Cache and only use Repository Replication Task, SuperAgent Repository sync with epo repository or new files added to SuperAgent Repository?
Replication is a push from epo to the repository, so the contents of epo master repository is pushed to the distributed repo. With lazy caching, the superagent pulls the data that clients request on an as needed basis from epo and stores it in its local repo cache for the next client that requests the same data. Lazy caching is preferred above replication to reduce bandwidth requirements and to ensure that the repository is always an up to date site.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
thanks a lot.
i will try what you say.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: