Object descriptions

This topic describes the objects in a SAN Volume Controller and the relationships between these objects.

The SAN Volume Controller is based on the following virtualization concepts which are discussed more fully later in this chapter.

The smallest processing unit in a SAN Volume Controller is a single node. Nodes are deployed in pairs to make up a cluster. A cluster may have either one or two node pairs in it. Each pair of nodes is known as an I/O group. Each node may be in only one I/O group.

Virtual disks (Vdisks) are logical disks that are presented by clusters. Each virtual disk is associated with a particular I/O group. The nodes in the I/O group provide access to the virtual disks in the I/O group. When an application server performs I/O to a virtual disk, it has the choice of accessing the virtual disk via either of the nodes in the I/O group. As each I/O group only has two nodes, the distributed cache that the SAN Volume Controller provides is only two-way.

Each node does not contain any internal battery backup units and therefore must be connected to an Uninterruptible Power Supply (UPS) to provide data integrity in the event of a cluster wide power failure. In such situations, the UPS will maintain power to the nodes while the contents of the distributed cache are dumped to an internal drive.

The nodes in a cluster see the storage presented by backend disk controllers as a number of disks, known as managed disks (MDisks). Because the SAN Volume Controller does not attempt to provide recovery from physical disk failures within the backend disk controllers, a managed disk is usually, but not necessarily, a RAID array.

Each managed disk is divided up into a number of extents (default size is 16 MB) which are numbered, from 0, sequentially from the start to the end of the managed disk.

Managed disks are collected into groups, known as managed disk groups (MDisk group). Virtual disks are created from the extents contained by a managed disk group. The managed disks that constitute a particular virtual disk must all come from the same managed disk group.

At any one time, a single node in the cluster is used to manage configuration activity. This configuration node manages a cache of the information that describes the cluster configuration and provides a focal point for configuration.

The SAN Volume Controller detects the Fibre Channel ports that are connected to the SAN. These correspond to the Host Bus Adapter (HBA) Fibre Channels world wide port names (WWPNs) that are present in the application servers. The SAN Volume Controller allows you to create logical host objects that group together WWPNs belonging to a single application server or a set of them.

Application servers can only access virtual disks that have been allocated to them. Virtual disks can then be mapped to a host object. The act of mapping a virtual disk to a host object makes the virtual disk accessible to the WWPNs in that host object, and hence the application server itself.

The SAN Volume Controller provides block level aggregation and volume management for disk storage within the SAN. In simpler terms, this means that the SAN Volume Controller manages a number of back-end storage controllers and maps the physical storage within those controllers into logical disk images that can be seen by application servers and workstations in the SAN. The SAN is configured in such a way that the application servers cannot see the back-end physical storage; this prevents any possible conflict between the SAN Volume Controller and the application servers both trying to manage the back-end storage.

The following figure is a representation of the objects described in this section and their logical positioning in a virtualized system.

Note:Note: Virtual disk to host mappings have not been shown to simplify the figure.
Figure 239. Virtualization
Virtualization

Items such as virtual disks, managed disks, and managed disk groups are known as objects. It is important that you understand what these objects are, how you use them, and their relationships to one another, so that you can effectively configure and use the SAN Volume Controller.

(C) Copyright International Business Machines Corporation 2003, 2004