Jump to content

Archived

This topic is now archived and is closed to further replies.

DarylI

ESET with NSX

Recommended Posts

Hi there, just wondered if there was any guidance or documentation on scale - ie: Max number of VM's per Virtual Appliance / Virtual Agent?

Share this post


Link to post
Share on other sites

Hi Daryll,

There is no official scaling document yet. Please, could you tell us, how many VMs do you have per Host (interval) and how many hosts do you have?

Thank you

Share this post


Link to post
Share on other sites

Thanks Matus, 

We will be implementing a Cloud Pod Architecture, potentially scaling to 50,000 Users. So 2000 connections per Resource Block and 10,000 per Pod. This will also be across 2 data centres so wondered if there the ESET Remote Administrator can be configured in a Cluster across both Data Centres or would we configure each Data Centre as an individual Instance?

Share this post


Link to post
Share on other sites

Hi Daryll,

thank you for your answer. Regard ESET Remote Administrator, for detail sizing of ESET Remote Administrator, please check our documentation:

ESET Remote Administrator does not support clustering for the case you have described. For such installation, ERA Proxy should be used, and then reporting to one centralized server.

Regarding ESET Virtualization Security for VMware, we're currently evaluating your scale. Are you willing to deploy VMware agent-less protection, not standard ESET Endpoint, right?

Can you tell us, whether those VDIs are persistent or non-persistent? 

Thank you very much.

Share this post


Link to post
Share on other sites

Thanks!

Yes we will be deploying Agent-less protection and on non-persistent VDI as well as RDSH.

Share this post


Link to post
Share on other sites

Hi DarylI,

thank you for your answer. I got a better picture now so I can provide a more relevant answer.

First of all, unfortunately, a current version of ESET Remote Administrator doesn't handle non-persistent VDIs very good. In case the new machine is created, it'll appear as new machine and it's not linked with old one. This is something which is already in progress and will be fixed in next version of ESET Remote Administrator (ERA) in the middle of the year. 

Another thing is, that 50,000 VDs at the same time is too much for Virtual Agent Host (VAH) component, which responsibility is to connect ESET Remote Administrator with VMs. All virtual machines would be protected without any issues, however in case of assigning new policy, creating new tasks or transfers of logs fro VMs to ERA would be very slow. It would be great if there would be multiple VAH components deployed, but current limitation is 1 VAH per 1 NSX Manager and VMware limits is 1 NSX Manager to 1 vCenter.

In case you'd manage this infrastructure with multiple vCenters where you'd have deployed multiple NSX Managers, you could have multiple VAH components. From our tests it seems that 20,000 VMs is max which VAH is able to handle and personally I'd recommend lower number. ESET Remote Administrator can however handle 50,000 machines without any issues (you'll need however appropriate HW on that server, see links above).

In case of further questions, do not hesitate to contact me.

Thank you very much.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×