|
|
InfoScale Foundation |
InfoScale Availability |
InfoScale Storage |
InfoScale Enterprise |
|
Back up configuration and application data
|
✓ |
✓ |
✓ |
✓ |
|
Review licensing details
|
✓ |
✓ |
✓ |
✓ |
|
Review the installation requirements and perform the required pre-installation tasks
|
✓ |
✓ |
✓ |
✓ |
|
Ensure there are no parallel scheduled snapshots in progress
|
✓ |
✓ |
✓ |
✓ |
|
For Windows Server 2008 R2 systems, Microsoft update KB3033929 or its superseding update, if any, is installed. This update is required to support SHA-2 code-based kernel drivers.
|
✓ |
✓ |
✓ |
✓ |
|
Verify that the systems in your environment meet the requirements to upgrade the cluster. Run the Windows Data Collector that is available on the SORT website to perform these checks.
|
✓ |
✓ |
✓ |
✓ |
|
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:
From the Java Console, click on the Cluster
Explorer toolbar. -
From the command prompt, type the following command:
C:\>haconf -dump -makero
|
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 %VCS_home% folder are removed. As a result, all the binaries of all the enterprise agents and custom agents that were
installed are removed. After the upgrade is complete, all the binaries of enterprise agents are
installed again. However, the binaries of a custom agent are not installed again.
The main.cf that is restored after the upgrade shows that the custom agent resources
are configured. However, the binaries are not present in the %VCS_home% folder.
You must manually install the custom agents after the upgrade is complete.
|
X |
✓ |
X |
✓ |
|
To perform parallel upgrade, take the service groups offline
To take the service groups offline
-
From the command prompt, type:
C:\>hagrp -offline group_name -sys system_name
Where 'group_name' is the name of the service group and system_name is the
node on which the group is online.
Repeat this command for all service groups that are online. |
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.
Cluster Manager (Java Console) Solutions Configuration Center (SCC) Veritas Enterprise Administrator (VEA) |
✓ |
✓ |
✓ |
✓ |
|
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
From the VEA Control Panel perspective, select the action agent node in the
tree view and double-click in the right pane. In the Rule Manager window, select the rules you want to export and then click . Save the rules at any temporary location in the XML format. |
✓ |
X |
✓ |
✓ |
|
Stop the Veritas High
Availability Engine (HAD) on all the cluster nodes
This task is applicable only if Veritas InfoScale Storage and InfoScale Availability co-exists in your environment.
If you plan to upgrade Veritas 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 of the cluster node:
hastop -all -force
|
X |
X |
✓ |
X |
