15.19. Forcing Replication Updates
15.19. Forcing Replication Updates If you stop a Directory Server instance that is involved in replication for regular maintenance, you must update the replication immediately when it comes back online. In the case of a supplier in a multi-supplier environment, the directory information needs to be updated by an other supplier in the setup. In other cases, for example if you take down a hub or a dedicated consumer for maintenance and then come back online later, the supplier server needs to update the status. Prerequisites The replication is set up. The consumer has been initialized. Procedure Check if the replication agreement has an update schedule configured: 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 below, note the value: If an update schedule is configured, enter the following command to temporary disable it: Temporarily disable the replication agreement: Re-enable the replication agreement to force the replication update: If a replication schedule was configured at the beginning of this procedure, set the schedule to the value:
dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt get --suffix=" dc=example,dc=com " agreement_name nsDS5ReplicaUpdateSchedule: 0800-2200 0246 dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt set --schedule \* --suffix=" dc=example,dc=com " agreement_name dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt disable --suffix=" dc=example,dc=com " agreement_name dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt enable --suffix=" dc=example,dc=com " agreement_name dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt set --schedule " 0800-2200 0246 " --suffix=" dc=example,dc=com " agreement_name