Why not use VPlex's mobility functionality?

Sent from my iPhone

Client would like to keep the data in both source and target for one week and then discard source.  Data mobility, i think, would move the data immediately to the target and not keep in source.

Thanks

Wiproo

Just don't commit. Once the mobility job is established and they are 100% in sync your maintaining your mirrors until broken when you run the commit command (graphical or CLI). IO will continue to go to both devices. Once your customer is comfortable, after a week commit jobs or you could cancel the job(s) and maintain the original devices

Sent from my iPhone

Device

That's a good idea.

My setup is Vplex local.  Which migration is best to do extent or device ?

Thanks

Kannadasan

Thanks for your help.

I will keep asking questions till we migrate one server.

Thanks

Wiproo

can we not use a device attach-mirror which would start a transfer for a rebuild?

and after the data is no longer needed, do a detach-mirror.

Yes

Sent from my iPhone

If my device is a RAID -1 mirror, my source leg is VMAX and target is VNX, I need to keep the mirror attached at all time.  I wont be able to detach the mirror in RAID-1 configuration.  How is this possible for RAID-1 device ?

How can i do the cutover ?

Thanks

Kannadasan

And there lies your issue. In VPlex we support 2-leg mirror devices. Mobility is your answer. Remember commit when your customer is ready. Until you commit you are maintaining both source and target devices.

Sent from my iPad