HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition (software-only) Release Notes (432086-004, February 2008)

ManualsBrandsHP ManualsStorageHP DL380-SL Clustered Gateway

Legato NetWorker volume shadow copy not supported [5807]

HP Clustered Fi

SystemGateway does not currently support the manner in which Legato N etWorker

7.1.1 u s e s v o l u

shadow copies. HP recommends that you conﬁgure NetWorkersothatitdoesnot use

shadow copies. One way to do this is to choose Options > Save Options in the NetWorker client,

and then type VSS:*=off in the options box.

Reinstalling HP Clustered File SystemGateway with an evaluation license

requires new conﬁguration [5838 ]

An HP Clustered File SystemGatew ay conﬁ guration createdwithanevaluationlicense cannot be

used if HP Clustered File SystemGateway is reinstalled with an evaluation license. When uninstalling

HP Clustered File SystemGateway, do not check the “Keep the existing Clustered File SystemGateway

conﬁguration” option. This option prohibits the use of the evaluation license provided with the H P

Clustered File SystemGateway distribution.

Built-in NT backup software fails on PSFS volumes when volume shadow copy is

enabled [5

89 7]

Volume sha

dow c opy is enabled by default in the built-in NT backup software provid ed with Windows

2003. The PSFS ﬁlesystem does not support volume shadow copies. If you want to use the N T backup

software on a PSFS volume, disable volume shadow copy.

Server’s IP address may change if assigned with DHCP [6364]

When DHCP or DH C P reservations are used to assign IP addresses to servers, the IP address can change

when the server is rebooted. The DHCP server may be slow to respond to the reboot, resulting in the

server temporarily using a rand om automatic IP address until the DHCP address is acquired. While the

server has the temporary address, it cannot rejoin the cluster, as HP Clustered File SystemGateway

expects the server to have the DHCP address.

During this pro cess, the cluster conﬁguration might be destroyed on the rebooted server; however, the

conﬁguration can be restored by importing it from another node in the cluster (or by exporting the

conﬁguration from a goo d node to the rebooted ser ver).

To avoid this problem, use static IP addresses for the servers that will be in the cluster.

Third-party MPIO software must discover devices [7519]

When third-party MPIO software is used, it must discover and present storage devices to the operating

system before HP Clustered File System is conﬁgured or started.

If HP Clustered File System is started a nd the third-party MPIO software has not previously discovered the

devices, HP Clustered File S ystem makes a “best effort” to discover them. In some cases, HP Clustered

File S

ystem initiates asinglereboot. HP ClusteredFile System doesnot startifitcannotdiscoverthe

devices. The administrator must then determine why the MPIO devices have not been discovered and

resolve the issue.

HP Clustered File SystemGateway Installer does not ﬁ nd saved conﬁguration

[7551]

When HP Clustered File System is uninstalled, you can save the cluster conﬁguration. If you then reinstall

HP Clustered File System in a different location, the Installer will not ﬁnd the saved conﬁguration. To avoid

this

problem, reinstall HP Clustered File System in its original location. The Installer will then ﬁnd the saved

conﬁguration and apply it to the new installation of HP Clustered File System.

If you need to install HP Clustered File System in a new location, move the saved conﬁguration ﬁles to

the

new location before the HP Clustered File System installation.