Administrator Guide

node’s cache devices, because all data is local to the client. If this option is not selected, cached data

is evenly distributed among all cache devices.

NOTE: Use of this option with vMotioned guest VMs may result in reduced performance for that

VM.

9. Click Finish.

At this stage, there is a delay while the system makes a number of configuration changes. When

processing is complete, the volume is available for use in ESXi (as a datastore, RDM, and so on).

Mapping Volumes to a Subcluster

Before mapping volumes to a subcluster, create a Fluid Cache cluster (see Creating a Fluid Cache Cluster)

and a server cluster (“subcluster”) within it.

To map a volume to a subcluster, follow the procedure for mapping a volume to a server (see previous

section), but instead of selecting a server in the Map Volume to Server window (step 4), select a

subcluster within a Fluid Cache cluster.

Although not specific to Fluid Cache, be aware of these aspects of volume mappings created at the

subcluster level in Enterprise Manager:

• When servers are added to or removed from the subcluster, they automatically inherit or disinherit the

subcluster’s volume mappings.

• You can promote a volume mapping from a server to the subcluster, and demote it from the cluster

to the subcluster.

• If a server has existing mappings, the server keeps those mappings when it becomes part of a

subcluster.

Removing Volume Mappings

To see a list of Fluid Cache mappings, select the appropriate Storage Center in the Storage view, and in

the in the Storage tab, select the Fluid Cache cluster. The Fluid Cache mappings for the cluster are listed

in the Volumes area at the bottom of the page.

Removing Volume Mappings from a Server

1. Make sure the volume is no longer in use and unmounted in vCenter.

2. In Enterprise Manager’s Storage view, expand Storage Centers if necessary and select the

appropriate Storage Center. (Do not select Fluid Cache Clusters or its contents.)

3. In the Storage tab, expand Servers if necessary and locate the server whose Fluid Cache mappings

you want to remove.

4. Right-click the server and select Remove Mappings.

The Remove Mappings window is displayed.

5. In the Remove Mappings window, select the volume and click OK.

There may be some delay while the mapping is removed and dirty data in the cache is flushed to

main storage. When the mapping removal is complete, the volume’s icon in the Storage tab turns

from blue to gray color. You may need to manually refresh the display.

NOTE: The Fluid Cache mappings for the server are listed in the Volumes area at the bottom of

the page.