CLI Guide
• Capacity for rollback processing, which is 1/5000th of the capacity of the base virtual disk.
If you are creating a new repository virtual disk when you run this command, you must enter the name of
a disk group or disk pool from which you want the repository virtual disk. Optionally, you can also define
the capacity of the repository virtual disk. The following capacity values are supported:
• A percentage ( integer value) representing an amount of the base virtual disk capacity.
• A decimal fraction representing a percentage of the base virtual disk capacity.
• A specific size for the repository virtual disk, in units of bytes, KB, MB, GB, or TB.
To increase capacity for a snapshot virtual disk, use the increaseRepository Capacity and
capacity parameter as shown below:
set snapVirtualDisk[“snapVirtualDiskName”] increaseRepositoryCapacity
repositoryVirtualDisks=("repos_xxxx" | repositoryVirtualDisks=(diskGroupName
[capacity=capacityValue]) repositoryVirtualDisks=(diskPoolName
[capacity=capacityValue]))
To decrease capacity, replace increaseRepositoryCapacity with decreaseRepository:
set snapVirtualDisk ["snapVirtualDiskName"] decreaseRepositoryCapacity
count=numberOfVirtualDisks
Setting Snapshot Group Repository Virtual Disk Capacity
To increase or decrease capacity of a snapshot group repository virtual disk, use the same basic
command syntax as shown previously for the virtual disk repository, except use the set snapGroup
command and supply the snapshot group name:
set snapGroup ["snapGroupName"] increaseRepositoryCapacity
(repositoryVirtualDisks="repos_xxxx" | repositoryVirtualDisks=((
diskGroupName
[capacity=capacityValue])) | repositoryVirtualDisks=((diskPoolName
[capacity=capacityValue])))
For more information about expanding storage objects, see the Administrator's Guide.
Reviving Disk Groups, Physical Disks, Snapshot Groups, And Snapshot Virtual
Disks
The revive command forces failed physical disks, disk groups, snapshot groups and snapshot virtual
disks into an Optimal state. However, this command should only be performed by qualified storage
administrators.
CAUTION: Possible loss of data access—Correct use of this command depends on the data
configuration on the physical disks in the disk group. Do not attempt to revive a physical disk or
disk group unless you are explicitly directed by your Technical Support representative.
To revive a physical disk:
revive physicalDisk [enclosureID,drawerID,slotID]
For MD-series dense storage arrays, all three location attributes (enclosureID, drawerID and slotID) are
required. For non-dense storage arrays, only enclosureID and slotID are required. Valid enclosureID
values are 0 to 99, drawerID values are 0 to 4 and slotID values are 0 to 31.
To revive disk group:
revive diskGroup [diskGroupName]
To revive a snapshot virtual disk, the snapshot virtual disk must be a:
66