Establish One Server Role as Secondary to Another

You can select a server role Entity that contains a logical, predefined set of components (system software or certified third-party software) deployed in the Data Center and Site Zones that provide specific functionality for the system. and then establish another role of the same type and version as its secondary role. This capability is also called "server role pairing."

In this situation, the server role configuration settings and associations of the primary role are duplicated on the secondary role. Also, configuration changes made to the primary server role are automatically applied to the secondary role.

Secondary roles are frequently used in recording environments to support failover, or redundancy, between two managed servers. If the primary server fails, the secondary server can automatically assume the functions of the primary. For example, if a primary Recorder Server fails, the secondary Recorder Server operates as the backup and can assume the recording of calls. With server pairing, the servers are not in operation at the same time and load sharing does not occur between the two servers.

To use this feature, you need to have Edit Installation Hierarchy privileges and also privileges for the role.

In server role pairing, the following applies:

When a primary server role is updated (with information from the Settings tab), all applicable updates are made automatically to the secondary server role.
Fields specific to the secondary role, such as an IP address, are not updated. Select the Settings tab of the secondary role to edit the fields that are specific to the secondary role.
Only active roles can be paired (that is, have a primary/secondary role relationship). Deactivating a role removes the pairing.
A role cannot be paired with a role that is already paired.
When you unpair a primary role, the secondary role is also unpaired.

When you remove a primary role’s association to a Data Source or to Rules, the same associations are also removed on the secondary role. When you add/associate a primary Integration Service to a Data Source, the secondary role is also associated.

You cannot copy settings to a secondary role by using the Copy Role Settings feature.
You cannot use the Create Role from Existing feature if a role is paired.

To establish one server role as secondary to another:

Go to System Management Module that allows performing suite-wide system management activities from a single, Web-based application, the Enterprise Manager.. Under Enterprise, select Settings.
In the Installations tree (left pane), select a primary role that can be paired, such as Recorder Integration Service.
Click Secondary Role. The Paired Secondary Role window displays, showing all eligible role instances.

If pairing is not available for this role, the Secondary Role tab does not appear.
Select a secondary role to be associated to the primary role, keeping the following in mind:
- There can be only one secondary role instance for each primary instance, and only one primary per secondary instance.
- All associations to the role (such as an association to a Recorder) are copied from the primary to the secondary role.
- Associations for the secondary role are disabled, including phone extensions in Member Groups.
Click Save.

If you make changes to the secondary role and click Save, the changes are not passed to the primary role.
If you later decide to unpair the role, select the primary role, and then uncheck the secondary role in the Secondary Role window.

After you make any server role configuration changes, check for any services or applications that require a restart, as discussed in Viewing and Continuing from the Service and Application Notification Pop-Up Window.