NetApp Snapmirror and VMFS partitions

NetApp Snapmirror and VMFS partitions

Hi All
I have a client with a peculiar problem that seems to be escaping me

He has a group of ESX boxes on one site, using NetApp storage,  replicated via async SnapMirror to another site where there are another  group of ESX systems

when the mirror is broken and the luns attached to the remote ESX boxes,  the ESX box seems to detect that it's a VMFS partition but says it  needs to reformat it

is this just a signature problem in esx? is there a way around it? I've  got numerous configs like this in production working fine, i've just  never been presented with this problem before

any help appreciated


Hi,

Sounds like a resignature issue, but it should not have shown you the  VMFS partition yet. (You may see it as an empty disk you can use for  extends)

1. In the "Virtual Infrastructure Client" Client on a ESX Server

2. Then click on the "Configuration Tab"

3. In the navigator under the software section select "Advanced Options"

4. Select the LVM node

5. Change LVM.EnableResignature from 0 to 1 to enable resignature

6. Click on OK

7. The on the same configuration screen, under the "Hardware" section click on "Storage (SCSI, SAN and NFS).

8. Top right corner of that screen, click on "refresh"

Now you should see the snapmirrored volume. Make sure the on the the netapp storage snapmirror is "broken-off"(not mirrored).


regards


Just do what shinsterneck wrote. That is the correct answer. We have a  netapp san running snapmirror as well and we experienced the same thing  as you.

The resignature setting solved it.

Frank

This document was generated from the following thread: NetApp Snapmirror and VMFS partitions

Version history
Revision #:
1 of 1
Last update:
‎11-14-2007 06:48 AM
Updated by: