Yes, in that case you would promote the secondary image and add it to the storage group with the DR host. Then rescan and follow ksp's procedure:   ksp wrote:  3. ESX still won't automatically mount this new primary volume right away, because it is on a different storage and has different address, and it gets detected as a snapshot. Now you have to: a) Make sure that the original Vol1 isn't and won't be accessible to ESX during the DR. It's ok if it is secondary now, or you have to disable access to it by other means. b) Mount the new primary volume Vol2 using either resignature or temporary mount -- choose which is more appropriate for your situation: [URL] We use temporary mount with esxcfg-volume -m in our tests, because we put everything back shortly after. (Caution: there was a bad experience with persistent mount esxcfg-volume -M, we had to reboot all ESX hosts to get the volume back, just a heads-up for you)
Hi,  I am in process of setting up DR for 1 server using remote mirror using mirror view.I have setup the remote mirror in async mode.2 LUNs are consistent now and 2 are in synchronizing mode.  Now I have to present the DR LUNs to ESX servers.But the ESX admin saying that when they create datastore,the LUN will get formatted.So i want to know how can i proceed fro here.  my thought is  1. fracture the seconday mirror 2.present the LUn to DR server 3.Once the datastore has been created and can synchronize it   can somebody tell this the correct ptocedure.I didnt do the these procedure before.and if there is any update to DR mirror(secondary),will that get copied to primary mirror   Thanks in advance  its a CX4 120
Question regarding Remote Mirror setup