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

5. Wait for the resynchronizer to complete by entering the following command until its output is
<FSNAME>: OK:
ibrix_archiving -l
6. Restore your audit log data by entering the following command:
MDImport -f <FSNAME> -n /tmp/auditData.csv -t audit
In this instance <FSNAME> is the file system.
7. Restore your custom metadata by entering the following command:
MDImport -f <FSNAME> -n /tmp/custAttributes.csv -t custom
In this instance <FSNAME> is the file system.
Troubleshooting upgrade issues
If the upgrade does not complete successfully, check the following items. For additional assistance,
contact HP Support.
Automatic upgrade
Check the following:
If the initial execution of /usr/local/ibrix/setup/upgrade fails, check
/usr/local/ibrix/setup/upgrade.log for errors. It is imperative that all servers are
up and running the StoreAll software before you execute the upgrade script.
If the install of the new OS fails, power cycle the node. Try rebooting. If the install does not
begin after the reboot, power cycle the machine and select the upgrade line from the grub
boot menu.
After the upgrade, check /usr/local/ibrix/setup/logs/postupgrade.log for errors
or warnings.
If configuration restore fails on any node, look at
/usr/local/ibrix/autocfg/logs/appliance.log on that node 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 following command:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade -f -s
If the install of the new image succeeds, but the configuration restore fails and you need to
revert the server to the previous install, run the following command and then reboot the machine.
This step causes the server to boot from the old version (the alternate partition).
/usr/local/ibrix/setup/boot_info -r
If the public network interface is down and inaccessible for any node, power cycle that node.
NOTE: Each node stores its ibrixupgrade.log file in /tmp.
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 following command:
20 Upgrading the StoreAll software to the 6.3 release