Configuring the Database Security servers to work in cluster mode improves system availability and performance. Cluster mode is configured in the server-cluster.xml file for each server in the cluster.
Install Database Security server and configure one of the Database Security servers to work with an external database.
Install Database Security server on the other systems in the cluster computers.
Stop all Database Security servers.
Rename the file server-cluster-example.xml to server-cluster.xml located in the following location:
<Trellix Database Security Server install dir>\confEdit the file so it contains information about all servers you intend to use in the cluster in this format:
<!-- This is an example server-cluster.xml file. It is used for configuring the server cluster. Each server element host and port configurations should match the Server configuration. Id field must be in the range of 0 to 999. Each server should have a unique id and the id shouldn't be changed onced assigned to a server. In none cluster mode the server uses id 0. Thus, if migrating to cluster mode (for example you have a server running and you wish to move to a cluster configuration) the migrated server should receive id 0. ––> <servers> <server> <!–– either ip or host name --> <host>cluster1.sample.com</host> <!-- https listen port of the server --> <port>8443</port> <id>0</id> </server> <server> <host>cluster2.sample.com</host> <port>8443</port> <id>1</id> </server> <server> <host>192.168.1.101</host> <port>8443</port> <id>2</id> </server> </servers>
Each server XML element should contain these fields:
host — The host name or the IP address of the Database Security server.
Port — The https port of the Database Security server.
id — A unique ID for each server, in the range 0-999.
The Database Security server that has been migrated to work with an external database should be assigned ID of 0.
The ID should not be changed once assigned to a server.
Copy the file server-cluster.xml from
<Trellix Database Security Server install dir>\confto all the servers in the cluster.On the server working with an external database, edit your server-custom.properties file located in
<Trellix Database Security Server install dir>\confdirectory. You can add to it these optional parameters:server.server.address — If the server has different internal and external IP addresses, configure here the internal IP address (as the server sees itself).
For example,
server.server.address=192.168.150.111server.cluster.ip.allow list — A list of IP addresses, which are the only ones allowed to connect to the cluster, separated by semicolons.
For example,
server.cluster.ip.allow list=127.0.0.1;192.168.150.23server.cluster.secret — A shared secret for all the computers in the cluster. Each server will agree to receive connect requests only from other servers in the cluster that have the same secret. If not specified, a default internal secret is used.
For example,
server.cluster.secret=mysecretserver.cluster.keystore — An alternative keystore location, if you want to use a location other than the one in the server.xml file located in the <Trellix Database Security Server install dir>\conf directory.
For example,
server.cluster.keystore=C:\Program Files\McAfee\server\httpsKeystore\.keystoreserver.cluster.keystore.type — The type of the alternative keystore used.
For example,
Trellix.cluster.keystore.type=JKSserver.cluster.keepalive — The time in milliseconds after which the server assumes another cluster computer is down, if it does not receive a connection request from it. The default value is 60000.
For example,
server.cluster.keepalive=100000
Copy the server-custom.properties file to all servers in the cluster.
Restart all cluster servers.
The cluster configuration details can be viewed on the Cluster tab of the System page.