• State Not Answered
  • Replies replies
    6
  • Subscribers subscribers
    28
  • Views views
    176
  • Users 0 members are here

Master Replica changes on EBA & EBCA enabled environment.

Sreejith Pidakkal

Hello,

We have three servers (Server A, B, and C) configured in a Replica Ring, with EBA enabled on all of them. In this setup, Server A is designated as the Master Replica, while Server B serves as the EBCA.

If Server A is shut down without first reassigning the Master Replica role to Server B or C, will this cause any impact?

  • 0  

    So Master Replica and EBCA are two different problems.

    I can answer for Master Replica... While it is down, moves, renames, deletes, and schema changes won't properly complete. The Obit will sit trying to get the missing replica to Notified.  This is a general eDir issue.  Schema changes would be specific to the Master being down.

    EBCA is different, still newish and less well known.  You can 'grab' the EBCA role onto a new server, when the old one is dead.  You cannot (at least I do not know how) move it easily around. They only support moving it, when the old one is dead.  Not sure what happens if that old server comes back up, and the EBCA is grabbed to another replica.  How does it handle the conflict. 

    I am curious if anyone else has additional issues.

  • 0   in reply to   
    Geoffrey Carman said:
      Not sure what happens if that old server comes back up, and the EBCA is grabbed to another replica.  How does it handle the conflict. 

    This is not a problem (this is how you can move EBACA to different server):

    See step 2 (Transfer EBA CA role to R/W replica) here: portal.microfocus.com/.../KM000031638

    Kind regards,

    Sebastijan

    Kind regards,

    Sebastijan

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

  • 0 in reply to   

    These servers are hosted across three different data centers (PDC, NDR, and FDR). Currently, we are using Server B (NDR) for the Identity Application, serving as the user store in Access Manager and Advanced Authentication. If we keep the master replica (Servers A) down for two days, will this cause any data loss or operational failures, considering this is a production environment?

  • 0   in reply to   

    I had understood that the seize_ebaca action was meant for when the old EBA CA is dead.  Not just to move it.  Does it know to disable the old one, on the previous server?

  • 0   in reply to   
    Geoffrey Carman said:
    Does it know to disable the old one, on the previous server?

    Old server is still EBA enabled, but not EBACA anymore.

    I found some screenshots from last time my colleague did that.

    This is "old" EBACA server:

    And this is "new" EBACA server:

    Kind regards,

    Sebastijan

    Kind regards,

    Sebastijan

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

  • 0 in reply to   

    This will work; we have already transferred the EBCA role from Server A (Master Replica) to Server B.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.