mkvolumegroup
Use the mkvolumegroup command to create and configure a new volume group.
Syntax
Make a safeguarded volume group (this does not apply to safeguarded copy with volume group snapshot)
Parameters
- -name volumegroup_name
- (Optional) Specifies a volume group name. The value must be an alphanumeric value. If you do not specify a volume group name, one is automatically created and assigned to the volume group.
- -ownershipgroup owner_id | owner_name
- (Optional) Specifies the name or ID of the ownership group in which the volume group will be created. This parameter is mutually exclusive with -partition parameter. When a volume group is created in a partition, the ownership group is inherited from the partition.
- -snapshotpolicy snapshot_policy_id | snapshot_policy_name
- (Optional) Specifies the snapshot policy to assign to the volume group.
- -type thinclone | clone
- (Optional) Specifies the type of volume to create.
- -fromsourceuid parent_uid
- (Optional) Specifies the UID used to identify the parent volumes of the snapshot to pre-populate the new volume in the new volume group.
- -fromsourcegroup volume_group_id | volume_group_name
- (Optional) Specifies the name or ID of the parent volume group of the snapshot to pre-populate the new volume in the new volume group.
- -snapshot snapshot_name
- (Optional) Specifies the name of the snapshot that is used to pre-populate the new volumes in the new volume group.
- -fromsnapshotid snapshotid
- (Optional) Specifies the ID of the snapshot used to pre-populate the new volumes in the new volume group.
- -fromsourcevolumes list_of_volume_ids | list_of_volume_names | list_of_volume_uids
- (Optional) Specifies the IDs, names, or UIDs of the parent volumes.Note: When combined with the -type and -snapshot parameters, you can create a volume group with a subset of those volumes whose image is present in a snapshot.
- -pool pool_name_or_id
- (Optional) Specifies the name or ID of the pool to contain the volumes.
- -iogroup io_group_name_or_id
- (Optional) Specifies the name or ID of the I/O group for the new volume.
- -replicationpolicy replication_policy_name_or_id
- (Optional) Specifies the replication policy to assign to the volume group.
If the replication policy has an async-dr topology the volume group must be created in the storage partition associated with the async-dr replication policy. A replication policy with the async-dr topology is associated with only one storage partition.
If the associated storage partition is a 2-site-ha storage partition the volume group will be HA with async-dr replication configured, otherwise it will create a volume group with DR replication. An async-dr replication policy will have DR linked storage partitions.
Note: This command can succeed whether the remote system in the replication policy is connected or disconnected. When connectivity is restored, the volume group is created on the remote system.Note: You cannot assign a replication policy to the volume group if the group contains any volumes with the following characteristics:- Volumes are in a different I/O group than the I/O group that is specified in the replication policy.
- Volumes have disabled cache.
- Volumes are image mode volumes.
- Volumes are used in Transparent Cloud Tiering (TCT).
- -safeguarded
- (Optional) Specifies that the snapshot policy creates Safeguarded snapshots of source volumes in
the volume group.Note: The -safeguarded parameter can only be specified with the -snapshotpolicy parameter.
- -ignoreuserfcmaps
- (Optional) Indicates that snapshots can be created with the scheduler or with the addsnapshot command, if any volumes in the volume group are used as a source volume in legacy FlashCopy mapping.
- -partition partition_name | partition_id| partition_uuid
- (Optional) Specifies the storage partition to assign to the volume group. This operation can be
performed whether the remote systems in the partition are connected or disconnected. The volume
group is created on the remote systems when connectivity allows. The command must be run on the
active management system for the specified partition.Note: If a storage partition is assigned to a volume group, that storage partition cannot be removed from the volume group and that volume group's replication policy can not be changed. A storage partition can only be removed from a volume group by removing the volume group using rmvolumegroup.Note: This parameter is mutually exclusive with the -type parameter and the -replicationpolicy parameter. The -ownershipgroup parameter is not supported when this parameter is specified.
- -draftpartition partition_name | partition_id| partition_uuid
- (Optional) Specifies the draft partition to assign to the volume group.
- -nopartition
- (Optional) Creates a clone or a thinclone volume group outside of the partition that the volume group or a snapshot was in originally.
- -setpartitiondefault
- (Optional) Specifies the volume group as default volume group. When added to a partition, the volume group will act as default volume group for the partition.
Description
- When added to a partition, there can be only one default volume group per partition.
- There is no limit on the count of volumes that can be added a default volume group.
- Replication and snapshot policies cannot be applied to a default volume group.
- It is possible to apply 2-site-HA policy on a partition only if its default volume group has less than 512 volumes
- The user must identify objects using the name or UUID. Short IDs cannot be specified when using the partition IP address.
- Only objects belonging to the partition can be created or acted upon. When creating new objects, the -partition parameter will be auto-populated for the partition. You cannot move items out of a partition when using the partition IP address.
An invocation example
mkvolumegroup
The resulting output:
Volume Group, id [0], successfully created.
An invocation example
mkvolumegroup -name Sunday
The resulting output:
Volume Group, id [1], successfully created
An invocation example creates a volume group with an association to a snapshot policy:
mkvolumegroup -snapshotpolicy 2
The resulting output:
Volume Group, id [4], successfully created.
An invocation example to create a volume group with an association to a snapshot policy and specifies a start time to use with this volume group:
mkvolumegroup -snapshotpolicy 2 -policystarttime 2203011800
The resulting output:
Volume Group, id [5], successfully created.
An invocation example
mkvolumegroup -type thinclone -fromsourcegroup sourceGroupA -snapshot noon
The resulting output:
Volume Group, id [6], successfully created.
An invocation example
The following example creates a volume group and associates it with a storage partition:
mkvolumegroup -partition partition0
The resulting output:
Volume Group, id [0], successfully created
An invocation example
The following example creates a volume group and associates it with a storage partition:
mkvolumegroup -partition partition0
The resulting output:
Volume Group, id [0], successfully created
An invocation example
svctask mkvolumegroup -type thinclone -fromsourcegroup sourceGroupA -snapshot noon -fromsourcevolumes 4:5
The resulting output:
Volume Group, id [0], successfully created
An invocation example
svctask mkvolumegroup -type clone -fromsnapshotid 0 -name cloneVolumeGroupB -pool clonesPool -fromsourcevolumes volA:volB:volC
The resulting output:
Volume Group, id [0], successfully created
An invocation example
The following example creates a volume group with -nopartition:
mkvolumegroup -type clone -fromsourcegroup 0 -snapshot snapshot0 -nopartition
The resulting output:
Volume Group, id [0], successfully created
An invocation example
mkvolumegroup -type clone -fromsourcegroup 0 -snapshot ha_snapshot0
CMMVC1243E The command failed because the volume group is part of a storage partition that has a replication policy.
The resulting output:
Volume Group, id [0], successfully created
