This post is more than 5 years old
4 Posts
0
2581
Migration of Consistency Group members?
We presently have a VPLEX Metro running and presenting storage to WSFC (Oracle cluster). Runs great. We are in a situation where we need to migrate the backend LUNs to another storage array, and wanted to leverage the capabilities of VPLEX to do so. During research, I came to determine that any devices/extents being used in Consistency Group (CG, which we use) must be removed prior to such migrations. So my questions...
1.) What is the impact of access to data in removing a Virtual Volume from a CG?
2.) What are the impacts of replication and synchronization when removing a Virtual Volume from a CG?
3.) I presume that the volume(s) have to remain out of the CG until the migration is completed, and then placed back into the CG?
4.) Any best practices/guidelines in doing this? (destroy the consistency group, migrate all devices, then rebuild it?, or do one device at a time?)
Any insight would be most appreciative.
Products
11 Posts
0
February 26th, 2018 09:00
Hi Kenneth -
To answer you questions,
1] What is the impact of access to data in removing a Virtual Volume from a CG?
There is no impact to the virtual volume, the data can be copied non-disruptively
2] What are the impacts of replication and synchronization when removing a Virtual Volume from a CG?
There is no impact, the physical data relocation is preformed by VPLEX transparently and the virtual volume
retains the same identities and the same access points to the host. VPLEX copies the data from the old array
to the new array while the host continues its access to the virtual volume without disruption.
3] I presume that the volume(s) have to remain out of the CGs until the migration is completed, and then place back
into the CG?
Correct.
4] Any best practice/guidelines in doing this? ( destroy the consistency group. migrate all devices, then rebuild it?
or do one device at a time?)
Please refer to "VPLEX Data Mobility and Migration: Implementing Planning and Best Practices" which can be found
on Online Support, https://support.emc.com/docu58230_VPLEX-Data-Mobility-and-Migrations:-Implementation-Planning-and-Best-Practices.pdf?languages=en_US. There is also some info in the VPLEX Administration Guide, also available on support online, look for the version for the code running on the VPLEX. And the CLI Guide will provide details of the commands to be used. There is also the procedure, "Migrate data from old array to new array" available from the SolVe Desktop procedure generator app, VPLEX > VPLEX Procedures > Administration procedures > Manage
kenneth.schall.talgov.com
4 Posts
0
February 26th, 2018 09:00
Thank you for that information. Based on that, I should have no concerns with removing a device/extent from a CG while doing this? I'm more worried about a fail-over if the device is not in the CG - should I have any concerns with this? While looking up the procedures on solVe (which I completely forgot about
), I found they now have an online version of solVe. I have the procedure you mentioned now and will review prior to any changes, as well as review of the Admin guide. I've had the CLI guide for a while, but it's not exactly "light reading". Also reviewing the best practices guide for additional info.
Thanks again!!
Products
11 Posts
1
February 27th, 2018 09:00
The best practice guide does a good job explaining what happens during a migration so you will be okay based on how the migration works to protect your data. Review the Overview section where it talks to "How Data Mobility Works".