Matthew,

While I have no experience of a LEAPP upgrade there are some pointers:

• UniVerse maintains a number of hidden root-level files that point to UniVerse resources. Some are text files containing a path and some are symbolic links. I recommend checking these before the upgrade and re-checking them after the upgrade as they may require reinstatement.
• The UniVerse product license will almost certainly become unauthorised and require re-authorisation - see the command uvregen (you will  need root or sudo access).
• If you use SSL certificates, check they are still valid on the new system - you might need to recreate them (unlikely, but possible and the cost of checking is trivial).
• Check the Unix kernel configuration in case any custom modifications revert during the LEAPP upgrade and need adjustment

NOTE: I have not considered UniVerse Replication (whether 2-way or n-way) or RFS as there other considerations, I recommend opening a Support case for specifics if these features are used.

.

The worst-case scenario I can anticipate is that you may need to reload/upgrade UniVerse in-place and as a matter of course I recommend a backup of the 'UV' home account and it's children beforehand. This will secure any local customisation and can be restored if needed without manual editing of configurations.

I'd recommend a dry-run on a test system - and you should be abke to obtain a short-term Evaluation license from either Rocket or your UniVerse supplier for test purposes.

I recommend checking the O.S Vendor's binary compatibility statement for versions 8 and 8.6  - usually it's fine for ANY 8.x version but the O.S vendor is the touchstone for binary compatibility.

Please post any feedback on the LEAPP upgrade results for others in the community once done.

Regards

JJ