6.2.2 HP IBRIX 9000 Storage Release Notes (AW549-96061, January 2013)

Antivirus support
• If McAfee is used as a virus scan engine, when virus definitions are updated on the virus scan
engine, the updated definitions are not sent automatically to the IBRIX servers. To correct this
condition, request hotfix HF692368 from McAfee.
• For performance reasons, when an NDMP backup is in progress, Antivirus scans are not triggered
for the files being backed up. The IBRIX server excludes the process corresponding to NDMP from
scanning any files on a cluster with Antivirus enabled.
HP recommends that you disable Antivirus on the file system when a non-NDMP backup is in
progress. IBRIX cannot exclude a non-NDMP backup process from scanning files during a backup.
Disabling Antivirus prevents scans for files being backed up, which improves backup performance.
• When WebDAV is enabled, the internal WebDAV files in the root of the file system are scanned.
To exclude all .lock/.pag files in the .DAV and .webdav directories from scanning, complete
these steps:
1. After the WebDAV share is created, unset the immutable bits on .webdav directory:
# chattr -i .webdav/
2. Run the following command to exclude all files in the .webdav directory:
# ibrix_avconfig -a -E -f FS1 -P /FS1/.webdav/ -x '*'
3. Reset the immutable bit on the .webdav directory:
# chattr +i .webdav/
4. Exclude all files in the .DAV directory for each HTTP/WebDAV share created:
# ibrix_avconfig -a -E -f FS1 -P /FS1/httpshare/.DAV/ -x '*'
Segment evacuation
• The segment evacuator cannot evacuate segments in a READONLY, BROKEN or UNIVAILABLE
state.
NDMP
• When Symantec NetBackup is used, a full backup job fails for a file system with large directory
tree. To correct this, set TYPE=tar in the Backup Selections tab in Symantec NetBackup. This
changes the backup type to tar instead of the default dump and forces NetBackup to handle the
file-based NDMP file history.
The ibrix_collect command
• If collection does not start after a node recovers from a system crash, check the /var/crash/
<timestamp> 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.
• If the status of a collection is Partially_collected, typically the management console service
was not running or there was not enough space available in the /local disk partition on the
node where the collection failed. To determine the exact cause of a failure during collection, see
the following logs:
◦ /usr/local/ibrix/log/fusionserver.log
◦ /usr/local/ibrix/log/ibrixcollect/ibrixcollect.py.log
• Email notifications do not include information about failed attempts to collect the cluster
configuration.
20 Workarounds