Configuring an iscsi volume, Example – HPP Enterprises P4000 SAN User Manual

Page 9

Advertising
background image

9

Configuring an iSCSI volume

The XenServer SR stores VM data on a volume (iSCSI Target) that is a logical entity with specific
attributes. The volume consists of storage on one or more storage nodes.

When planning storage for your VMs, you should consider the following:

How will that storage be used?

What are the storage requirements at the OS and application levels?

How would data growth impact capacity and data availability?

Which XenServer host – or, in a resource pool, hosts – require access to the data?

How does your DR approach affect the data?

Example

An HP StorageWorks P4000 SAN is configured using the Centralized Management Console (CMC).
In this example, the HP-Boulder management group defines a single storage site for a XenServer host
resource pool (farm) or a synchronously-replicated stretch resource pool. HP-Boulder can be thought
of as a logical grouping of resources.
A cluster named IT-DataCenter contains two storage nodes, v8.1-01 and v8.1-02.

20 volumes have currently been created. This example focuses on volume XPSP2-01, which is sized at
10GB; however, because it has been thinly provisioned, this volume occupies far less space on the
SAN. Its iSCSI qualified name (IQN) is iqn.2003-10.com.lefthandnetworks:hp-boulder:55:xpsp2-01,
which uniquely identifies this volume in the SR.
Figure 2 shows how the CMC can be used to obtain detailed information about a particular storage
volume.

Advertising