10.5 HP StoreVirtual Storage User Guide (AX696-96269, March 2013)

iSCSI sessions and volume migration
iSCSI sessions are rebalanced during volume migration. While data is being migrated the volume
is still accessible and fully functional. The rebalancing affects systems using the DSM for MPIO
differently than systems that are not using the DSM for MPIO.
• Using DSM for MPIO—Administrative sessions are rebalanced to the new cluster immediately
upon volume migration. DSM sessions go into an unknown/failed state and are then
re-established on the second cluster within a short period of time.
• No DSM for MPIO—iSCSI session is rebalanced to the new cluster immediately on volume
migration.
As soon as possible after beginning the migration, the iSCSI initiators configured to access this
volume must be re-configured to connect to the VIP of the new cluster. Most initiators require you
to disconnect the volume, re-configure the initiator to use the new cluster VIP as a target address,
and then connect to the volume again. Since this volume is disconnected, administrators should
schedule a maintenance window for the re-configuration of the initiator.
NOTE: Moving the volume to a different cluster requires restriping the data in both clusters.
Restriping can take hours, or even days.
To change the cluster—migrate the volume
1. On the Edit Volume window, click the Advanced tab.
2. In the Cluster list, select a different cluster.
3. Click OK.
Changing the data protection level
1. In the Data Protection Level list, select the level of Network RAID you want.
Changing a volume to either Network RAID-5 or Network RAID-6 requires that volume to have
a snapshot schedule. If the volume does not already have a snapshot schedule related to it,
one will be created automatically. This default schedule is named VolumeName_Schedule,
recurs once daily, and retains 1 copy. You can edit this schedule as desired, as described in
“Editing scheduled snapshots” (page 172).
2. Click OK when you are finished.
Changing the size
1. In the Size field, change the number and change the units if necessary.
2. Click OK when you are finished.
CAUTION: Decreasing the volume size is not recommended. If you shrink the volume in the CMC
before shrinking it from the server file system, your data will be corrupted or lost.
Deleting a volume
Delete a volume to remove that volume’s data from the storage system and make that space
available. Deleting a volume also deletes all the snapshots underneath that volume, except for
clone points and shared snapshots. For more information, see “Clone point” (page 190) and “Shared
snapshot ” (page 192).
CAUTION: Deleting a volume permanently removes that volume’s data from the storage system.
Deleting a volume 163