HP 3PAR Upgrade Pre-Planning Guide

NOTE:
◦ See HP SPOCK streams, on the HP SPOCK website, for supported multipathing
environments.
◦ For unsupported environments, the hosts should be shut down and in some cases powered
off. The VLUNs exported to such hosts must be unexported or connections must be logically
disconnected before the online HP 3PAR OS upgrade.
• A host definition must not contain initiators from multiple hosts. For example, host cluster
configurations must use a separate host definition for each host in the host cluster.
• Stop all system administration activities during an HP 3PAR OS online upgrade. Complete or
stop all active tasks before proceeding. This includes any provisioning activity, physical copy
activity, virtual copy activity, and dynamic optimization. Stop any automated administration
scripts such as Recovery Manager and VSS Provider for Microsoft Windows.
• iSCSI hosts must have active I/O on all paths during the upgrade. The upgrade process reboots
nodes and checks that all hosts are reconnected after each node reboots. The upgrade will
not advance until all hosts re-establish connection. An idle iSCSI host will not reconnect, it is
important to have I/O on all paths during the upgrade.
• The recovery manager for Oracle, SQL, Exchange or VMware may require a newer version
to be compatible to HP 3PAR OS 3.1.1 or later. See the interoperability information on the
HP SPOCK website for HP 3PAR OS 3.1.x for supported levels.
• An upgraded CLI client for HP 3PAR OS 3.1.1 MU1 or later must be installed on the recovery
manager host. See the HP SPOCK website for information about HP 3PAR OS 3.1.x for
supported levels and host compatibility.
• Verify compatibility of any host third-party software to the HP 3PAR OS release 3.1.x.
• The HP 3PAR System Reporter requires an upgrade to be compatible with HP 3PAR OS 3.1.x.
When you upgrade the HP 3PAR StoreServ Storage to HP 3PAR OS 3.1.x, upgrade the HP
3PAR System Reporter application compatible with 3.1.x as mentioned in HP SPOCK with
the bundled HP 3PAR System Reporter CLI Remote Client.
• The HP 3PAR Management Console is generally compatible with all HP 3PAR OS 2.3.1,
3.1.1, 3.1.2, and 3.1.3 MU1 versions. For the latest features and fixes, it is advisable to
upgrade to the current HP 3PAR Management Console release.
• For hosts running HP 3PAR Cluster Extension (CLX) software upgrading to HP 3PAR OS 3.1.1,
the HP 3PAR OS 2.3.1 CLI must be run on all nodes in the HP 3PAR CLX. Do not upgrade the
CLI on those nodes to 3.1.1 CLI. However, if you upgrade to HP 3PAR OS 3.1.1 MU1, you
can upgrade the nodes to 3.1.1 MU1 CLI.
For hosts running HP 3PAR CLX upgrading to HP 3PAR OS 3.1.1 MU1, upgrade the host CLI
to the HP 3PAR OS 3.1.1 MU1 CLI before the HP 3PAR StoreServ Storage is upgraded to HP
3PAR OS 3.1.1 MU1.
CAUTION: When upgrading to HP 3PAR OS 3.1.1 MU1, you must upgrade the HP 3PAR
OS CLI to HP 3PAR OS 3.1.1 MU1 on any node attached to the array. Otherwise, HP 3PAR
CLX fails to perform failover/failback operations on HP 3PAR Remote Copy volume groups
or other applications.
For an upgrade to HP 3PAR OS 3.1.3, host-based applications must be upgraded to the latest
version in the order specified by the HP 3PAR OS upgrade instructions.
8 Guidelines for Online Upgrades