Filter
Top Products
HP StorageWorks 2000 G2 Modular Smart Array Reference Guide 45
3 Provisioning the system
Using the Provisioning Wizard
The Provisioning Wizard helps you create a vdisk with volumes and to map the volumes to hosts. The
wizard has several steps, which are highlighted at the bottom of the panel as you complete them. The last
step prompts you to confirm changes before applying them. If you cancel the wizard, no changes are
made.
Step 1: Starting the wizard
1. In the Configuration View panel, right-click the system and select either Provisioning > Provisioning
Wizard or Wizards > Provisioning Wizard. The wizard panel appears.
2. Click Next to continue.
Step 2: Specifying the vdisk name and RAID level
A vdisk is a “virtual” disk that is composed of one or more disks, and has the combined capacity of those
disks. The number of disks that a vdisk can contain is determined by its RAID level. All disks in a vdisk must
be the same type (SAS or SATA, small or large form-factor). A maximum of 16 vdisks per controller can
exist.
A vdisk can contain different models of disks, and disks with different capacities. For example, a vdisk can
include a 500-GB disk and a 750-GB disk. If you mix disks with different capacities, the smallest disk
determines the logical capacity of all other disks in the vdisk, regardless of RAID level. For example, if a
RAID-0 vdisk contains one 500-GB disk and four 750-GB disks, the capacity of the vdisk is equivalent to
approximately five 500-GB disks. To maximize capacity, use disks of similar size. For greatest reliability,
use disks of the same size and rotational speed.
In a single-controller system, all vdisks are owned by that controller. In a dual-controller system, when a
vdisk is created the system automatically assigns the owner to balance the number of vdisks each controller
owns; or, you can select the owner. Typically it doesn’t matter which controller owns a vdisk.
In a dual-controller system, when a controller fails, the partner controller assumes temporary ownership of
the failed controller's vdisks and resources. If the system uses a fault-tolerant cabling configuration, both
controllers' LUNs become accessible through the partner.
When you create a vdisk you can also create volumes within it. A volume is a logical subdivision of a
vdisk, and can be mapped to controller host ports for access by hosts. The storage system presents only
volumes, not vdisks, to hosts.
To create a vdisk
1. Set the options:
• Vdisk name. Optionally change the default name for the vdisk. A vdisk name is case sensitive and
cannot already exist in the system. A name cannot include a comma, double quote, or backslash.
• Assign to. Optionally select a controller to be the preferred owner for the vdisk. The default, Auto,
automatically assigns the owner to load-balance vdisks between controllers.
• RAID Level. Select a RAID level for the vdisk.
• Number of Sub-vdisks. For a RAID-10 or RAID-50 vdisk, optionally change the number of sub-vdisks
that the vdisk should contain.
• Chunk size. For RAID 1, 3, 5, 6, 10, or 50, optionally set the amount of contiguous data that is
written to a vdisk member before moving to the next member of the vdisk. For RAID 50, this option
sets the chunk size of each RAID-5 sub-vdisk. The chunk size of the RAID-50 vdisk is calculated as:
configured-chunk-size x (subvdisk-members - 1). The default is 64KB.
2. Click Next to continue.