How replication works

Article:HOWTO55328  |  Created: 2011-06-29  |  Updated: 2011-12-16  |  Article URL
Article Type
How To


How replication works

Replication enables data to be duplicated between databases one separate sites so that both databases contain the same information. If one database fails, you can manage the entire site by using the information on the database from another site.

A partner is a management server on another site with a different database and management servers. A site may have as many partners as needed. Each partner, or remote site, connects to the main site or local site, which is the site that you are logged on to. All sites that are set up as partners are considered to be on the same site farm.

Each site you replicate data with is either a replication partner or a site partner. Both replication partners and site partners use multiple servers, but the database they use and the way they communicate is different:

  • Replication partners can use either an embedded database or a Microsoft SQL Server database. The management servers do not share the database. All replication partners share a common license key.

  • Site partners share a single Microsoft SQL database.

All sites typically have the same type of database. However, you can set up replication between one site that has an embedded database and a second site that has a Microsoft SQL Server database. If you use an embedded database, you can only connect one Symantec Endpoint Protection Manager. If you use the Microsoft SQL Server, you can connect multiple management servers or share one database. Only the first management server needs to be set up as a replication partner.

See Determining how many sites you need.

The changes that you make on any partner are duplicated to all other partners. For example, you may want to set up one site at your main office (site 1) and a second site (site 2). Site 2 is a partner to site 1. The databases on site 1 and site 2 are reconciled by using the replication schedule. If a change is made on site 1, it automatically appears on site 2 after replication occurs. If a change is made on site 2, it automatically appears on site 1 after replication occurs. You can also install a third site (site 3) that can replicate data from either site 1 or site 2.

Figure: How replication works between the main site and two remote sites illustrates how replication of data occurs from the main site to two other sites.

Figure: How replication works between the main site and two remote sites

How replication works between the main site and two remote sitesprint_allIn future, use SiteDesign.svg instead

Groups and policies are always replicated. You can choose to replicate logs, updated content, and patches.

See Specifying which data to replicate.

After replication occurs, the database on site 1 and the database on site 2 are the same. Only computer identification information for the servers differs.

If administrators change settings on the sites on a site farm, conflicts can occur.

Table: How the management server resolves conflicts between sites displays the ways that Symantec Endpoint Protection Manager handles the conflicts that the arise.

Table: How the management server resolves conflicts between sites

Conflict type


Two differences cannot exist together.

For example, administrators for site 1 and site 2 both configure an identical Firewall policy setting. On site 1, the setting is enabled. On site 2, the setting is disabled.

The management server retains only the most recently made change.

For example, the site 2 change is retained.

The same variable is created for both sites.

For example, administrators on site 1 and site 2 both add a group with the same name.

The management server retains both changes, adding a tilde and the numeral 1 (~1) after the more recently made variable.

For example, with two groups named as Sales, the most recently named Sales group becomes Sales ~1.

Data can merge without conflict.

For example, the administrator for site 1 adds two Firewall policies and the administrator for site 2 adds five Firewall policies.

The management server merges the changes

For example, the management server displays all seven Firewall policies on both sites.

See Backing up the database and logs.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices