Owners Manual

The Cluster Settings page of the configuration wizard is displayed.

8. Type or select appropriate data in the Cluster Settings window.

a. In the Name box, enter a name for the cluster.

b. Click Browse next to the License File box.

The Select Fluid Cache License File dialog box is displayed.

c. Browse to the location of the license file, select the file, and then click Save.

d. Verify that the license file and path displayed are correct and click Next.

The system processes for a few minutes while the cluster is created and the system automatically

identifies compatible servers and devices on the network. After this process is completed, the

Select Devices window is displayed.

9. By default, all available Fluid Cache devices are selected. Clear the check box next to unwanted

devices or select the Unselect All option, and then select the required devices. (Select the Select All

option to use all available devices again.)

CAUTION: You will lose any existing data on the cache devices when they are added to the

Fluid Cache cluster. Back up this data before proceeding.

10. Click Next.

The Select Storage Centers page of the configuration wizard is displayed.

11. In the Select Storage Centers page, select one or more Storage Centers to include in the Fluid

Cache cluster, and then click Finish.

After a delay while the system processes, the Storage pane contains a new top-level folder named

Fluid Cache Clusters. Inside this folder is the Fluid Cache cluster that was just created. Fluid Cache

clusters are denoted by a blue circle with the letters FC.

Select the Fluid Cache cluster. In the Summary tab, different areas of the window show the cluster's

status, servers, devices, and other information.

After creating a Fluid Cache cluster, map volumes to the cluster. See Mapping Volumes.

Mapping Volumes in Fluid Cache

In Enterprise Manager, volume mappings created for a server in a Fluid Cache cluster behave similar to

any other volume mappings. Volumes can be mapped either to an individual server, or to a server cluster

(a “subcluster”) within the Fluid Cache cluster.

NOTE: If you have a shared data application, such as a clustered file system or clustered application,

map volumes to a subcluster.

NOTE: Any applications that were using a volume before it was cached must be modified to use the

new cached volume. When a cached volume is mapped to one or more servers, Fluid Cache creates

its own Linux device file, /dev/fldcX. (The first device mapped is /dev/fldc0, the second

is /dev/fldc1, and so on.) Any application that uses the cached volume must be configured to

use the new Fluid Cache device rather than the

/dev/sdX or /dev/mpathX device. If the cached

volume is shared by multiple servers, the /dev/fldcX device is available on each server.

Mapping Volume to Servers

Before mapping a volume to a server node, create a Fluid Cache cluster (see Creating a Fluid Cache

Cluster).