Menu Close
Settings Close

Language and Page Formatting Options

Chapter 11. Forcing replication updates after an instance in a replication environment was offline

If you stop a Directory Server instance that is involved in replication for regular maintenance, the supplier must update the directory data immediately when it comes back online. You can enforce this update using the command line and the web console.

11.1. Forcing replication updates using the command line

Perform the following steps on the suppliers to enforce replication updates for the dc=example,dc=com suffix in example-agreement.

Prerequisites

  • The replication is set up.
  • The consumer has been initialized.

Procedure

  1. Check if the replication agreement has an update schedule configured:

    # dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt get --suffix "dc=example,dc=com" example-agreement

    If the output of the command contains nsDS5ReplicaUpdateSchedule: * or the nsDS5ReplicaUpdateSchedule parameter is not present, no update schedule is configured.

    If nsDS5ReplicaUpdateSchedule contains a schedule, such as shown in the following, note the value:

    nsDS5ReplicaUpdateSchedule: 0800-2200 0246
  2. If an update schedule is configured, enter the following command to temporary disable it:

    # dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt set --schedule \* --suffix "dc=example,dc=com" example-agreement
  3. Temporarily disable the replication agreement:

    # dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt disable --suffix "dc=example,dc=com" example-agreement
  4. Re-enable the replication agreement to force the replication update:

    # dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt enable --suffix "dc=example,dc=com" example-agreement
  5. If a replication schedule was configured at the beginning of this procedure, set the schedule to the previous value:

    # dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt set --schedule "0800-2200 0246" --suffix "dc=example,dc=com" example-agreement

Verification

  • Display the replication status:

    # dsconf -D "cn=Directory Manager" ldap://supplier.example.com repl-agmt status --suffix "dc=example,dc=com" example-agreement
    ...
    Last Update Start: 20210406120631Z
    Last Update End: 20210406120631Z
    Last Update Status: Error (0) Replica acquired successfully: Incremental update succeeded
    ...

11.2. Forcing replication updates using the web console

Perform the following steps on the suppliers to enforce replication updates.

Prerequisites

  • The replication is set up.
  • The consumer has been initialized
  • You are logged in to the instance in the web console.

Procedure

  1. Open the Replication menu.
  2. Select the dc=example,dc=com suffix.
  3. Open the Agreements tab.
  4. Check if the replication agreement has an update schedule configured:

    1. Click the overflow menu next to the agreement, and select Edit Agreement.
    2. On the Scheduling tab, note the values that are currently set.

      replication schedule

      If Use A Custom Schedule is not selected, no schedule is configured.

  5. Click the overflow menu next to the replication agreement, and select Disable/Enable Agreement to disable the agreement.

    The status of the agreement in the State column is now Disabled.

  6. Click the overflow menu next to the replication agreement again, and select Disable/Enable Agreement to re-enable the replication agreement and enforce the replication update.

    The status of the agreement in the State column is now Enabled.

  7. If a replication schedule was configured at the beginning of this procedure, set the schedule to the previous values:

    1. Click click the overflow menu, and select ActionsEdit Agreement.
    2. On the Scheduling tab, set the previous values.

Verification

  • Display the replication status:

    # dsconf -D "cn=Directory Manager" ldap://supplier.example.com repl-agmt status --suffix "dc=example,dc=com" example-agreement
    ...
    Last Update Start: 20210406120631Z
    Last Update End: 20210406120631Z
    Last Update Status: Error (0) Replica acquired successfully: Incremental update succeeded
    ...