Ignore:
Timestamp:
Sep 25, 2011, 2:33:35 PM (11 years ago)
Author:
achernya
Message:
Merge r1973-r1988 from trunk to branches/fc15-dev
Location:
branches/fc15-dev
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • branches/fc15-dev

  • branches/fc15-dev/server/doc/install-ldap

    r1878 r1989  
    162162            M1 <---> M2 <---> S
    163163
    164     3. Set up the rest of the replication agreements at your leisure.
     164    3. Set up the rest of the replication agreements.
    165165
    166166                M1 <---> M2
     
    169169                +--> S <--+
    170170
     171    4. Push a change from every existing server (to the new server), and
     172       then a change from the new server to (all) the existing servers.
     173       In addition to merely testing that replication works, this will
     174       set up the servers' changelogs properly.
     175
     176       If this step is not completed before any server's LDAP server
     177       shuts down, then the replication agreements will fall apart the
     178       next time a change is made. You may wish to intentionally reboot
     179       any servers that look like they want to crash _before_ beginning
     180       this process.
     181
    171182  Here's how you do it.
     183
     184    0. Tell -c scripts not to go off and reboot servers until you're
     185       done (or to get any rebooting done with first).
    172186
    173187    1. Pull open the replication part of the database. It's fairly empty
     
    286300    then try again.
    287301
     302    7. Repeat step 6 to complete the graph of replications (i.e., from
     303    every other server to the new server, and from the new server to
     304    every other server).
     305
     306    Note the only difference between steps 5 and 6 is the lack of
     307    nsDS5ReplicaRefresh: start. That only needs to be done once, to the
     308    new server.
     309
     310    8. If at this point you look at the new server's changelog with
     311    cl-dump (preferably /mit/scripts/admin/cl-dump.pl, to not prompt you
     312    for a password), you won't see the servers you added in step 7. So,
     313    from each of those servers, make a change to some record so it gets
     314    propagated to the new server, and then one from the new server so it
     315    gets propagated to all the existing servers' changelogs. This is
     316    also good for making sure the replication agreements actually work.
     317
    288318Troubleshooting
    289319===============
Note: See TracChangeset for help on using the changeset viewer.