Bug 2126503 - Upgrade procedure for a MMR topology
Summary: Upgrade procedure for a MMR topology
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-installation-guide
Version: 11.5
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Evgenia Martynyuk
QA Contact: LDAP QA Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-13 16:00 UTC by thierry bordaz
Modified: 2023-05-02 11:37 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-02 11:37:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-145547 0 None None None 2023-01-30 04:55:20 UTC

Description thierry bordaz 2022-09-13 16:00:12 UTC
Document URL: https://access.redhat.com/documentation/en-us/red_hat_directory_server/12/html/installing_red_hat_directory_server/index

Section Number and Name: 
Upgrade of a MMR topology

Describe the issue: 
I have not seen any documentation explaining how to upgrade a full MMR topology

Suggestions for improvement: 

Suggested steps
For the first instance,

remove replication agreement from/to the instance
export all backends (with replication)
remove instance
upgrade RPM
create instance
configure instance
import backends
recreate RA from/to instance

For the next instances, make sure all direct updates have been replicated on the first instance

remove RA from/to
remove instance
upgrade RPM
create/configure instance
import backends from the first instance export
recreate RA from/to
Prevent direct update on that host until it is fully in sync

 

Additional information:

Comment 1 Evgenia Martynyuk 2022-09-13 16:04:44 UTC
Hi Thierry, 

I hope this sections covers

Comment 2 Pierre Rogier 2022-09-13 18:08:46 UTC
A comment: 
  - This procedure should only be used when upgrading from a major version to another one 
    (For minor upgrade, simply upgrading each instance is OK.)


Note You need to log in before you can comment on or make changes to this bug.