chvolumegroup

Use the chvolumegroup command to change volume group properties.

Syntax

Read syntax diagramSkip visual syntax diagram chvolumegroup -namevolumegroup_name-ownershipgroupowner_id | owner_name-noownershipgroup-safeguardedpolicysafeguarded_policy_id | safeguarded_policy_name-policystarttime start_time-nosafeguardedpolicy-snapshotpolicysnapshot_policy_idsnapshot_policy_name-safeguarded-policystarttime start_time-nosnapshotpolicy-replicationpolicyreplication_policy_namereplication_policy_id-nodrreplication-ignoreuserfcmapsyesno-retainbackupenabled-nosnapshotpolicy-draftpartitionpartition_namepartition_id volumegroup_namevolumegroup_id

Parameters

-name volumegroup_name
(Optional) Specifies a new volume group name. The value must be an alphanumeric string.
-ownershipgroup owner_id | owner_name
(Optional) Specifies the name or ID of the ownership group to which the object is being added.
-noownershipgroup
(Optional) If specified, the object is removed from the ownership group to which it belongs.
volumegroup_name | volumegroup_id
(Required) Specifies the volume group name or group ID for the volume you want to modify. The value must be a number for the volume group ID, and an alphanumeric string for the volume group name.
-safeguardedpolicy safeguarded_policy_id | safeguarded_policy_name
(Optional) Specifies the name or ID of the assigned Safeguarded backup policy to a volume group.
-policystarttime start_time
(Optional) Specifies when the first copy is taken using the specified policy. Indicates the time in YYMMDDHHMM format.
-nosafeguardedpolicy
(Optional) Specifies the removal of the Safeguarded policy that is assigned to a volume group.
-snapshotpolicy snapshot_policy_id | snapshot_policy_name
(Optional) Specifies the snapshot policy to assign to the volume group.
Note: If snapshot policy has cloud backup schedule, cloud backup is enabled for all vdisks in the volumegroup.
-nosnapshotpolicy
(Optional) Specifies the removal of snapshot policy assigned to a volume group.
Note: If snapshot policy has cloud backup schedule, cloud backup is disabled for all vdisks in the volumegroup. Additionally, -retainbackupenabled allows user to retain cloud backup enabled for the vdisks.
-replicationpolicy replication_policy_name | replication_policy_id
(Optional) Specifies the replication policy to assign to the volume group.

When the replication policy has an async-dr topology then the volume group must be in a storage partition and the async-dr replication policy must be associated with that storage partition.

If the volumegroup is in a 2-site-ha storage partition and an associated async-dr replication policy is specified then the volumegroup will be HA with async DR replication configured. If the storage partition is not HA then the volume group will be created with only async DR replication configured.

Note:
  • This command can run whether the remote system in the replication policy is connected or disconnected. If the command succeeds, the policy is assigned immediately on the local system. The policy is assigned asynchronously on the remote system when connectivity is restored.
  • 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).
-nodrreplication
(Optional) Removes DR replication for the volume group.
Note:
  • This parameter is mutually exclusive with -replicationpolicy.
  • DR replication can be removed from a volume group configured with a 2-site-async-dr or async-dr replication policy.
-safeguarded
(Optional) Specifies that the snapshot policy creates Safeguarded snapshots of source volumes in the volume group.
Note: The -safeguarded option is not allowed while applying the cloud backup policy to a volume group.
-ignoreuserfcmaps
(Optional) Allow a user to create snapshots through the scheduler or manually with the addsnapshot command. It can only be done if a volume in the volume group is used as a source of a user FlashCopy mapping. Values can be yes or no.
-draftpartition partition_name | partition_id
Attempt to associate this volume group with the specified draft partition.
-retainbackupenabled
(Optional) Retains cloud backup enabled for the vdisk.
Case 1
If a vdisk is removed from a volume group without using -retainbackupenabled, the cloud backup is disabled for that vdisk.
Case 2
If a vdisk is removed from the volume group using -retainbackupenabled, the cloud backup remains enabled for that vdisk.

Creating snapshot policies

The value in the -policystarttime parameter overrides the -backup_start_time parameter in the snapshot policy. It is used when the first snapshot is created. The frequency information in the snapshot policy determines the timing of all the subsequent snapshots. If the value is in the past, the frequency information in the snapshot policy is used to determine the appropriate time for the first snapshot to be taken.

Creating Safeguarded backup policies

The value in -policystarttime overrides the backup_start_time in the Safeguarded policy. It is used for determining when the first Safeguarded backup is created. After this the frequency information in the Safeguarded policy determines the timing of all subsequent Safeguarded backups. If the value is in the past, the frequency information in the Safeguarded policy is used to determine the appropriate time for the first Safeguarded backups to be taken.

  • The value of -policystarttime should be specified in the local time of the system in YYMMDDHHMM format. Seconds are not to be specified.
  • If -safeguardedpolicy is specified and -policystartime is not specified any existing value of policy_start_time is cleared and the backup_start_time from the Safeguarded policy is used to determine when Safeguarded backup copies are created.
  • If -nosafeguardedpolicy is specified, any existing value of -policy_start_time is cleared.
  • The -safeguardedpolicy parameter is mutually exclusive with -nosafeguardedpolicy, -ownershipgroup and -noownershipgroup.
  • The -nosafeguardedpolicy parameter is mutually exclusive with -ownershipgroup.
  • If the volume group is associated with an ownership group, the -safeguardedpolicy parameter fails.
  • If the volume group is associated with a Safeguarded policy, the -ownershipgroup parameter fails.

A volume group can be associated with a Safeguarded backup policy only if all volumes it contains meet all the requirements to be a Safeguarded source volume. If any volume does not meet those requirements, the -safeguardedpolicy parameter fails. For more information, refer to Snapshots.

Note: You cannot modify the name of the volume group if the volume group is in a storage partition with an HA replication policy assigned. You cannot assign or remove a replication policy from a volume group in a storage partition. Volume groups in a storage partition can not be in an ownership group. These restrictions apply to a single-system partition and a partition with an HA replication policy assigned.
Note: Policing on other commands ensures that a replication policy with async-dr topology can only be created and associated with a partition if that partition has DR links configured. There is no requirement to police this as part of the chvolumegroup command when using -replicationpolicy parameter.

An invocation example

chvolumegroup -name newname1 1

The resulting output:

No feedback