HP StoreAll OS v6.3.
© Copyright 2013 Hewlett-Packard Development Company, L.P. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Description These release notes describe StoreAll OS Software version 6.3.113. Customers running StoreAll OS Software 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.6.x, 5.5.x, or 5.4.x are eligible for the update. Refer to the administrator guide for your storage system for specific update requirements and procedures. Customers running StoreAll OS Software 5.3.2 or earlier versions should contact HP Support to determine compatibility before updating their software.
Other supported software Software Supported versions Linux StoreAll clients • Red Hat Enterprise Linux 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 6.1, 6.2, 6.4 (all 64 bit) • SUSE Linux Enterprise Server 11 (64 bit) • SUSE Linux Enterprise Server 10.3 (64 bit) • openSUSE 11.1 (64 bit) • CentOS 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 6.1, 6.2, 6.
Languages International English NOTE: The HP-SMB server supports the following languages for file and directory names: English (ASCII), Latin-1 (Danish, German, French, Spanish, Italian, and Portuguese), Russian, Greek, Japanese, Korean, and Chinese (Mandarin). This language support will be available for file share names in a future release. 6.3.2 release Enhancements The intent of the 6.3.2 release was to resolve key issues found in earlier releases.
• The ibrix_quotamonitor command now synchronizes with the host errors logged after an upgrade to 6.1.4. Previously, the error message, “Failed to sync with host ” displayed in the quotamonitor.err file even though the host was up and running and the quota usage reported was incorrect. • Performance of snapshot reclamation jobs has been increased, particularly for configurations with multiple snapshot directories (snaptrees).
reset the switch and retry the update. With this fix, the FMT performs the switch reset and retries the firmware update. If the reset fails, the following error message is displayed: 0x1072 Reset failed for SAS Switch located at interconnect bay: SAS_SWITCH_BAY_. Please reset the switch manually. When this occurs, you must reset the switch manually.
Fixes • 8 Firmware release version 1.42 provides the following enhancements: ◦ The timeout for READ CAPACITY commands was increased to 45 seconds. Previously, certain drive models would be identified as FAILED shortly after a replacement drive was inserted (if the response time exceeded 15 seconds). ◦ Fixed regressions introduced in firmware version 1.40 that caused the controller to occasionally hang during replacement drive insertion.
• Some SNMP managers, such as Netcool Omnibus Manager, received StoreAll SNMP traps with an incorrect Specific Trap type and mismatched variable bindings. The fix changes the SNMP Trap OID (OID of IBRIXGENERICEVENT) to “.1.3.6.1.4.1.18997.2.0.1” and adds “eventIndex” to the variable bindings. Additionally, this fix includes a change to the StoreAll MIB file, which requires the following configuration steps after installing the 6.3.1 patch: 1.
• The file name in the DCN response was changed to be the relative Windows file name (which is the Windows server behavior) instead of the absolute UNIX file name. • The HP-SMB share management utility called lwnet previously failed when run with the lwnet share --set-info option. This occurred only when a domain user was used in the command, and the node had been removed from the domain. • Wrapper scripts were modified to accept spaces in arguments.
The ibrix_collect command has also been expanded so that the field can create add-on scripts that capture custom StoreAll and operating system commands and logs. See the HP StoreAll Storage CLI Reference Guide for additional information. See “Fixes” (page 11) for a list of fixes in this release. Fixes • When using the –e “date/timestamp” option in the ibrix_reten_adm command, the command now correctly handles date strings that include spaces.
• After an upgrade, the following message no longer appears: The IbrixArchiving rpm is not installed. • Use of StoreAll Native clients for any SUSE or SLES kernel is now supported for file systems with Express Query enabled. • The MDImport tool can now import large files created by MDExport or ibrix_audit_reports.
server. If the NTP and AD servers are not in sync, this causes the cluster nodes to receive conflicting time updates, which can lead to errors such as file system creation failures. To avoid this issue, ensure the AD server and the NTP server are synchronized so they have the same time. Or, ensure that the AD server and the StoreAll cluster are configured to synchronize the time from the same NTP server.
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME ibrix_aj_ 4390 root 10r DIR 0,22 4096 6327363124890451971 /fs_bug/.audit The online upgrade will terminate any user access applications and continues. Do you wish to Continue with online upgrade? [Y/N]: Terminate the ibrix_aj_ command, which is mentioned in the output, by pressing Y to continue with the upgrade.
connect interconnect 3 NOTE: This pass through connection to the integrated I/O console is provided for convenience and does not supply additional access control. For security reasons, use the password features of the integrated switch. The following is an example of command’s output: Connecting to integrated switch 3 at 115200,N81...
file, and hardlinkA is updated, then the stat hardlinkA command produces the same (updated) size as the stat hardlinkB command, since the stat command shows metadata from the file system. In contrast, Express Query treats hard links to the same file as if they are separate files. As a result, only the hard link you modified has its metadata updated in Express Query. The Express Query metadata for all other hard links to the same file are not updated.
Management console • File system creation on the 9300 server fails from the Getting Started Wizard. No data loss or corruption occurs, and you can still create the file system using the Create Filesystem Wizard or its comparable CLI command (ibrix_fs -c -f...). • File system creation from the Management Console, not the CLI, might sometimes fail with the message Exporting filesystem (NFS) failed. The file system was created correctly and all the other steps in the process have completed.
3. • Wait for a few seconds to let the Store archive propagate through the cluster and then restart the active FM. The credentials management service (hpsp_credmgmt) will not allow adding a credential for a new MSA storage array after the credential database is created. The workaround is to install the credentials manually. To install the credentials manually: 1. Enter the hpsp_couplet_info -i command to get a list of UUID for attached MSA enclosures.
If you do not perform these steps, some Robocopy operations will fail. Specifically, copies of all read-only files and, in some cases, zero size files, will transition prematurely to a WORM state during the copy process and Robocopy will be unable to apply all of the source file's attributes to complete the copies. Detailed steps are: 1.
dialog box in Windows. However, in this case, the Windows client cannot interpret LOCAL. Instead, specify the machine name of the server. For example, to add LOCAL\user1 to an ACL on an SMB file shared out by serverX, specify serverX\user1 in the Add dialog box on the security tab.
• Do not use spaces in share names. The GUI cannot create a share if there is a space in the name. • SMB clients have a 45 second timeout on every SMB request they make. If a request's timer expires before a response comes, the client disconnects and terminates the SMB connection with this error message: The specified network name is no longer available. After this, the client must reconnect to the SMB server.
Before starting the replication, ensure that cross-protocol ACL synchronization is enabled on all source and target cluster nodes. • When remote replication is running, if the target file system is unexported, the replication of data will stop. To ensure that replication takes place, do not unexport a file system that is the target for a replication (for example, with ibrix_crr_export -U). • Remote replication will fail if the target file system is unmounted.
• The ibrix_reten_adm -e command fails for WORM files that are not retained. If a WORM file is not retained (either it has never been retained, or it was retained but its retention period has expired), use the touch command to set its last accessed time (atime) forward to the desired expiration time. The file will then be retained until that time. • PDF reports cannot be generated from the GUI when using Windows Internet Explorer 8.
Segment evacuation • The segment evacuator cannot evacuate segments in a READONLY, BROKEN or UNIVAILABLE state. The ibrix_collect command • If collection does not start after a node recovers from a system crash, check the /var/crash/ directory to determine whether the vmcore is complete. The command ibrix_collect does not process incomplete vmcores. Also check /usr/local/ibrix/log/ ibrixcollect/kdumpcollect.log for any errors.
SNMP • When the StoreAll SNMP agent is configured, do not restart snmpd. If the snmpd restart command is run on the active node, you will need to take one of these steps: ◦ If Phone Home was configured, reconfigure it. ◦ If Phone Home was not configured, reconfigure the StoreAll SNMP agent. HP Insight Remote Support • After HP Insight Remote Support is configured, do not restart snmpd. See “SNMP” (page 25) for more information.
ibrix_fsck command • The log files for user-initiated tasks (such as running ibrix_fsck and migrating or rebalancing segments) are not rotated automatically. To control the space used by these log files, you will need to maintain them manually. The log files are located in /usr/local/ibrix/log. • After running a tiering, rebalance or segment evacuation job, a phase 1 of the ibrix_fsck command might display a message regarding “bad replica” inodes.
2. 3. Run segment evacuation. See the HP StoreAll Administrator Guide for your platform for additional information. Reload the CommVault driver. Refer to the CommVault documentation for additional information. • HP recommends that you do not run rebalancer, segment evacuation and/or data tiering tasks with ibdirecheck. • Any object store user can get a container listing for any object store user on an object mode REST API share. Permission changes are not allowed on the account level directory.
3. Fail over a server (ibrix_server -f -h ) 4. Unmount the file system. Workaround: Restart the server with the issue before unmounting the file system. • If the ibrix_auth command fails after a QR restore of a server in a cluster with a message similar to: ibrix_auth -n IBRQA1.HP.COM -A administrator@ibrqa1.hp.com -P password -h hostnameX Iad error on host hostnameX failed command () status (1) output: (Joining to AD Domain:IBRQA1.HP.COM With Computer DNS Name: hostsnameX.
Documentation changes and additions Modifying the /etc/hosts file on every StoreAll node is no longer necessary The post upgrade steps in the 6.3 HP StoreAll Storage Administrator Guides (dated March 2013) recommend that you modify the /etc/hosts file on every StoreAll node. This step was necessary in an earlier release, but it is no longer necessary for 6.3. Revision of text for creating a retention/WORM/auto-commit feature set The 6.
and retention, there are other factors considered before autocommit or retention is applied, such as when the file is created (ctime) and when file content and metadata were last changed (mtime). ctime is used to determine when autocommit should be applied. Once a decision is made about autocommit, mtime is used to calculate the retention period.
(docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
