chpartition

Use the chpartition command to modify a storage partition.

Syntax

Read syntax diagramSkip visual syntax diagram chpartition -namepartition_name-replicationpolicyreplication_policy_namereplication_policy_id-noreplicationpolicy-deletepreferredmanagementcopy-accessstalecopy-preferredmanagementsystemsystem_namesystem_id-makedrlink-remotedrlinkedpartitionuuidpartition_uuid-remotesystemsystem_namesystem_id-removedrlink-forceupperlocationyesno-publish-locationlocation_system_namelocation_system_id-override-locationuuidremote_system_grid_uuid-override-managementportsetmanagement_portset_idmanagement_portset_name-nomanagementportset-ownershipgroupownershipgroup_nameownershipgroup_id-noownershipgroup-migrationactionfixeventwithchecksfixeventskipcheckscancelrollback partition_idpartition_namepartition_uuid

Parameters

-name partition_name
(Optional) Specifies a name for the storage partition. The value must be an alphanumeric string.
-replicationpolicy replication_policy_name | replication_policy_id
(Optional) Specifies to assign a replication policy for the storage partition. This operation can be performed whether the remote systems in the policy are connected or disconnected. If the command is successful, the change is applied asynchronously to the remote system. The replication policy must be a HA replication policy.
A replication policy cannot be applied to a storage partition if any volume group that is associated with the storage partition contains volumes that are:
  • cache disabled
  • image mode
  • configured to use Transparent Cloud Tiering (TCT)
  • zero size
  • in the process of removing associated system resources for replication
  • a volume with a copy in a standard pool and a copy in a data reduction pool.

A replication policy cannot be assigned to a partition if any associated volume groups have a replication policy with a 2-site-async-dr topology assigned.

When making a disaster recovery link, if there are any volume groups in the partition with a 2-site-async-dr replication policy assigned, the specified remote system must match the remote system of the 2-site-async-dr replication policies.

Additionally, any 2-site-async-dr volume groups that are being migrated to async-dr replication policies must have been added to both the local and remote partition before a disaster recovery link can be made.

Note: This parameter is mutually exclusive with -noreplicationpolicy, -accessstalecopy and -preferredmanagementsystem parameters.
-noreplicationpolicy
(Optional) Specifies to remove the replication policy from the storage partition. This operation can be performed whether the remote systems in the policy are connected or disconnected. The remote storage partition and associated objects are removed asynchronously.

If the -deletepreferredmanagementcopy flag is specified, the command is only permitted on the active management system, and the active management system should not be equal to the preferred management system. This allows for the replication policy to be removed in response to the complete loss of the remote system.

Note: This parameter is mutually exclusive with -replicationpolicy, -accessstalecopy and -preferredmanagementsystem parameters.
-deletepreferredmanagementcopy
(Optional) Specifies to remove the preferred management copy of the storage partition. Specify -noreplicationpolicy parameter with this parameter and the active management system must not be the same as the preferred management system.
-accessstalecopy
(Optional) Specified to modify the UUID of the volumes associated with the storage partition. This parameter is only permitted when the command runs on the non-active management system and the preferred management system is ignored. The UUID of all volumes in the storage partition will be changed and vdiskhostmaps will be deleted. The replication policy is removed from the storage partition resulting in a single-system storage partition, and all fields that refer to a replication policy in the storage partition view will be blank.
If volumes are offline on the system where this command is run, the command completes successfully, but all volumes in each group remain offline until a consistent image can be made available. Volumes may be deleted while in this state and a new replication policy cannot be applied until the consistent image is restored.
Note: This parameter is mutually exclusive with -replicationpolicy, -noreplicationpolicy and -preferredmanagementsystem parameters.
-preferredmanagementsystem
(Optional) Specifies to modify the preferred management system for the storage partition. This operation can be performed while the remote systems in the policy are connected, or under the following conditions while disconnected:
  • If the storage partition has HA and there is management access to the remote system, the command succeeds and the change will be applied to both systems.
  • If the storage partition has HA and there is no management access to the remote system then the command will fail.
  • If the storage partition does not have HA, then the operation succeeds and the configuration change will be applied to the remote system in line with other configuration and data syncing that is required to regain HA, which may mean to wait for management connectivity to resume if there is currently no connectivity.
Note: This parameter is mutually exclusive with -replicationpolicy, -accessstalecopy and -noreplicationpolicy parameters.
-makedrlink
(Optional) Creates the disaster recovery link between this partition and a partition on a remote system. This operation can only be performed when the partition does not already have a disaster recovery link.
Note: This parameter requires -remotesystem and -remotedrlinkedpartitionuuid and is mutually exclusive with -removedrlink.
-remotesystem
(Optional) Specifies the remote system where the partition to link exists.
Note: This parameter requires -makedrlink and -remotedrlinkedpartitionuuid.
-remotedrlinkedpartitionuuid
(Optional) Specifies the uuid of the remote partition to link.
Note: This parameter requires -makedrlink and -remotesystem.
-removedrlink
(Optional) Removes the disaster recovery link from this partition.
Note: This parameter is mutually exclusive with -makedrlink
-forceupperlocation
(Optional) Specifies this partition should be shown in the upper location of the topology diagram in the GUI, overriding the default layout for the view.
Note: This parameter is only used for partitions that are configured for 2-site replication for disaster recovery.
-publish
(Optional) Specify to publish a draft storage partition.
-ownershipgroup
(Optional) Specifies the name or ID of the ownership group to which the partition is being added.
  • This option also changes the ownership group of all volume groups and hosts in the partition to the specified ownership group.
  • For a draft partition, the ownership group for the volume groups and hosts is updated when the partition is published.
  • This parameter is mutually exclusive with -replicationpolicy parameter.
-noownershipgroup
(Optional) The partition is removed from the ownership group to which it belongs.
  • This option also removes the ownership group of all volume groups and hosts in the partition.
  • For a draft partition, the ownership group of its volume groups and hosts is removed when the partition is published.
  • This parameter is mutually exclusive with -ownershipgroup parameter.
Note:
  • The volume groups and the host objects in a partition inherit the ownership group from the partition.
  • Changing the ownership group of a partition will change the ownership group of its member volume groups and host objects.
-location location_system_name | location_system_id
(Optional) Specifies a desired target system location to migrate an existing storage partition.
-locationuuid remote_system_grid_uuid
(Optional) Specifies a desired target system grid system UUID to migrate an existing storage partition.
-override
(Optional) This parameter should be specified along with the -locationuuid or -location parameter to trigger any operations on an ongoing storage partition migration.
When used with -locationuuid or -location at source system:
  • If the location specified is the source system, it aborts any ongoing active or queued storage partition migration.
  • Abort is supported on source until the preferred management location gets switched to the target system.
When used with -locationuuid or -location at target system:
  • Rolls back the migrating storage partition to its original state at source system without deleting the target copy.
  • Rollback is supported on target until the user confirms the source copy delete event.
-migrationaction fixeventwithchecks | fixeventskipchecks | cancelrollback
(Optional) Specifies that this option is used when migrating a partition to a different system. If migration is stopped due to a logged error condition, use this command option to indicate how the partition migration should continue.
  • fixeventwithchecks: The system marks the event as fixed and recheck the configuration. If the error condition still exists, the event is logged again. This ensures migration only proceeds when error conditions are resolved.
    Note: Host validations are not performed at target cluster if storage partition migration occurs from source system with 8.7.2 version (or higher) to target system versions earlier than 8.7.2. For more information about for source copy deletion, see Event ID 051021 in Error event IDs and error codes.
  • fixeventskipchecks: The system marks the event as fixed and migration continues, without checking that the cause of the event is fixed. This forces migration to progress to the next logical step, ignoring the current error condition.
  • cancelrollback: This option is used to cancel ongoing storage partition migration rollback operation on target system. After cancelling rollback operation, migration continues on target system. This option is only applicable on target system when rollback operation is going on.
Note: This option is applicable only for specific migration states that may require your input to forcefully proceed with the partition migration or to continue validations for proper resolution. In other states where the new option is not applicable, the CLI will execute without taking any action.
-managementportset management_portset_id | management_portset_name
(Optional) Specifies a management portset object assigned to the partition object. The management portset must have at least one IP address and cannot be the SystemManagement portset.
Note: The -managementportset parameter for HA partition will fail if management portset feature is not supported in the remote system.
-nomanagementportset
(Optional) Specifies the removal of the management portset assignment from the partition.
Note: The -managementportset and -nomanagementportset parameters are mutually exclusive with the following parameters:
  • -preferredmanagementsystem
  • -makedrlink
  • -removedrlink
  • -replicationpolicy
  • -noreplicationpolicy
partition_name | partition_id | partition_uuid
(Optional) Specifies the name or ID or the universally unique identifier of the partition. When this parameter is used, a detailed view of the storage partition is displayed. If this parameter is omitted, a concise view of all storage partitions is displayed.

Description

This command modifies the attributes of a storage partition.

Note: This command is available during the upgrade process.
When using the partition IP address to run this command, consider the following:
  • 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.

Invocation examples

  • The following examples migrates a storage partition to a remote location system by using the locationuuid.
    chpartition -locationuuid <remote_grid_system_uuid> mypartition1
    

    The resulting output:

    No Feedback
  • The following examples migrates a storage partition to a target location system.
    chpartition -location myTargetFlashSystem mypartition1  

    The resulting output:

    No Feedback
  • The following example changes the preferred management system for a storage partition.
    chpartition -preferredmanagementsystem myTargetFlashSystem mypartition1 

    The resulting output:

    No Feedback