Promoting a server to be a peer

 

Use this information to promote a server to be a peer. Using the forwarding topology created in Creating a master-forwarder-replica topology, you can promote a server to be a peer. In this example you are going to promote the replica (server3) to be a peer to the master server (server1).

1. Connect Web Administration to the master (server1).

2. Expand the Replication management category in the navigation area and click Manage topology.

3. Select the subtree that you want to replicate and click Show topology.

4. Click the arrow next to the Replication topology selection to expand the list of servers.

5. Click the arrow next to the server1 selection to expand the list of servers.

6. Click the arrow next to the server2 selection to expand the list of servers.

7. Click server1 and click Add replica. Create server4. See Creating a replica server. Follow the same procedure to create server5. The server roles are represented by icons in the Web administration tool. Your topology is now:

   • server1 (master)

     • server2 (forwarder)

       • server3 (replica)

     • server4 (replica)

     • server5 (replica)

8. Click server2 and click Add replica to create server6.

9. Click server4 and click Add replica to create server7. Follow the same procedure to create server8. Your topology is now:

   • server1 (master)

     • server2 (forwarder)

       • server3 (replica)

       • server6 (replica)

     • server4 (forwarder)

       • server7 (replica)

       • server8 (replica)

     • server5 (replica)

10. Select server5 and click Move.

    The server you want to move must be a leaf replica with no subordinate replicas.

11. Select Replication topology to promote the replica to a master. Click Move.

12. The Create additional supplier agreements panel is displayed. Peer replication requires each master to be a supplier and consumer to each of the other masters in the topology and to each of the first level replicas, server2 and server4. Server5 already is a consumer of server1, it now needs to become a supplier to server1, server2, and server4. Ensure that the supplier agreement boxes are checked for:

    Table 1.

    	Supplier	Consumer
    ✓	server5	server1
    ✓	server5	server2
    ✓	server5	server4

    Click Continue.

    In some cases the Select credentials panel will pop up asking for a credential which is located in a place other than cn=replication,cn=localhost. In such situations provide a credential object which is located in a place other than cn=replication,cn=localhost. Select the credentials the subtree is going to use form the existing sets of credentials or create new credentials. See Creating replication credentials.

13. Click OK. Your topology is now:

    • server1 (master)

      • server2 (forwarder)

        • server3 (replica)

        • server6 (replica)

      • server4 (forwarder)

        • server7 (replica)

        • server8 (replica)

      • server5 (master)

    • server5 (master)

      • server1 (master)

      • server2 (forwarder)

      • server4 (forwarder)

14. Copy data from server1 to the all the servers. See Coping data to the replica for information on how to do that.

 

Parent topic:

Replication tasks