HP StoreAll OS 6.5.1 Upgrade Guide

Express Query will begin resynchronizing (repopulating) a new database for this file system.
6. Re-enable auditing if you had it running before (the default).
ibrix_fs -A -f <FSNAME> -oa audit_mode=on
In this instance <FSNAME> is the file system.
7. Restore your audit log data:
MDImport -f <FSNAME> -n /tmp/auditData.csv -t audit
In this instance <FSNAME> is the file system.
8. Restore your custom metadata:
MDImport -f <FSNAME> -n /tmp/custAttributes.csv -t custom
In this instance <FSNAME> is the file system.
For more information about troubleshooting an MIF, see “Troubleshooting an Express Query Manual
Intervention Failure (MIF)” in the Administrator Guide for your platform.
Issues with cascading upgrades
NOTE: The following issues apply to an upgrade to any version (5.5, 5.6, or 6.1.5) unless
otherwise noted.
Automatic upgrade
Check the following:
• After upgrading from StoreAll version 5.5 and running the restore script, the /etc/multipath
file might contain "hp_scsi_id". As a result, the device mapper will not work. To resolve
this issue, change "hp_scsi_id" to "scsi_id" by entering the following command:
sed -i -e 's/hp_scsi_id/scsi_id/g' /etc/multipath.conf
• 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.
46 Troubleshooting upgrade issues