Posted by: MikeLaverick
when relevant content is
added and updated.
Editors Note: This is part two of a two-part series on VMware Site Recovery Manager (SRM). If you’re just joining us, please take a minute to read part one, which goes over the basics of VMware Site Recovery Manager and what resignaturing is.
In normal day-to-day operations an ESX host in the protected site should not get to see both the original LUN and replicated LUN/snapshot at the same time. If it did, ESX would suppress the second LUN/volume. If an ESX host was allowed to see both LUNs/volumes at the same time, ESX would be very confused and not at all happy. It wouldn’t know which LUN/volume to send its reads and writes to. In ESX 3.5, the host would print a hard console error message, suggesting you may need to do a resignature of the VMFS volume.