Setting up failover and load balancing

Article:HOWTO55323  |  Created: 2011-06-29  |  Updated: 2012-08-22  |  Article URL http://www.symantec.com/docs/HOWTO55323
Article Type
How To


Subject


Setting up failover and load balancing

The client computers must be able to connect to a management server at all times to download the security policy and to receive log events.

Failover is used to maintain communication with a Symantec Endpoint Protection Manager when the management server becomes unavailable. Load balancing is used to distribute client management between multiple management servers.

You can set up failover and load balancing if you use a Microsoft SQL Server database. You can set up failover with the embedded database, but only if you use replication.  When you use replication with an embedded database, Symantec recommends that you do not configure load balancing, as data inconsistency and loss may result.

To set up failover and load balancing, you add multiple management servers or Enforcers to a management server list.

Table: Process for setting up failover and load balancing lists the tasks that you should perform to set up failover and load balancing.

Table: Process for setting up failover and load balancing

Tasks

Description

Read about failover and load balancing.

You should understand if and when you need to set up a failover and load balancing configurations.

See About failover and load balancing.

Add management servers to a management server list.

You can either use the default management server list or add management servers to a new management server list. A management server list includes the IP addresses or host names of management servers to which clients and Enforcers can connect.

See Configuring a management server list.

Assign the custom management server list to a group.

After you have created a custom management server list, you must assign the management server list to a group.

See Assigning a management server list to a group and location.

Fix communication problems with the management server.

If the management server goes offline, or the client and the management server do not communicate, you should also troubleshoot the problem.

See Troubleshooting communication problems between the management server and the client.


Legacy ID



v51660713_v59371754


Article URL http://www.symantec.com/docs/HOWTO55323


Terms of use for this information are found in Legal Notices