HP StorageWorks Clustered Gateway (software-only) 3.6.0 Windows Storage Server Edition Upgrade Guide (433702-002, January 2008)

Chapter 4: Non-Rolling Upgrades 17
If you perform a custom installation of HP Clustered File System 3.6.0
and specify a new location for the cluster software, the Installer will not
be able to locate the existing configuration files. To avoid this problem,
take one of these steps:
• If HP Clustered File System is currently installed in a custom location,
install HP Clustered File System 3.6.0 in the same location.
• If you need to install the 3.6.0 release in a different location, copy the
backup configuration files (see “Back Up the Existing Cluster” on
page 5) to that location before installing HP Clustered File System
3.6.0.
Upgrade Considerations
When upgrading HP Clustered File System, you should be aware of the
following:
• The server with the numerically highest primary IP address must be
upgraded first. Then continue to upgrade the servers in descending
order of IP address, with the server with the lowest primary IP
address being upgraded last.
• It is important to upgrade all nodes in the cluster within a short time
frame. We do not recommend running the cluster for an extended
period of time with only some of the nodes upgraded to 3.6.0. This
release introduces a new configuration data repository and a new
logging facility that do not become fully functional until all nodes are
upgraded. If the cluster is only partially upgraded, alerts raised by
nodes running 3.6 will be improperly logged by nodes running 3.4.
Also, until the entire cluster is upgraded, many services that are run
on 3.6 nodes must be run as local system administrator.
• If a server is temporarily out of the cluster during the upgrade (for
example, for maintenance), you will need to upgrade it to 3.6.0 before
returning it to the cluster.
• The stand-alone HP CFS Management Console, which is used to
connect to the cluster from hosts not running the cluster software,
must be upgraded to the 3.6.0 version.