Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Shared Insight Cache - Load balancing

Created: 10 Mar 2012 • Updated: 13 Mar 2012 | 4 comments
pete_4u2002's picture
6 Agree
0 Disagree
+6 6 Votes
Login to vote
Status: In Review

Is there a possibility of having multiple Shared Insight server configured in the policy so that they act as in load balance. This might be helpful, if one of the shared insight cache service is re-started/down then the DB will have to build from scratch, the client may not have the advantage of improving performance. If the other SIC server is present client go to that server and get to know whether to scan or not, hence performance is not compromised.

Comments 4 CommentsJump to latest comment

ScottM 2's picture

Not a bad idea, the sharing between insight caches wouldn't need to be as high priority as them responding to clients, just a frequent sharing so that you keep the cache data.

0
Login to vote
John Cooperfield's picture

From  http://www.symantec.com/docs/TECH174123

"Only one SIC server IP address or hostname can be configured for each SEP Virus and Spyware Protection policy. It may be necessary to split Client Groups up based on SIC size limitations in large VDI infrastructures. Alternatively, a DNS alias (A record) can be created to allow DNS round-robin between several SIC servers."

HTH

0
Login to vote
ScottM 2's picture

I think the idea would be so that it only has to be learned into a cache once and the sharing could endure if one of the servers needs to be rebooted (like Microsoft Patch time). DNS though is exceptionally useful, we use it so that different hubs can always communicate with their local cache without needing to use an AV policy for each.

0
Login to vote