VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
2 Replies Last post: Nov 6, 2009 3:09 PM by ajames  

Error running Recovery Plan - storage prep (IBM n / NetApp) posted: Aug 12, 2009 10:18 AM

Click to view wackjunk's profile Lurker
wackjunk
1 posts since
Aug 12, 2009
Hi, I'm getting an error when I try to test a recovery plan. I get it on any of the datastores I'm trying it on. It's an IBM n5200 (running NetApp OnTap). This worked at one point but there was a crash and after rebuild I get this error. What am I missing? Any help would be appreciated, thanks.

--2009-08-11 09:46:05.215 'SysCommandLineWin32' 3860 verbose-- Starting process: "C:
Program Files\\VMware
VMware Site Recovery Manager\\external\\perl-5.8.8\\bin
perl.exe" "C:/Program Files/VMware/VMware Site Recovery Manager/scripts/SAN/IBM_ONTAP/command.pl"
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 info-- testFailover exited with exit code 0
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 trivia-- testFailover's output:
<Response>
4 Starting script
4 Test-Failover-start
4 Collecting igroup information
4 skipping igroup since its ostype is not vmware
4 skipping igroup since its ostype is not vmware
4 skipping igroup since its ostype is not vmware
4 skipping igroup since its ostype is not vmware
4 skipping igroup since its ostype is not vmware
4 igroup DR_VMWARE has initiator 210000e08b9b300b and type FC
4 igroup DR_VMWARE has initiator 210000e08b9b1c0c and type FC
4 igroup DR_VMWARE has initiator 210000e08b9b330b and type FC
4 Checking existence of Lun /vol/SM_VMWARE_PROD2/Prod_VMFS2
4 Lun /vol/SM_VMWARE_PROD2/Prod_VMFS2 exists
4 Creating test Clone volume testfailoverClone_nss_v10745371_SM_VMWARE_PROD2
4 Mapping Lun /vol/testfailoverClone_nss_v10745371_SM_VMWARE_PROD2/Prod_VMFS2
4 No such LUN exists
4 Mapping Lun /vol/testfailoverClone_nss_v10745371_SM_VMWARE_PROD2/Prod_VMFS2 to DR_VMWARE failed
4 Test-Failover-start completed with errors
4 Generate EMS event in filer
4 Generating EMS event in filer succeeded
4 </Response>
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 trivia-- 'testFailover' returned <?xml version="1.0" encoding="UTF-8"?>
4 <Response>
4 <ReturnCode>4</ReturnCode>
4 </Response>

--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 info-- Return code for testFailover: 4
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 error-- The scripts returned an error, leaving the temporary file 'C:\WINDOWS\TEMP\vmware-SYSTEM\dr-sanprovider0'
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 error-- Unknown error encountered by the script
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 error-- No shadow LUNs found in testFailover/start output
--2009-08-11 09:46:11.090 'SecondarySanProvider' 3860 verbose-- Deleting lun snapshots

Re: Error running Recovery Plan - storage prep (IBM n / NetApp)

1. Aug 18, 2009 10:53 AM in response to: wackjunk
Click to view jbloo2's profile Enthusiast
jbloo2
24 posts since
Mar 26, 2008

Similar issues have been seen on ONTAP 7.3.1 and below and seem to have been fixed in ONTAP 7.3.1.1. The NetApp adapter users their ZAPI to communicate with the array, and there may have been a timing issue that after the adapter creates a clone, information about the clone was not yet available for the next call that tried to map the clone to an initiator group. It may have been the case that when you rebuilt your array you might have installed a version of ONTAP below 7.3.1.1 which is why the problem now manifests itself (and as a timing issue might be intermittent as well). You can get the version of ONTAP by typing "version" at a telnet session of ONTAP.


Re: Error running Recovery Plan - storage prep (IBM n / NetApp)

2. Nov 6, 2009 3:42 PM in response to: jbloo2
Click to view ajames's profile Novice
ajames
7 posts since
May 31, 2005
I am having this exact same problem. NetApp advised me to upgrade to ONTAP 7.3.1.1P9 or greater. I upgraded to 7.3.2 and the problem still persists. It has to be a timing issue, as after 2 or 3 tries it does work.

I have added a delay to the perl script in the sub lunsetspacereservation and it seems to be a valid workaround for now. This is for the sra/ndra v1.4.

my $zapi = "lun-set-space-reservation-info";

sleep 10;

my $out = $server->invoke($zapi, "enable", $reserve, "path", $lun_path);

Adrian

Actions

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities