HP StorageWorks P2000 G3 MSA System SMU Reference Guide 115
Detached volumes remain associated with their replication sets but are not updated with replication data
or with replication control information.
NOTE: It is recommended that the vdisk that you are moving contains only secondary volumes and their
snap pools. You are allowed to move other volumes along with secondary volumes and their snap pools,
but be sure that you are doing so intentionally.
NOTE: If you intend to move a vdisk's drive enclosure and you want to allow I/O to continue to the other
enclosures, it is best if it is at the end of the chain of connected enclosures. If the enclosure is in the middle
of the chain, the enclosures must be cabled with no single point of failure, so that removing the enclosure
does not prevent communication between other enclosures.
To detach a secondary volume
1. In the Configuration View panel, right-click the secondary volume and select Provisioning > Detach
Replication Volume.
2. In the main panel, click Detach Replication Volume. A message indicates whether the task succeeded
or failed. When a volume is detached its status is shown as Detached.
Stopping a vdisk
Stopping a vdisk is part of the process for moving a secondary volume into a remote system. The process
to move a secondary volume is:
1. In the primary system:
a. Detach the secondary volume. For details see Detaching a secondary volume on page 114 .
b. If the secondary volume's vdisk contains other secondary volumes, detach those volumes.
c. Stop the secondary volume's vdisk.
d. If the secondary volumes' snap pools are in other vdisks, stop those vdisks.
e. Move the vdisks into the secondary system.
2. In the secondary system:
a. Start the snap pools' vdisks. For details see Starting a vdisk on page 116.
b. Start the secondary volumes' vdisks.
c. Reattach the secondary volumes. For details see Reattaching a secondary volume on page 116 .
Before stopping a vdisk, ensure that all secondary volumes that it contains are detached. When a vdisk is
stopped:
• The volumes in the vdisk become inaccessible to hosts.
• Its cached data is flushed to disk.
• Removing its disks will not cause the system to report errors or to attempt reconstruction.
NOTE: You cannot stop a vdisk that contains a primary volume.
NOTE: If a secondary volume and its snap pool are in different vdisks, you cannot stop the snap pool's
vdisk until you stop the secondary volume's vdisk.