1 rolling upgrades – HP StorageWorks Scalable File Share User Manual
Page 33
IMPORTANT:
All existing file system data must be backed up before attempting an upgrade.
HP is not responsible for the loss of any file system data during an upgrade.
The safest and recommended method for performing an upgrade is to first unmount all clients,
then stop all file system servers before updating any software. Depending on the specific upgrade
instructions, you may need to save certain system configuration files for later restoration. After
the file system server software is upgraded and the configuration is restored, bring the file system
back up. At this point, the client system software can be upgraded if applicable, and the file
system can be remounted on the clients.
3.6.1 Rolling Upgrades
If you must keep the file system online for clients during an upgrade, a "rolling" upgrade
procedure is possible on an HP SFS G3 system with properly configured failover. As file system
servers are upgraded, the file system remains available to clients. However, client recovery delays
(typically around 5 minutes long) occur after each server configuration change or failover
operation. Additional risk is present with higher levels of client activity during the upgrade
procedure, and the procedure is not recommended when there is critical long running client
application activity underway.
Also, please note any rolling upgrade restrictions. Major system configuration changes, such as
changing system interconnect type, or changing system topology are not allowed during rolling
upgrades. For general rolling upgrade guidelines, see the Lustre 1.6 Operations Manual
section 13.2.2. For upgrade instructions
pertaining to the specific releases you are upgrading between, see the “Upgrading Lustre”
chapter.
IMPORTANT:
HP SFS G3.1-0 requires a valid license. For license installation instructions, see
Follow any additional instructions you may have received from HP SFS G3 support concerning
the upgrade you are performing.
In general, a rolling upgrade procedure is performed based on failover pairs of server nodes. A
rolling upgrade must start with the MGS/MDS failover pairs, followed by successive OST pairs.
For each failover pair, the procedure is:
1.
For the first member of the failover pair, stop the Heartbeat service to migrate the Lustre
file system components from this node to its failover pair node.
# chkconfig heartbeat off
# service heartbeat stop
At this point, the node is no longer serving the Lustre file system and can be upgraded. The
specific procedures will vary depending on the type of upgrade to be performed. Upgrades
can be as simple as updating a few RPMs, or as complex as a complete reinstallation of the
server node. The upgrade from HP SFS G3.0-0 to HP SFS G3.1-0 requires a complete
reinstallation of the server node.
2.
In the case of a complete server reinstallation, save any server specific configuration files
that will need to be restored or referenced later. Those files include, but are not limited to:
•
/etc/fstab
•
/etc/hosts
•
/root/.ssh
•
/etc/ha.d/ha.cf
•
/etc/ha.d/haresources
•
/etc/ha.d/authkeys
3.6 Upgrade Installation
33