Selects an inbound replica set stored in the group and clones a replica from that set, creating a new volume.
Cloning a replica creates a new volume with a different iSCSI target name, but the same size and thin-provision settings (if applicable) as the original volume. The new volume will contain the volume contents that existed when the replica was created and will be available immediately through the IP address of the secondary group (not the primary group, where the original volume resides). You can use and modify the new volume as you would any other volume.
By default, the new volume will be set online, have read-write permission, and use the group-wide snapshot space and iSCSI settings, unless you override them. You can specify the storage pool in which the new volume will reside.
You can clone only complete replicas.Cloning a replica does not have any effect on the replica, which continues to exist after being cloned, or replication activity.
Cloning a replica consumes 100% of the original volume size from free secondary group pool space. If you want to create snapshots or replicas of the new volume, additional space is needed.
You can display the names of the replicas in a replica set as follows:
partner select partner_name inbound-replicaset select set_name show
Format
partner select partner_name inbound-replicaset select set_name clone replica_name new_vol_name [parameter...]
Variables
|
partner_name |
Group name of a partner. |
|
set_name |
Name of an inbound replica set. |
|
replica_name |
Name of a replica. |
|
new_vol_name |
Name of new volume. |
Parameters
|
description text |
Description for the new volume. If the text variable contains spaces, surround it with quotation marks. |
|
read-write|read-only |
New volume permission (default is read-write). |
|
offline|online |
New volume status (default is online). |
|
snap-reserve n% |
Amount of space, as a percentage of the new volume size, to reserve for snapshots. You must include the percent sign. The default is the group-wide setting, as described in grpparams def-snap-reserve . |
|
snap-warn n% |
Threshold at which an alarm is generated because the amount of free space reserved for snapshots of the new volume has fallen below this value, as a percentage of the total reserved snapshot space. You must include the percent sign. The default is the group-wide setting, as described in grpparams def-snap-warn . |
|
snap-depletion action |
Action to take when the new volume’s snapshot reserve is exceeded, either delete-oldest (delete the oldest snapshots, the default) or volume-offline (set the volume and its snapshots offline). The default is the group-wide setting, as described in grpparams def-snap-depletion . |
|
iscsi-alias alias_name |
iSCSI target alias, up to 64 alphanumeric characters, for the new volume. Some iSCSI initiators can see the alias. The default is the group-wide setting, as described in grpparams def-iscsi-alias. |
|
unrestricted |
Allows unrestricted host access to the new volume. Unrestricted access is not recommended. Instead, after cloning the replica, you should create one or more access control records to restrict host access to the new volume. |
|
bind member_name |
Binds the new volume to the specified member. Volume data will be restricted to this member. Binding a volume to a member will override any RAID preference and will disable performance load balancing for the volume. |
|
pool pool_name |
Pool in which to place the new volume. |
Example
The following command clones an inbound replica and creates a volume named v1-clone:
> partner select psgroup11 inbound-replicaset select v1.1 clone v1.1-2006-01-26-11:19:27.15 v1-clone
Cloning is in progress. Successfully created volume 'v1-clone'