Workflow: Offline Manual Upgrade from Release 6.1.x to 7.0.0

This page summarizes the steps for upgrading from release 6.1.x or 6.2.0 to 7.0.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.

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.

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 7.0.0.
Upgrade the EEP to 7.1.2 or 8.1.0.
Merge custom configuration settings.
Start the cluster and perform post-upgrade checks.
Enable core 7.0.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.0.0, you must upgrade ecosystem components to an EEP that is compatible with 7.0.0. This must be done before you enable release 7.0.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	Operating System Support Matrix EEP Support and Lifecycle Status Component Versions for Released EEPs
2. Plan for the Core Upgrade	Upgrading and Your License Installation Notes (Release 7.0.0) Upgrade Notes (Release 7.0.0) Planning Your Core Upgrade
3. Plan for the EEP Upgrade	Planning Ecosystem Pack (EEP) Upgrades
4. Perform Pre-Upgrade Steps for Core	Preparing to Upgrade Core
5. Prepare to Upgrade EEP Components	Preparing to Upgrade the Ecosystem Pack
6. Set up Repositories	Setting Up Repositories
7. Perform the Offline Manual Upgrade	Offline and Manual Upgrade Procedure
8. Upgrade the EEP Components	Upgrading the Ecosystem Pack Without the Installer
9. Perform Post-Upgrade Steps for EEP	Finishing the Ecosystem Pack Upgrade
10. Perform Post-Upgrade Steps for Core	Restart and Check Cluster Services Manually Update Configuration Files Upgrade Clients Enable New Features
11. Install Additional Core Features	Installing 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.
12. Secure the Upgraded Cluster	Securing the Upgraded Cluster