VPLEX: How to move one leg of a logging volume
Zusammenfassung: This article explains how to move one leg of logging volume from one array to another. This is done by detaching one of the existing legs and attaching the new leg from the new location. ...
Weisungen
This article explains how to move one leg of the logging volume to a different array for better redundancy, or for migrations requirements.
Use Case: This is usually required during storage array migrations, and tech refresh where you must also migrate the logging volume Mirrors.
First you must create a new storage volume on the new target array.
Notes:
- The size of the new storage volume must be the same size or larger than the size of the old component (leg) of the logging volume you want to move.
- By default, the logging volume consists of components. These components are storage volumes that could be provisioned from the same array, or two different arrays.
Procedure to move just one leg of the logging volume to another array:
- Identify the logging volume:
VPlexcli:/clusters/cluster-1/system-volumes> ll
Name Volume Type Operational Health Active Ready Geometry Component Block Block Capacity Slots
------------------------------ -------------- Status State ------ ----- -------- Count Count Size -------- -----
------------------------------ -------------- ----------- ------ ------ ----- -------- --------- -------- ----- -------- -----
Cluster1_logvol1_vol logging-volume ok ok - - raid-1 2 2621440 4K 10G -
c1meta meta-volume ok ok true true raid-1 2 26214144 4K 100G 64000
c1meta_backup_Nov02_230017 meta-volume ok ok false true raid-1 1 26214144 4K 100G 64000
c1meta_backup_Nov03_230022 meta-volume ok ok false true raid-1 1 26214144 4K 100G 6400
- List the logging volume components (legs) using the
"show-use-hierarchy"CLI command:
logging-volume: Cluster1_logvol1_vol (10G, raid-1, cluster-1)
extent: extent_Cluster1_logvol_1_1 (10G)
storage-volume: Cluster1_logvol_1 (10G)
logical-unit: VPD83T3:600601600xxxxxxxxxxxxxe2ee58e
storage-array: EMC-CLARiiON-CKMXXXXXXXX208
extent: extent_R_Rental_VPLEX1_Logging_Crossconnect_1 (10G)
storage-volume: R_Rental_VPLEX1_Logging_Crossconnect (40G)
logical-unit: VPD83T3:600601xxxxxxxxxxxxx6380cc8
storage-array: EMC-CLARiiON-CKMXXXXXXXX247
- Specify the Slot Number of the mirror leg to detach, or use the name of the leg that is to be detached, and use the
--mirror flagwith the"logging-volume detach-mirror"command:
Name Slot Type Operational Health Capacity
----------------------------------------------------- --------------------- Number -------- Status State
----------------------------------------------------- ------- ------ ----------------- -------
extent_Cluster1_logvol_1_1 0 extent ok ok 10G
extent_R_Rental_VPLEX1_Logging_Crossconnect_1 1 extent ok ok 10G
- Detach the leg of the logging volume that is to be moved to a different array:
VPlexcli:/clusters/cluster-1/system-volumes> logging-volume detach-mirror --logging-volume Cluster1_logvol1_vol/ --slot 0 - Add a new mirror (leg) from the different array to the logging volume:
- Monitor the rebuild status:
When the new leg has been attached to the logging volume a rebuild takes place. You can monitor the rebuild status so you know when the rebuild is complete using the"rebuild status"command:
For more information about commands and examples see the VPLEX CLI Reference Guide for the GeoSynchrony version running on the VPLEX.
Weitere Informationen
The procedure discussed in this article does not move the total logging volume. If you would like to move the total logging volume, refer to KB article VPLEX: How to Move an entire logging volume.
There is also a procedure from SolVe Desktop/Online for migrating data from old array to new array:
VPLEX > Administration > Manage >
By default, the logging volume consists of components. These components are storage volumes that could be provisioned from the same array, or two different arrays.
For redundancy Dell Technologies recommends storing the logging volume components on two different backend arrays. This way should one array that a leg is on have issues the leg on the other array is still available.
You might need to migrate data from one of the storage arrays to another array. In that case, you do not have to totally move the logging volume. You can follow the above procedure to move the attached leg under one storage array to another storage array, while keeping the second leg attached to its own storage array.