Upgrade non-HA Linux MDCs

Pre-Upgrade Steps

Quantum recommends that you run and complete a StorNext backup prior to starting the upgrade. If you have not completed a backup, you can initiate one from the StorNext GUI (see System Backup).
Make sure all store and retrieve requests have finished.
If you are using DDM, disable it on all the hosts by using the StorNext GUI or the fsddmconfig command. Storage Manager requires that the MDC and DDM clients are running the same version of the software. Refer to the section on Distributed Data Mover in the StorNext User’s Guide for information on DDM.

Upgrade the MDC

Mount the StorNext installation DVD and change to the DVD root directory.

Note: When you mount a DVD in a Red Hat system, DVDs are mounted by default with a noexec (non-executable) option which prevents you from proceeding with the installation. For complete details on the supported versions of Red Hat, see the StorNext 6 Compatibility Guide.

For Red Hat users only, before proceeding you must remount the DVD by typing mount -o remount, exec ....
List the installation directories on the DVD. At the command prompt, type:

ls -l
Change to the stornext_full directory.

Note: Make sure you are in the stornext_full directory and not the fs_only directory. The fs_only directory installs the StorNext File System only.
List the directories in the stornext_full directory. At the command prompt, type:

ls -l
Identify the correct installation directory for your operating system and hardware platform, and then change to that directory. For example, for Red Hat Linux 7 running on an x86 64-bit platform, change to the RedHat7_x86_64 directory.
As described in Get Ready To Upgrade, license checks are made as part of the upgrade. Some of these checks require the software to be running, so start it now. At the command prompt, type:

service cvfs start
Run the script with the -liccheck option. At the command prompt, type:

./install.stornext -liccheck

The install script runs and checks for valid licenses. If the license check fails, then contact Quantum before continuing with the upgrade. For sample output, see The License Check Option.

Run the install script. At the command prompt, type:

./install.stornext

The installation script runs, as illustrated below.

     Stornext Upgrade 6.2.0(79220E) MAIN MENU

      1)  Installation Configuration
      2)  Upgrade stornext
      3)  Show Status
      4)  Quit

Enter your choice <2>:

On the Upgrade Menu, type 2 and press <Enter>. The StorNext installation script runs and displays the current progress of the upgrade.
When the upgrade is complete, press <Enter> to return to the Main Menu.

Note: A database schema update is applied to Storage Manager when upgrading from StorNext 4.3.x to StorNext 5. This update takes approximately one hour for every hundred million entries in the filecomp tables.

In a non-HA environment, database schema updates will be applied during the first start of StorNext from install.stornext following the upgrade to the new version of the StorNext software StorNext file systems are accessible while the database schema is being updated, but Storage Manager functionality (including stores and retrieves) will be offline.

Do NOT interrupt StorNext services while the database is being updated. Interrupting the database schema update could result in an inconsistent database, and may require assistance from Quantum Support to repair or restore the database.
To exit the installation script, type 4 and press <Enter>.
After running the installer, source the profile on the MDC by running this command:

. /usr/adic/.profile

Post-Upgrade Steps

If you are using the DDM feature, follow these steps:

Upgrade the DDM hosts to same version of StorNext as the MDC.
Enable the DDM host by executing the fsddmconfig command or the StorNext GUI.

The License Check Option

When you run the installation script with the -liccheck option, the script checks for valid licenses. Proceed with the upgrade only if the license check is successful.

Note: Even if the license check is successful, messages about unlicensed features may display. However, if these features are not in use, you may proceed with the upgrade.

The license check can fail for the following reasons:

StorNext or StorNext components are not running, which keeps the licensing status from being determined for a feature. Therefore it is treated as non-licensed even if the license is present.
The capacity has been reached for a licensed feature so it is treated as non-licensed.
A feature is found to be in use but not licensed.
The maintenance license expired prior to the build date of the upgrade release.

See the sections below for sample output for a successful and a failed license check.

SSL Certificate Exception

When you log into StorNext for the first time, you might see a message warning you about a security certificate. Refer to the Quantum Knowledge Base and search for “SSL” for a permanent workaround to this issue.

For a temporary solution, create a certificate exception that will allow you to log into the StorNext GUI without seeing the warning message during subsequent logins.