Dell PowerVault MD3260i - Manual (Page 228)

NOTE: Formatting a virtual disk starts a long-running operation that cannot be stopped.
Syntax
start virtualDisk [virtualDiskName] initialize
[existingRepositoryLabel = existingRepositoryName] |
[diskPoolUserLabel="diskPoolName"
[retainRepositoryMembers = [TRUE|FALSE]]
Parameters
Parameter Description
virtualDisk The name of the virtual disk for which you are starting the
formatting. Enclose the virtual disk name in square
brackets ([ ]). If the virtual disk name has special
characters, you also must enclose the virtual disk name in
double quotation marks (" ").
existingRepositoryLabel Causes the repository virtual disk to be replaced by the
candidate virtual disk specified.
• The value specified is an existing repository
virtual disk user label. The virtual disk specified
must be an unused repository virtual disk with the
name in the proper form.
• If the newly specified repository virtual disk is on
a different disk pool, the thin virtual disk will
change ownership to that pool.
• The old repository virtual disk will be deleted by
default.
diskPoolUserLabel Use this parameter to allocate a new repository virtual
disk with the specified capacity.
retainRepositoryMember If this parameter is set to TRUE, the old repository is
retained. By default, the old repository is deleted. This
parameter is ignored if the existing repository is reused.
Remove Incomplete Remote Replicated Pair From Remote
Replication Group
Description
This command removes an orphaned replicated pair virtual disk on the storage array. An orphaned replicated pair virtual
disk exists when a member virtual disk in a remote replication group has been removed on one side of the remote
replication group (either the primary side or secondary side) but not on the other side.
Orphan replicated pair virtual disks are detected when inter-RAID controller module communication is restored and the
two sides of the replication configuration reconcile replication parameters.
Use this command when the replicate relationship is successfully removed on the local or remote storage array, but
cannot be removed on the corresponding storage array because of a communication problem.
228