Upgrade Guide for InsightIQ 5.1.0’
Fri, 21 Jun 2024 15:41:08 -0000
|Read Time: 0 minutes
Upgrading your InsightIQ instance from your version to 5.1.0 is essential for leveraging new enhancements and critical updates. This blog post provides a detailed guide to ensure a smooth upgrade process.
Upgrade from IIQ 5.0.x to IIQ 5.1.0:
This upgrade process applies to both InsightIQ Simple and InsightIQ Scale configurations, does not impact the datastore or configuration settings. See more details in my previous blog: Understanding InsightIQ 5.0.0 Deployment Options: Simple vs. Scale | Dell Technologies Info Hub.
Before starting the upgrade, ensure the following prerequisites are met:
- You must accept the End User License Agreement (EULA) in the current version before initiating the upgrade.
- Ensure at least 40 GB of free space is available.
It is recommended to perform the upgrade when you are not logged into InsightIQ, because the system will experience downtime during the process.
Upgrade Steps
1. Download the Installation Package
Navigate to the Drivers & Downloads tab on the PowerScale InsightIQ page from the Dell Support site. The package to download is named iiq-installer-5.1.0.tar.gz, with a total size of 30 GB (15 GB for Kubernetes management components and 15 GB for InsightIQ components).
2. Start an SSH Session
InsightIQ Simple: Log in as the administrator user.
InsightIQ Scale: Log in to the primary VM as the root user.
3. Extract the Installation Package
Extract the files from the downloaded package using the following command:
tar zxvf iiq-installer-5.1.0.tar.gz
4. Navigate to the Upgrade Directory
cd InsightIQ/upgrade
5. Run the Upgrade Script
For InsightIQ Simple: Run the command: ./upgrade-iiq.sh
For InsightIQ Scale: Parameters are required. Use the --help parameter to view the command syntax and run the script accordingly.
6. Monitor the Upgrade Process
The upgrade process times are approximately 2 hours 15 minutes for InsightIQ Simple and 3 hours 15 minutes for InsightIQ Scale. The upgrade runs as a background process, so you can disconnect from the SSH session after starting it. However, please do not shut down the machine during the upgrade.
7. Verify Completion
Once the upgrade process is complete, verify the successful completion by looking for the following message:
Completed 100% of the upgrade
The upgrade process is designed to be robust, allowing for reattempts in case of temporary failures. If the upgrade script fails, you can rerun it, and it will resume from the point of failure.
Upgrade from IIQ 4.3.x and 4.4.x to IIQ 5.1.0:
There are two migration methods:
- Upgrade by Exporting and Importing the Datastore: This method only moves the datastore from the older instance into InsightIQ 5.1.0.
- Upgrade by Offline Migration: This method migrates the datastore along with additional configuration data from the older version to InsightIQ 5.1.0.
Upgrade by Exporting and Importing the Datastore Steps
Note: The export operation must be performed from InsightIQ versions 4.3, 4.4, or 4.4.1.
1. Export the Datastore:
Use the InsightIQ UI on the respective InsightIQ instances to export the datastore to a location that is not on the InsightIQ host system. Ensure the export is working properly by testing the import and checking for errors.
Export datastore from Manage Monitored Cluster section
2. Download and Install InsightIQ 5.1.0:
- Based on your business requirements, choose your preferred InsightIQ installation method and obtain the installation file (tar.gz for IIQ Scale or .ova for IIQ Simple).
- Download the file to an accessible location and install InsightIQ 5.1.0.
3. Import the Datastore:
Use the exported .zip file to import the datastore into the newly installed InsightIQ 5.1.0 instance.
Upgrade by Offline Migration Steps
Note: A running instance of InsightIQ 4.3.x or 4.4.x. is required. If you are running InsightIQ 4.2.x or earlier versions, you need to perform an upgrade to InsightIQ 4.3 or 4.4 before performing offline migration to InsightIQ 5.1.0.
1. Download and Install InsightIQ 5.1.0:
- Based on your business requirements, choose your preferred InsightIQ installation method and obtain the installation file (tar.gz for IIQ Scale or .ova for IIQ Simple).
- Download the file to an accessible location and install InsightIQ 5.1.0.
2. Locate and Copy Migration Scripts:
- Find the migration scripts from the InsightIQ 5.1.0 instance at: /usr/share/storagemonitoring/scripts/deploymentmanager.
- Copy iiq_migration_export.sh to the InsightIQ 4.x source instance.
3. Run the Export Script:
Execute the script on the InsightIQ 4.x source instance with root user or administrator:
sudo bash iiq_migration_export.sh <name and place of the exported archive file, e.g., '/mnt/export.tar.gz'>
This can take several hours based on the datastore size. The migration scripts generate a tar.gz file that contains the datastore and the configuration data. It is recommended that you mount a directory with free space that is at least twice the datastore size.
Note: During the migration process, InsightIQ is unable to collect data from monitored clusters.
4. Transfer the Export File:
Once the data export is complete, you can move the exported file to the InsightIQ 5.1.0 target instance via NFS share or direct copy.
5. Run the Import Script:
From InsightIQ 5.1.0, navigate to the directory containing the exported file, and from here, execute the import script:
- For InsightIQ Scale: as the root user on the primary VM, run: bash /usr/share/storagemonitoring/scripts/deploymentmanager/iiq_migration_import.sh <the exported archive file location>
- For InsightIQ Simple: as the administrator, run: /usr/share/storagemonitoring/scripts/deploymentmanager/iiq_migration_import_ova.sh <the exported archive file location>
6. Wait for the successful completion!
Upgrading InsightIQ to 5.1.0 ensures your system is up-to-date with the latest features and critical updates. By following the steps outlined in this guide, you can perform the upgrade smoothly and minimize downtime. Remember to always check for sufficient disk space and perform the upgrade during low usage periods to reduce the impact on users.
Author: Shaofei Liu