SRM - NETAPP - Problem with Process FailBack

[AndreasKunz]

Hi,

I have two storage NETAPP environnement FAS3020 and FAS2050 with DATA ONTAPP 7.3 and 7.3.1.

Storage source is FAS3020 with 3 ESX VI3.5U4

Storage recovery is FAS2050 with 2 ESX VI3.5U4

When I take the "Recovery Test" and "Recovery Plan (RUN)", All is correct ! Perfect Solution !

But when I want take a FAILBACK process, I have a problem with the SRA. In Fact, I my NETAPP environnement, my ESX server have 2 groupe Initiator (One for BootSan and One for present LUN-DATASTORE).

the error process is a SRA BUG !

Error: Non-fatal error information reported during execution of array integration script: testFailover Output: Starting script Test-Failover-start Collecting igroup information igroup ESX17 has initiator 2100001b321b2573 and type FC igroup ESX17 has initiator 2100001b321bd86e and type FC igroup ESX16 has initiator 2100001b321b957d and type FC igroup ESX16 has initiator 2100001b321b5172 and type FC igroup ESX15 has initiator 2100001b321b2571 and type FC igroup ESX15 has initiator 2100001b321b537c and type FC igroup VMMWARE_Cluster has initiator 2100001b321b2571 and type FC igroup VMMWARE_Cluster has initiator 2100001b321b957d and type FC igroup VMMWARE_Cluster has initiator 2100001b321b2573 and type FC igroup VMMWARE_Cluster has initiator 2100001b321b537c and type FC igroup VMMWARE_Cluster has initiator 2100001b321b5172 and type FC igroup VMMWARE_Cluster has initiator 2100001b321bd86e and type FC skipping igroup VMMWARE_Cluster since its ostype is not vmware Checking existence of Lun /vol/VOLPROD_PRA1/LUNTESTPRA1 Lun /vol/VOLPROD_PRA1/LUNTESTPRA1 exists Creating test Clone volume testfailoverClone_nss_v10745371_VOLPROD_PRA1 Mapping Lun /vol/testfailoverClone_nss_v10745371_VOLPROD_PRA1/LUNTESTPRA1 Mapped Lun /vol/testfailoverClone_nss_v10745371_VOLPROD_PRA1/LUNTESTPRA1 to ESX16 Mapped Lun /vol/testfailoverClone_nss_v10745371_VOLPROD_PRA1/LUNTESTPRA1 to VMMWARE_Cluster Mapped Lun /vol/testfailoverClone_nss_v10745371_VOLPROD_PRA1/LUNTESTPRA1 to ESX15 Mapped Lun /vol/testfailoverClone_nss_v10745371_VOLPROD_PRA1/LUNTESTPRA1 to ESX17 Onlining Lun /vol/testfailoverClone_nss_v10745371_VOLPROD_PRA1/LUNTESTPRA1 LUN already mapped to initiator(s) in this group Onlining Lun /vol/testfailoverClone_nss_v10745371_VOLPROD_PRA1/LUNTESTPRA1 failed Test-Failover-start completed with errors Generate EMS event in filer Generating EMS event in filer succeeded Error: .

But I don't change my presentation, i have 50 LUN !

Please Help me for this problem.

thank's, Andréas (VCP with significant experience SRM).

I have see two post with the similar problem :

http://communities.vmware.com/thread/225803

http://communities.vmware.com/thread/197159

thank's

[luisarnauth]

Perhaps not much help but:

1. Try inverting the DR scenario with a small LUN and VM, ie, since the DR site has different storage than the protected site, this way you can (rapidly) the replication process between DR and protected site.

2. Second, in my present scenario, EMC Clariion with MirrorView/A, I must create a snapshot for each protected LUN on the DR site for failover. If I wanted to failback via SRM I should have a snapshot for each DR LUN in the protected site. I'm not sure if this is the configuration for NetApp.

Hope it helps

[EddieH3]

I have been working heavily with SRM and testing it out in our lab for the past 4 months, but I haven't got to the failback testing yet. The only input I can add here is to check your licensing. The protection‐enablement license key (SRM_PROTECTED_HOST) will need to be purchased or transfered from the recovery site to the protected site for failback.

This is from page 70 of the SRM Admin Guide 1.0.1

NOTE If you have not purchased a protection‐enablement license key (SRM_PROTECTED_HOST) for the protected site, you must transfer that key from the recovery site to the protected site before you can run a failback. For more information, see "SRM Licensing" on page 24

Also might want to open a support case with NetApp.

Hope this helps

[AndreasKunz]

Hi,

Thank you for your responses.
I isolated the
problem and it becomes from the iSCSI initiator.

It's not a license problem or other problem.

I call NetApp and the respons is "just one a initiator IQN per Host".....It's not easy when you are a BootSan....

thank's.