Workflow: Manual Rolling Upgrade from Release 6.x to 7.0.0

This page summarizes the steps for upgrading from release 6.1.x or 6.2.0 to release 7.0.0 by using a manual rolling upgrade. In this workflow, the cluster to be upgraded is secure; after the upgrade, the cluster will continue to be secure.

NOTE This workflow assumes that the cluster to be upgraded is running release 6.1.x or release 6.2.0 with one of the following ecosystem packs and Linux operating systems:
Data-Fabric Release Ecosystem Pack Linux Operating System (one of the following)
6.2.0 EEP 7.1.2 or 8.1.0
  • RHEL 8.1, 8.2, 8.3, or 8.4*
  • Ubuntu 18.04 or 20.04
  • SLES 15 SP2 or SP3
  • Oracle Enterprise Linux 8.2, 8.3, or 8.4
6.1.x EEP 6.3.x
  • RHEL 8.2 or 8.3*
  • Ubuntu 16.04 or 18.04
*Note that release 7.0.0 is supported on RHEL but not on CentOS.

Manual Rolling Upgrade Summary

In a manual rolling upgrade, you upgrade the software one node at a time so that the cluster as a whole remains operational throughout the process. The manual rolling upgrade requires you to:
  1. Perform pre-upgrade checks.
  2. Perform a rolling upgrade of core.
  3. Verify that all use cases are functional on the cluster.
  4. Upgrade the EEP to 8.x.
  5. Merge custom configuration settings.
  6. Enable release 7.0.0 features.
  7. Perform post-upgrade checks.

The workflow later in this section provides more detail to help you get started with a manual rolling upgrade.

Considerations for Manual Rolling Upgrades

Before performing a manual rolling upgrade, note these considerations:
  • Rolling upgrades only upgrade core packages, not ecosystem components. A rolling upgrade of ecosystem components is not supported.
  • If you choose to do a rolling upgrade on a cluster with core and ecosystem components, the ecosystem components will continue to work during the rolling upgrade as long as the ecosystem components are not updated. If you choose to upgrade core and ecosystem components together, the ecosystem components might not function properly during the upgrade process.
  • After upgrading core to release 7.0.0, you must upgrade ecosystem components to EEP 8.1.0 or later, and this must be done before you enable release 7.0.0 features.

Manual Rolling Upgrade Workflow

High-Level Steps Detailed Information (review all items unless noted otherwise)
1. Understand Core/MEP Dependencies

Down arrow

2. Plan for the Core Upgrade

Down arrow

3. Plan for the EEP Upgrade

Down arrow

4. Perform Pre-Upgrade Steps for Core

Down arrow

5. Prepare to Upgrade EEP Components

Down arrow

6. Set up Repositories

Down arrow

7. Perform the Manual Rolling Upgrade

Down arrow

8. Upgrade the EEP Components

Down arrow

9. Perform Post-Upgrade Steps for EEP

Down arrow

10. Perform Post-Upgrade Steps for Core

Down arrow

11. Install Additional Core Features

Down arrow

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.
12. Secure the Upgraded Cluster