6.0 HP StorageWorks X9000 File Serving Software Release Notes (TA768-96042, October 2011)

Block snapshots
• Snapshot creation may fail while mounting the snapshot. The snapshot will be created successfully,
but it will not be mounted. Use the following command to mount the snapshot manually:
ibrix_mount -f <snapshotname> -m /<snapshotname>
• Quotas are disabled on block level snapshots (for example, MSA2000 snapshots) and the quota
information from the origin file system is not carried to the block level snap file system. Block level
snapshots are temporary file systems that are not writable. Users should not query quota information
against block level snap file systems.
• After the initial creation of a snapshot, it can take 4 to 6 minutes to mount the snapshot.
Remote Replication
• 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. To ensure that replication takes
place, do not unmount the target file system.
• When continuous remote replication is used and File Serving Nodes are configured for High
Availability, you will need to take the following steps following failure of a node:
1. Stop continuous remote replication.
2. After the migration to the surviving node is complete, restart continuous remote replication
to heal the replica.
If these steps are not taken, any changes that had not yet been replicated from the failed node
will be lost.
• No alert is generated if the continuous remote replication target becomes unavailable. Confirm
the connection to the target system by issuing a ping command and by inspecting
ibrcfrworker.log.
• Sparse files on the source file system are replicated unsparse on the target. That is, all blocks
corresponding to the file size are allocated on the target cluster. Consequently, if the target file
system is the same size as the source file system, remote replication can fail because there is no
space left on the target file system. To work around this situation, if the source system contains
large sparse files, be sure that the target file system is larger than the source file system, and large
enough to fit all files in an unsparsed manner.
• The mountpoint /mnt/ibrix is reserved for remote replication. Hiding or blocking this mountpoint
by mounting anything over the parent /mnt will prevent Run Once replication from working at
all, and the initial domain scan of Continuous replication will fail.
Data retention and validation
• The ibrix_reten_adm command fails if the date string specified with -e contains spaces. As
a workaround, use the following command to enter date strings containing spaces:
/usr/local/ibrix/sbin/ibr_reten_adm -e expire_time -f FSNAME -P PATHLIST
• NDMP cannot restore files from an NDMP backup of a filesystem enabled for data retention to
a filesystem that is not retention-enabled. If this is attempted, the X9000 NDMP Server returns
errors to the user’s backup application. The errors can include messages such as Error setting
10 Workarounds