Unsolved
This post is more than 5 years old
10 Posts
0
5788
June 10th, 2014 02:00
how to migrate data thru VPLEX by setting up mirror between source and target array?
how to migrate data from VMAX to VNX using VPLEX by setting up a mirror between source array (VMAX) and target array (VNX). After one week we need to detach the source array (VMAX). This would be the cutover for our migration.
No Events found!
Andrew-F
27 Posts
0
July 2nd, 2014 09:00
During the entire process the virtual volume remains the same. The host sees the same virtual volume and mostly is unaware of any changes happening underneath.
The reason I say mostly is because if and when a virtual volume name is changed, VPLEX will send a unit attention to the host that a SCSI field has changed. It should not impact the host access in any way, but some people have noted the unit attention when filtering host logs. This only happens if the virtual volume name is changed from the default name.
Anonymous User
67 Posts
0
July 2nd, 2014 09:00
Hello kannan,
After committing, both the source and target devices will be visible, with the target device being associated with the virtual volume that is presented to the host (If you've presented it to a host).
After you commit, perform a "clean" operation. This would dismantle the source device down to the storage volume and the source storage device will change to an unclaimed state. (ll /clusters/**/storage-volumes)
Also, use the rename option when you clean, which will cause the target volume to assume the name of the source volume. [esp if you've given the source virtual volume, a meaningful name like "host1_db_logvol1" .. ]
(batch-migrate clean –-rename-targets /tmp/batchMig_file). The migration target device will assume the name of the source device and will associate itself with the encapsulated virtual volume. Also, the source device will be removed.
(ll /clusters/**/devices)
regards.
wiproo
10 Posts
0
July 3rd, 2014 05:00
Hi Steve,
I am sorry your statement is slightly confusing me.
I am under the impression that during encapsulation i will have VV created with the source device and presented to storage view and my applications are up and running. At the target side, i will have to create till device in vplex and start the migration using source and target device (both vplex device). At the end of the migration i will commit and cleanup the migration.
So where am i creating the second VV for the migration? and why should i create second VV for the migration?
Thanks
Kannadasan
Intech1
57 Posts
0
July 3rd, 2014 05:00
Yes you must create a VV but this doesn't mean you must put the VV in a storage View.
Steve
Sent from my iPad
Intech1
57 Posts
0
July 3rd, 2014 06:00
It was I who misunderstood. You are correct.
Steve
Sent from my iPad
Andrew-F
27 Posts
0
July 3rd, 2014 06:00
Hi,
There should only be one VV and it may be presented to a host during the mobility job. For an explanation of the process, I would recommend looking at this 2013 EMC World presentation particularly slides 21-30. https://www.emcworldonline.com/2013/connect/fileDownload/session/AC3C379311BD4BE91BA5425C2702BED8/esd.01_Gallagher-ESD.0…
Thanks,
Andrew
wiproo
10 Posts
0
July 3rd, 2014 06:00
Thanks Steve.
Now the migration process is completely clear to me.
If any doubt arises, i will put up the questions in the same thread.
Hopefully we will start migration by next week.
Thanks
Kannadasan
snalluri
1 Rookie
•
28 Posts
0
August 5th, 2014 18:00
Steve- Is there any difference between extent level migration and device level migration ?
Intech1
57 Posts
0
August 6th, 2014 05:00
No
Steve
Sent from my iPad