Workflow: Offline Manual Upgrade from Release 6.x or 7.x to 7.9.0
This page summarizes the steps for upgrading from release 6.1.x or 6.2.0 or 7.x to 7.9.0 by using the offline manual upgrade. In this workflow, the cluster to be upgraded is secure; after the upgrade, the cluster will continue to be secure.
Offline Manual Upgrade Summary
In an offline manual upgrade, cluster processes and the jobs that depend on them are
stopped on all nodes so that packages can be updated. The offline upgrade process is simpler
than a rolling upgrade, and usually completes faster. The offline manual upgrade requires
you to:
- Perform pre-upgrade checks.
- Shut down the cluster.
- Upgrade core to release 7.9.0.
- Upgrade the EEP to 9.3.1.
- Merge custom configuration settings.
- Start the cluster and perform post-upgrade checks.
- Enable core 7.9.0 features.
The workflow later on this page provides more detail to help you get started with an offline manual upgrade.
Considerations for Offline Manual Upgrades
Before performing an offline manual upgrade, note the following considerations:
NOTE
After
upgrading core to release 7.9.0,
you must upgrade ecosystem components to an EEP
that is compatible with 7.9.0.
This must be done before you enable 7.9.0
features. To determine the compatible EEPs, see
EEP Support and Lifecycle Status. - The offline upgrade procedure requires an outage of the entire cluster. During the
maintenance window, the administrator:
- Stops all jobs on the cluster.
- Stops all cluster services.
- Upgrades packages on all nodes (which can be done in parallel).
- Brings the cluster back online at once.
Offline Manual Upgrade Workflow
High-Level Steps | Detailed Information (review all items unless noted otherwise) |
---|---|
1. Understand Core/EEP Dependencies | |
2. Plan for the Core Upgrade | |
3. Plan for the EEP Upgrade | |
4. Perform Pre-Upgrade Steps for Core | |
5. Prepare to Upgrade EEP Components | |
6. Set up Repositories | |
7. Perform the Offline Manual Upgrade | |
8. Upgrade the EEP Components | |
9. Perform Post-Upgrade Steps for EEP | |
10. Perform Post-Upgrade Steps for Core | |
11. Install Additional Core Features |
NOTE This page includes the steps to generate Object Store certificates by using
manageSSLKeys.sh . The certificates must be generated after
upgrading and running configure.sh -R . If you fail to generate
the certificates, you will not be able to use the Object Store. |