• State Not Answered
  • Replies replies
    15
  • Subscribers subscribers
    20
  • Views views
    735
  • Users 0 members are here

eDirectory 9.2.8 SLES 12 sp5 to SLES 15 sp6 in-place upgrade

a2822au

Does anyone have experience with an in-place upgrade eDirectory from SLES12 SP5 to SLES15 SP6?

We have VM servers, 3 in each of 4 trees, in production and also in the test environment.

We are using eDirectory 9.2.8 as LDAP server and IDM 4.8.7.

One eDirectory server is running on SLES15 SP6 with a fresh install. It works perfectly.

I want to avoid installing new VMs, it would be about 20 servers.

I have not found any references to recommendations and no-goes. Every information is helpful

Thank you very much,
Ute E.

Parents
  • 0  

    Hi, a2828au

    It is possible to run more than one eDir instance on a SLES system. If I run into such a situation in the field, I move the DIB with everything that goes with it to a system on which an eDir is already running. Of course there is more to do than just moving the DIB from a to b. Secondary IP, additional names to the corresponding IP etc. I think anyone who runs eDir on SLES knows what is meant here.

    After the eDir has been moved, I stop the corresponding services and prevent the services from starting after a restart. Because the NDS of the system in question is running on another server, the NDS is OK. Now either in-place upgrade or another method can be selected. The way backwards of the DIB is basically a disaster recovery process from a system that had a crashed NDS. The procedure even works for master and for BaumCA carriers. There are many other ways that are elegant, here is a first approach for further procedures,
    George

    “You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei

Reply
  • 0  

    Hi, a2828au

    It is possible to run more than one eDir instance on a SLES system. If I run into such a situation in the field, I move the DIB with everything that goes with it to a system on which an eDir is already running. Of course there is more to do than just moving the DIB from a to b. Secondary IP, additional names to the corresponding IP etc. I think anyone who runs eDir on SLES knows what is meant here.

    After the eDir has been moved, I stop the corresponding services and prevent the services from starting after a restart. Because the NDS of the system in question is running on another server, the NDS is OK. Now either in-place upgrade or another method can be selected. The way backwards of the DIB is basically a disaster recovery process from a system that had a crashed NDS. The procedure even works for master and for BaumCA carriers. There are many other ways that are elegant, here is a first approach for further procedures,
    George

    “You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei

Children
No Data

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.