Data Loss Prevention

Is anyone currently using a load balancer for the URL to access the DLP Management console?  I've been asked if we need one.

DLP v 14.6

Enforce server specs: physical Win2012 server with 16GB ram and 2 six core CPUs.

We expect to have at some point maybe 20 simultaneous users viewing incidents and running reports.

When responding either yes or no please provide the number of persons you have using the console. i.e. "We don't use a load balancer and we have ~400 users accessing the console" or "Yes we use a front end load balancer and we have ~400 users accessing the console"

A very few environments use the Veritas Cluster Server (VCS) to load-balance (failover) Enforce especially when response times are documented as SLAs & penalties in picture for delayed incident response.

@Leadvue : When we use VCS configuration it supports Active - Passive. Which means One enforce would be UP other one would be Down. Using this configuration we cannot impelement Load Balancer for accessing console.

@DLP Freak:  Nope we cannot implement load balancer for your requirement.

There is no point load balancing the console, because it's impossible to have an Active/Active DLP Enforce configuration. If you do have a DR Enforce Server, it will be cold/warm standby with the services off, so you'd just be 'load balancing' one system. If you have 2 Enforce Servers, they will fight for Detection Servers (the detection servers will switch back and forth, showing as down on one and running on the other).

The number of simultaneous users will only affect Enforce and Database resources (incidents/reports being run, etc), and your 2 six-core CPUs should suffice in this instance.