IBM System Storage DS3000, Programming Manual

Page: 87 / 652

term member means a base logical drive for Enhanced FlashCopy operations. You can manipulate
Enhanced FlashCopy images associated with members of a consistency group through batch-style
operations, while maintaining consistency across the Enhanced FlashCopy images.
Each member logical drive must have a corresponding repository logical drive. You can define the
relationship between the member logical drive and the repository logical drive using the
repositoryLogicalDrive
parameter. The
repositoryLogicalDrive
parameter can perform one of these
actions:
v
Identify an existing repository logical drive that is connected to the consistency group.
v Identify either an subsystem or a disk pool in which you want to create a repository logical drive.
Adding a member to a consistency group with an existing repository has two purposes:
v
You can create an entirely new repository logical drive by running the command without the
repositoryLogicalDrive
parameter. When you run the command without the
repositoryLogicalDrive
parameter the command creates a repository logical drive in the subsystem or disk pool in which all
the other repository logical drives are stored. An example of this command usage is:
set consistencyGroup [" First_Images "] addCGMemberLogicalDrive=" Data_020212 "
You can reuse an existing repository logical drive if:
v
that repository logical drive is empty
v that repository logical drive is not related to another member logical drive
v
you want to maintain a particular sequence or relationship for the repository logical drives
To reuse an existing, empty repository logical drive you need to know the name of the repository logical
drive. To determine the name of the repository logical drive use the
show allLogicalDrives summary
command. All repository logical drive names have the form repos_XXXX , where XXXX is a unique
identifier generated by the storage management software. An example of this command usage is:
set consistencyGroup [" First_Images "] addCGMemberLogicalDrive=" Data_020212 "
repositoryLogicalDrive=" repos_0011 "
You can place the repository logical drive in an subsystem or a disk pool of your choosing. You are not
required to have the repository logical drive in the same location as other repository logical drives. To
place the repository logical drive in an subsystem or a disk pool of your choice, use the
repositoryLogicalDrive parameter and identify the subsystem or the disk pool and a size for the
repository logical drive. An example of this command usage is:
set consistencyGroup [" First_Images "] addCGMemberLogicalDrive=" Data_020212 "
repositoryLogicalDrive=" 12 " capacity=2 GB)
In this example, " 12 " is the name of an existing subsystem or an existing disk pool. The capacity
parameter defines the size that you want for the repository subsystem.
When you create a repository logical drive in either an subsystem or a disk pool, you must include
parenthesis around the subsystem name and capacity, or the disk pool name and capacity.
Add drives to Performance Read Cache
Use this command to increase the capacity of an existing Performance Read Cache by adding additional
solid state disks (SSDs).
Synatx
set performanceReadCache [performanceReadCacheName]
addDrives=(enclosureID1,drawerID1,slotID1 ...
enclosureIDn,drawerIDn,slotIDn)
Chapter 3. Script Commands
3-41