Workflow: Installer Upgrade from Release 6.1.x to 7.0.0

This page summarizes the steps for upgrading from core 6.1.x to 7.0.0 by using the Installer.

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.

IMPORTANT Installer 1.18.0.5 supports core upgrades only from release 7.5.0 to 7.6.1. All EEP upgrades are supported. To upgrade core or EEP manually, see these topics:

Installer Upgrade Summary

In an upgrade using the Installer, the Installer shuts down core on the entire cluster, upgrades and configures core, starts core, upgrades EEP components, and then starts the EEP components. Like the offline manual upgrade, the Installer upgrade is an offline upgrade. The Installer upgrade requires you to:

Plan for the upgrade.
Update the Installer to version 1.17.0.3 or later.
Launch the Installer and select Version Upgrade.
Complete the upgrade through the Installer.
Manually merge custom configuration settings.
Perform post-upgrade checks.

The workflow later on this page provides more detail to help you get started with the Installer upgrade.

Considerations for Installer Upgrades

Before upgrading using the Installer, note these considerations:

Upgrades using the Installer are supported only from release 5.2.x with EEP 3.0.1 or later.
If security is enabled on the cluster – either data-fabric default security or custom security – you cannot upgrade from release 5.2.x using the Installer; you must use one of the manual upgrade workflows. Note that upgrades from secure release 6.0.0 or 6.0.1 clusters can be done using the Installer, as described in Planning Your Core Upgrade.
Security settings cannot be changed during a version upgrade using the Installer.
Before upgrading using the Installer, you must update the installer to version 1.17.0.3 or later.
This procedure assumes that the cluster was originally installed using the Installer or an Installer Stanza. If the cluster was installed manually, you must use the manual steps to upgrade or use probe and import to generate the installer database.
When upgrading to release 6.2 using the Installer, EEP 4.x or later is upgraded automatically to EEP 7.0.0.

Installer 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	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. Upgrade the Installer to Version 1.17.0.3 or later	Checking the Installer Version Updating the Installer Using the Installer
7. Upgrade the OS	When Upgrading Core with the Installer Requires an OS Upgrade
8. Select the Version Upgrade Option	Upgrading Core With the Installer
9. Complete the Upgrade Through the Installer	Online Help for Installer Fields
10. Perform Post-Upgrade Steps for Core	Considerations for Upgrades Using the Installer Step 2: Manually Update Configuration Files Step 3: Upgrade Clients
11. Perform Post-Upgrade Steps for EEP	Finishing the Ecosystem Pack Upgrade
12. Secure the Upgraded Cluster	Securing the Upgraded Cluster