Re: Promoting two replicas to master/replica

Mark Reynolds <mareynol@xxxxxxxxxx> · Thu, 28 Jul 2016 16:54:46 -0400



    Hi Gary

    
    On 07/28/2016 03:55 PM, Gary Algier
      wrote:

    
                Hello,

                  
                  I have an old directory server (Sun's) as a master and
                  it is replicating to two slave 389 servers.  I want to
                  pull the plug on the old server and promote one of the
                  replicas to a master.

                  
                Here's what it looks like:

              
                Server A, running old DS.   Master.

                
                Server B, running 389 DS.  Consumer of A.
                Server C, running 389 DS.  Consumer of A.
              
              I want:
              
                Server B, running 389 DS. Master.
                Server C, running 389 DS. Consumer of B.
              
            
            What's the easiest way to make this happen with minimal (0?)
            downtime?

          
          My guess would be I should first make C and consumer of B. 
          But how do I easily "promote" B?

          
        All the docs I find talk about multimaster. 

      
    There is some documentation on this:

    
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Administration_Guide/Managing_Replication-Making_a_Replica_Updatable.html

https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Administration_Guide/removing-supplier-cleanly.html

    
    Anyway, this is actually pretty easy and there should not be any
    down time.

    
    [1] First, you need to convert Server B to a Master.  Follow these
    steps

    
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Administration_Guide/Managing_Replication-Configuring-Replication-cmd.html#Configuring-Replication-Suppliers-cmd

    
    Basically you are just creating a change log and updating the
    replication configuration.  

    
    If there are any agreements to Server A remove them.

    
    [2]  Then you need to start pointing your clients to Server B, as
    opposed to Server A

    
    [3]  Decommission Server A:  Remove the agreements if nothing else!

    
    [4]  Run the cleanAllRUV task to remove the old rid (replica ID)
    that came from Server A

    
    http://www.port389.org/docs/389ds/howto/howto-cleanruv.html

    
    [5]  Initialize Server C:

    
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Administration_Guide/Managing_Replication-Initializing_Consumers.html#Initializing_Consumers-Online_Consumer_Initialization_cmd

    
    If you have a large database you might want to do a LDIF file
    initialization:

    
https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Administration_Guide/Managing_Replication-Initializing_Consumers.html#Initializing_Consumers-Manual_Consumer_Initialization_Using_the_Command_Line

    
    Regards,

    Mark

    
       I don't think I am ready to go there yet.

        
                        -- 

                        
                          Gary Algier

                          
      --
389-users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx

    
--
389-users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx