Sun Directory Server 5.2 6-Way MMR – part 8 – Enable Directory Server backends for updates
Once the directory server replica’s are configured and initialized, the final step is to enable them to accept updates.
This step was added as there is a necessary catch-up time when initializing MMR (especially in a busy environment); where by the time an instance is initialized, it is out-of-date until all the subsequent updates have been propagated. When I had to do this the first time, I was working off static data, and didn’t need to worry about performing this when the updates have been propagated, as there were no updates.
The only instance and suffixes that do not need to be enabled are those on ultimate master, which had all the data initially. All other instances need to be enabled after the replica’s have caught up.
In summary, those instances are:
ds0: nothing needs to be enabled
ds1: user/group, o=internet, o=piserverdb, o=pab, o=comms-config, o=netscaperoot
ds2: user/group, o=internet, o=piserverdb, o=pab, o=comms-config, o=netscaperoot
ds3: user/group, o=internet, o=piserverdb, o=pab, o=comms-config, o=netscaperoot
ds4: user/group, o=internet, o=piserverdb, o=pab, o=comms-config, o=netscaperoot
ds5: user/group, o=internet, o=piserverdb, o=pab, o=comms-config, o=netscaperoot
I’ve created an example command set to enable a directory server backend.
