6.3 HP StoreAll 9300/9320 Storage Administrator Guide (AW549-96072, June 2013)

Manual upgrade
Check the following:
• If the restore script fails, check /usr/local/ibrix/setup/logs/restore.log for
details.
• If configuration restore fails, look at /usr/local/ibrix/autocfg/logs/appliance.log
to determine which feature restore failed. Look at the specific feature log file under /usr/
local/ibrix/setup/logs/ for more detailed information.
To retry the copy of configuration, use the command appropriate for your server:
◦ A file serving node:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade -s
◦ An agile node (a file serving node hosting the agile management console):
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade -f -s
Upgrading the StoreAll software to the 5.5 release
This section describes how to upgrade to the StoreAll software 5.5 release. The management
console and all file serving nodes must be upgraded to the new release at the same time.
IMPORTANT:
• Do not start new remote replication jobs while a cluster upgrade is in progress. If replication
jobs were running before the upgrade started, the jobs will continue to run without problems
after the upgrade completes.
• If you are upgrading from a StoreAll 5.x release, ensure that the NFS exports option
subtree_check is the default export option for every NFS export. See “Common issue
across all upgrades from StoreAll 5.x” (page 154) for more information.
NOTE: If you are upgrading from a StoreAll 5.x release, any support tickets collected with the
ibrix_supportticket command will be deleted during the upgrade. Download a copy of the
archive files (.tgz) from the /admin/platform/diag/supporttickets directory.
Upgrades can be run either online or offline:
• Online upgrades. This procedure upgrades the software while file systems remain mounted.
Before upgrading a file serving node, you will need to fail the node over to its backup node,
allowing file system access to continue. This procedure cannot be used for major upgrades,
but is appropriate for minor and maintenance upgrades.
• Offline upgrades. This procedure requires that file systems be unmounted on the node and
that services be stopped. (Each file serving node may need to be rebooted if NFS or SMB
causes the unmount operation to fail.) You can then perform the upgrade. Clients experience
a short interruption to file system access while each file serving node is upgraded.
You can use an automatic or a manual procedure to perform an offline upgrade. Online upgrades
must be performed manually.
Automatic upgrades
The automated upgrade procedure is run as an offline upgrade. When each file serving node is
upgraded, all file systems are unmounted from the node and services are stopped. Clients will
experience a short interruption to file system access while the node is upgraded.
All file serving nodes and management consoles must be up when you perform the upgrade. If a
node or management console is not up, the upgrade script will fail and you will need to use a
manual upgrade procedure instead. To determine the status of your cluster nodes, check the
dashboard on the GUI.
To upgrade all nodes in the cluster automatically, complete the following steps:
Upgrading the StoreAll software to the 5.5 release 167