Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    11
  • Subscribers subscribers
    7
  • Views views
    1477
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

upgrade Vibe server to OES2018

valveamp300b

We have Vibe 4.0.4 on OES2015 sp1 / SLES11 sp4 on VMware

We would like to upgrade the OS to OES2108sp2, what is best practice for Vibe?

In place upgrade? Migration server? or new server and backup/restore Vibe?

How do we deal with the change in database?

MySQL 5.5.62 on SLES 11 sp4 to MariaDB 10.2 on SLES 12 sp5

Many thanks

 

Tags:

Parents
  • 0
    Why OS2018-Server?
    SLES12SP5 or SLES15 are perfect Plattform for Vibe.
    I have reinstall Vibe4.07p1 on a SLES12SP5 with included Mariadb (same as mysql) without Problem, following the install doc.
    But for users/group you must connect a oes2018 Server with edir!
    It is your choice what platform and database you use!
  • 0 in reply to 

    why OES? so we have a copy of the tree on the other OES server, otherwise no reason

     

  • 0 in reply to 
    You must have an oes2018 with edir and another for the replica edir, that is a good way.
    But for Vibe4.07p1 as SLES-Server will be the best choice, that my experience and my meaning.
    But, you can do what you prefer, my mind is only my recommandation. Take a good choice, a virtual machine is quickly prepared and installed to test this.
  • 0   in reply to 

    However it's not a problem to run Vibe on OES. How do you plan your OES upgrade? In-place?

    If in-place then do a Vibe in-place upgrade too. It does not hurt. It is even easier now because Vibe comes with its own Java.

    Even if database changes from MySQL to MariaDB will not hurt. Vibe will continue without any problems.

    I.e. I use a test environment for years now. I started with old Vibe versions 3.x and old OES versions. I upgraded over the years and I am on OES2018Sp1 now; Vibe on version 4.0.7 P1 ..

    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to   

    I was hoping that an in place upgrade would work.

    This server started as Teaming v2 starter pack way back when. Possibly a clean system and data migration would be a good idea, however when I have attempted this in the past it has not been successful.

    Now I know that in place has a good chance of success I will give that a try.

    Many thanks

Reply
  • 0 in reply to   

    I was hoping that an in place upgrade would work.

    This server started as Teaming v2 starter pack way back when. Possibly a clean system and data migration would be a good idea, however when I have attempted this in the past it has not been successful.

    Now I know that in place has a good chance of success I will give that a try.

    Many thanks

Children
  • 0   in reply to 

    I moved many Vibe installations from server to server - because of operation systems, because of lack of space or any other reasons. Many parts are really easy to migrate i.e. copying the data directories or dumping and restoring sql data. In some cases the encryption key(s) can be tricky

    Use "Verified Answers" if your problem/issue has been solved!

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.