beautypg.com

Multi-master replication deployment, Table 7–1 – Sun Microsystems 8190994 User Manual

Page 140

background image

The sample deployment scenarios include:

“Multi-Master Replication Deployment” on page 140

“Multi-Host Deployment with Windows NT” on page 141

Multi-Master Replication Deployment

In a multi-master replication (MMR) deployment, two Directory Server instances are installed
on different hosts. It is possible to run the hosts on different operating systems, but in this
scenario, both hosts are running on the same operating system.

Table 7–1

and

Figure 7–2

illustrate how the Identity Synchronization for Windows components

are distributed between the two hosts.

TABLE 7–1

Component Distribution in a Multi-Master Replication Deployment

Host 1

Host 2

Directory Server (one instance) as the secondary
master for synchronized users

Directory Server (one instance) as the preferred
master for synchronized users

Core (Message Queue, Central Logger, System
Manager, and Console)

Directory Server Plugin

Active Directory Connector

Directory Server Connector

Directory Server Plugin

The migration process keeps on-demand password synchronization running continuously on
the preferred master or on the secondary master.

Note –

If both hosts are running on a Solaris operating system, then a third host running

Windows 2000 with Active Directory is required for synchronization purposes only. (No
components would be installed on the third host.)

The following figure illustrates the process for migrating Identity Synchronization for Windows
in a MMR deployment.

Other Migration Scenarios

Sun Java System Directory Server Enterprise Edition 6.0 Migration Guide • March 2007

140

Sun Confidential: Registered