Morrorview /S manual recovery

so you would zone but not present any LUNs ? As you know MirrorView target LUNs are in "read-only" mode when MirrorView is syncing and also when it's fractured.  To make them truly read-write you will need to promote them or fracture/delete secondary.

take a look at the Techbook

https://www.emc.com/collateral/hardware/technical-documentation/h8229-vnx-vmware-tb.pdf

I think it would be no problem also to present the secondary LUNs to the Hosts. As you say they are in read-only and have probably different names. And yes I know, only after promote i can deal with them.

What I want to know is, after the promote action, do i have to reregister the VMs on the secondary(now primary) LUNs?

The best way to test the behaviors of the mirrored LUNs in your environment would be to clone or snapshot them.

That way, you don't have to fracture the synhcronisation before you can test a read/write LUN, this can be done while syncing.

Didi wrote: What I want to know is, after the promote action, do i have to reregister the VMs on the secondary(now primary) LUNs?

yes, I believe SRM does that for you but since you are doing it manually you will need to register them in vCenter.

Rainer,

you mean this section of the document(Page 209)?

4. Right-click a consistency group and select Synchronize to synchronize all LUNs as

MirrorView LUN synchronization performs the following changes:

• Sets the primary images on the production site to write-disabled.
• Reverses the mirror relationship of the devices. The devices at the remote site assume the primary role and are set to write-enabled.
• Resumes the MirrorView link to allow updates to flow from the remote data center to the production data center.
• Registers and powers on the virtual machine from the vSphere client or command line utilities.

I'm a little bit confused about the last point. Can not imagine that the process does it automatically.

Regards

Didi