HP Clustered FileSystem3.6.1 for Windows release notes (T4422-96003, September 2008)

Issue
Description
Shadow copy option is available for snapclon es
13275
When you create a snapclone on the Create Snapshot window, the option to
“Share as Shadow Copy of Shared Folder” is available; however, a shadow copy
cannot be created from a snapclone and the option is unused.
13 411
13587
13988
13996
Synchronized bookmarks do not work with secondar y interface
If you are unable to connect to the cluster using the primary network interfaces on
your servers beca
use of the network infrastructure or a firewall, the “S ynchroniz e
Server Bookmark
s
Automatically” option should be disabled. If it is not disabled,
bookmarks that
contain addresses on a secondary interface will be replaced
with the unreac
hable
primary interface.
The Java client VM terminates when mx commands are run from a monitor script
Although not a fi x for this issue, placing a .matrixrc file in the following folder
may prevent the crash.
C:\Documents and Settings\Default User\
vssadmin cannot be used with snapshots
When snapshots are created through the HP Management Console or the mx
snapshot command, they are created via the HP EVA array interface without the
involvement of VS S (Microsoft’s V olume Shadowcopy Service). However, when
you select the “Shadow Copies of Shared Folders” checkbox, sufficient information
must be cr eated to inform VSS of the existence of the snapshot so that it can be
shared to CIFS clients.
These SCSF-enabled snapshots are visible in the output of vssadmin.exe list
shadows and
they are identifiable by their all-zero GUIDS and other invalid
information. These snapshots are not real VSS snapshots, and cannot be deleted
via the vssadmin command. They should generally be managed with the HP
Management
Console or the mx snapshot command instead.
mx fs des
troy partially destroys snapshots
Do not us
ethe mx fs destroy command to remove a snapshot. If you attempt
to delet
e a
snapshot with the mx fs destroy command, the snapshot filesystem
will be
removed but the snapshot will remain on the array. You will then need to
manual
ly remove the snapshot LUNs from th e array. (After removing the LU Ns, you
will see disk import errors on the console for the LUNs that were removed.)
If you need to delete a s napshot, either use the mx snapshot destroy
command
or locate the snapshot on the HP Management Console, right-click,
and select Delete .
16