InfoScale™ 9.0 Installation and Upgrade Guide - Windows
- Preinstallation and planning
- About InfoScale licenses
- Installing the Arctera InfoScale products
- Upgrading the InfoScale products
- Performing the post upgrade tasks
- Administering the InfoScale product installation
- Uninstalling the InfoScale products
- Performing application upgrades in an InfoScale environment
- Upgrading Microsoft SQL Server
- Upgrading Oracle
- Upgrading application service packs in an InfoScale environment
- Appendix A. Services and ports
- Appendix B. Migrating from a third-party multi-pathing solution to DMP
General preparations
Perform the following general pre-upgrade checks or tasks on all the systems:
The following table lists the general pre-upgrade checks.
Table: General pre-upgrade checks
Tasks | Applicable for | |||
---|---|---|---|---|
InfoScale Foundation | InfoScale Availability | InfoScale Storage | InfoScale Enterprise | |
Back up configuration and application data | ✓ | ✓ | ✓ | ✓ |
Review licensing details and back up the older license key | ✓ | ✓ | ✓ | ✓ |
Review the installation requirements and perform the required pre-installation tasks | ✓ | ✓ | ✓ | ✓ |
Ensure there are no parallel scheduled snapshots in progress | ✓ | ✓ | ✓ | ✓ |
Ensure that the latest Microsoft Windows updates are installed on the systems. The latest updates are required for successfully installing Microsoft Visual C++ 2015 Redistributable-x64. The product installation fails if Microsoft Visual C++ 2015 Redistributable-x64 is not installed. | ✓ | X | ✓ | ✓ |
Ensure that there are no parallel installations, live updates, or Microsoft Windows updates in progress | ✓ | ✓ | ✓ | ✓ |
If the systems have NetBackup version 6.0 or 6.5 installed and running, then shut down the OpsCenterServer service. Both, NetBackup and InfoScale products share the same AT broker and client. | ✓ | ✓ | ✓ | ✓ |
Save and close the cluster configuration. This operation saves the latest configuration to disk and changes the configuration state to read-only mode To save the cluster configuration, perform one of the following tasks: | X | ✓ | X | ✓ |
Take the backup of custom agent binaries During the product upgrade, a backup of the main.cf and other configuration files is taken. However, it does not take the backup of any agent binaries. During the upgrade, the contents of | X | ✓ | X | ✓ |
To perform parallel upgrade, take the service groups offline To take the service groups offline
| X | ✓ | X | ✓ |
Close client applications If you are running any of the following client applications on the systems where you plan to upgrade the product, stop and exit all the application instances.
| ✓ | ✓ | ✓ | ✓ |
Export the configured rules If you have configured any rules for event notification messages and actions, you must export them into XML format before you begin with the upgrade. To export the configured rules
| ✓ | X | ✓ | ✓ |
Stop the High Availability Engine (HAD) on all the cluster nodes This task is applicable only if Arctera InfoScale Storage and InfoScale Availability co-exists in your environment. If you plan to upgrade Arctera InfoScale Storage in a co-existing environment, you must forcefully stop HAD before you begin the upgrade. To forcefully stop HAD, run the following command from any cluster node: hastop -all -force | X | X | ✓ | X |
Note:
You can configure Arctera Telemetry Collector if you are upgrade an InfoScale product to version 9.0 by using the CLI. The configuration of Arctera Telemetry Collector is not supported via the installation wizard. However, it can be configured manually by using Arctera Telemetry Collector commands after an InfoScale product is installed or upgraded.