Hi TMeissner,

This looks like an SRA problem during test failover. Looking at the SRA log it seems that the operation was successfull, however the response indicated an error.

<?xml version="1.0" encoding="UTF-8"?>
<Response>
<ReturnCode>4</ReturnCode>
</Response>

...

(2008-10-07 10:45:06) .\cli\sraTestFailover.cpp:302::TRIVIA::SMsra::TestFailover::performOp::Calling tfoStart
(2008-10-07 10:45:06) .\cli\sraTestFailover.cpp:355::TRIVIA::SMsra::TestFailover::toStart::Entry
(2008-10-07 10:45:06) .\cli\sraTestFailover.cpp:1170::VERBOSE::SMsra::TestFailover::getVolumeWithWWN::Got Volume with WWN 600a0b800042359600000c5848ce720f
(2008-10-07 10:45:06) .\cli\sraTestFailover.cpp:386::VERBOSE::SMsra::TestFailover::toStart::Got Volume
(2008-10-07 10:45:06) .\cli\sraTestFailover.cpp:401::VERBOSE::SMsra::TestFailover::toStart::Volume status is Optimal
(2008-10-07 10:45:06) .\cli\sraTestFailover.cpp:411::VERBOSE::SMsra::TestFailover::toStart::Snapshot for Volume not present, Creating Snapshot
(2008-10-07 10:45:06) .\cli\sraTestFailover.cpp:1507::VERBOSE::SMsra::Next Snapshot Count=0
bindToController succesfull
Current CGN=4115
2008-10-07:: 10:45:12:INFO:failover:exit failover.....

-Masha

Hi Brett,

required. Does any one know if this is the minimum or supported version
levels?

Safe assumption would be that only the exact versions are supported. However, in most cases all higher versions are supported as well. It would be best to consult the vendor of the SRA about your particular version.

-Masha

I'm in the process of installing SRM on a DS4800 (1 on each site). I have got the hotfix for Update 1, and it states:

*The
VMkernel build number MUST BE equal to 82663, otherwise, the hot patch cannot
be installed*

my output is:
root@dzmesx005 root# rpm -qa | grep vmkernel
VMware-esx-vmkernel-3.5.0-113339

This means i can't install the patch at the moment, or i'll have to downgrade all my ESX server to Update 1 (build 82663).

The problem i have is that the array manager gives the error message: ERROR OCCURED.

When i look at the logging i see the following error (highlighted the section with the error)

2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 info Command Line for discoverArrays: "D:\VMware\VMware Site Recovery Manager\external\perl-5.8.8\bin\perl.exe" "D:/VMware/VMware Site Recovery Manager/scripts/SAN/IBM/command.pl"
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 verbose Input for discoverArrays: <?xml version="1.0" encoding="UTF-8"?>
1 <Command>
1 <Name>discoverArrays</Name>
1 <ConnectSpec>
1 <Name>DS4800</Name>
1 <Address>225.255.255.255</Address>
1 <Address>225.255.255.255</Address>
1 </ConnectSpec>
1 <OutputFile>C:\WINDOWS\TEMP\vmware-SYSTEM\dr-sanprovider0</OutputFile>
1 <LogLevel>trivia</LogLevel>
1 </Command>
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment ALLUSERSPROFILE=C:\Documents and Settings\All Users will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment ClusterLog=C:\WINDOWS\Cluster\cluster.log will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment CommonProgramFiles=C:\Program Files\Common Files will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment COMPUTERNAME=DZMVC001 will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment ComSpec=C:\WINDOWS\system32\cmd.exe will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment FP_NO_HOST_CHECK=NO will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment NUMBER_OF_PROCESSORS=1 will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment OS=Windows_NT will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;D:\VMware\VMware Site Recovery Manager\scripts\SAN\IBM will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment PROCESSOR_ARCHITECTURE=x86 will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 8, GenuineIntel will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment PROCESSOR_LEVEL=15 will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment PROCESSOR_REVISION=0408 will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment ProgramFiles=C:\Program Files will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment SystemDrive=C: will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment SystemRoot=C:\WINDOWS will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment TEMP=C:\WINDOWS\TEMP will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment TMP=C:\WINDOWS\TEMP will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment USERPROFILE=C:\Documents and Settings\Default User will be set for the script
2008-10-31 14:19:51.387 'PrimarySanProvider' 2300 trivia Environment windir=C:\WINDOWS will be set for the script
2008-10-31 14:19:51.387 'SysCommandLineWin32' 2300 verbose Starting process: "D:\\VMware
VMware Site Recovery Manager\\external\\perl-5.8.8\\bin
perl.exe" "D:/VMware/VMware Site Recovery Manager/scripts/SAN/IBM/command.pl"
2008-10-31 14:19:51.606 'PrimarySanProvider' 2300 info discoverArrays exited with exit code 0
2008-10-31 14:19:51.606 'PrimarySanProvider' 2300 trivia discoverArrays's output:
D:/VMware/VMware Site Recovery Manager/scripts/SAN/IBM2008-10-31:: 14:19:51:INFO:discoverArray:call the discoverArray.pl file.....
1 2008-10-31:: 14:19:51:INFO:discoverArray:exit discoverArrays.....

2008-10-31 14:19:51.606 'PrimarySanProvider' 2300 error discoverArrays's errors:
'perl' is not recognized as an internal or external command,
1 operable program or batch file.

2008-10-31 14:19:51.606 'PrimarySanProvider' 2300 trivia 'discoverArrays' returned
2008-10-31 14:19:51.606 'PrimarySanProvider' 2300 error Failed to retrieve script results
2008-10-31 14:19:51.606 'ArrayManagerImpl.QueryInfoTask-Task' 2300 info Work function threw std::exception: XML document is empty
2008-10-31 14:19:51.606 'ArrayManagerImpl.QueryInfoTask-Task' 2300 info Fault:
(dr.fault.InternalError) {
1 dynamicType = <unset>,
1 reason = "XML document is empty",
1 msg = ""
1 }
2008-10-31 14:19:51.606 'ArrayManagerImpl.QueryInfoTask-Task' 2300 verbose Error set to (dr.fault.InternalError) {
1 dynamicType = <unset>,
1 reason = "XML document is empty",
1 msg = ""
1 }

Has anyone have the same issue's, and is the solution downgrading to ESX 3.5 update 1 ?

Thx

Sarek

Hello,

Your firmware is down level and will not work with the SRA. One thing that can be confusing is that there are two different version numbers used with the IBM DS. One is for their management software which will be version 10.10.xx.xx and the other is for the firmware in the array which would be 7.10.xx.xx. You indicate that your array is running version 6.60.xx.xx firmware and that is downlevel from the 7.10.xx.xx release and in fact the 7.10 release was a major upgrade in the firmware with a lot of enchancements and changes such as removing the 2TB volume size limit. The upgraded firmware is avaliable but be aware that you have to take the array offline to do this upgrade unlike other previous upgrades and that if you do upgrade you can not go back without having to restore your data from backup.

Bob

From the storage configuration perspective, you'll want to ensure you have flashcopy and ERM enable on both the protected and recovery site DS4700 subsystems.( assuming you want to test failback in both directions or at least have flashcopy enabled on the recovery side subsystem) You'll want to go ahead and activate ERM and configure the logical drives that you want to mirror with StorageManager for the protected site subsystem to the recovery site subsystem.( I'm assuming the physical communication for the subystems has already been configured, if you're working within a local test configuration, go ahead and make sure you have have the two subsytems communicating via a fabric through its mirroring ports ). You'll want the mirroring relationship established before proceeding with the rest of SRM configuration. The logical drives that are in the mirror relationship at the recovery side should already be mapped as well. This is probably a good time to point out that you want to have your mapping and partitioning layout configured via StorageManger for the protected/recovery side subsytems. I went ahead and manually scanned for all of the LUNs that I expected to be registered by the recovery side ESX hosts to make sure all LUNs were correctly seen and also that my multipathing design worked as I intended in regards to the number of paths available to my recovery side subsystem. The multipath considerations is often overlooked so make sure you see the LUNs as expected, number of paths as expected and so forth. DS4000/5000 multipathing behavior under the current VMware failover code probrably deserves its own thread, but multipathing design is a critical consideraton of your BC/DR planning with SRM and DS4/5K line subsystems. Once you get furthur into SRM configuration, it'll become more clear as to what SRM sees from it's perspective. The reason you need flashcopy enabled on the subsystem is if you run a test of your recovery plan later. The SRM server on the recovery side via its SRA adapter will initiate a flashcopy of your mirrored logical drives and it's the flashcopy that is presented to the recovery side ESX servers. Note that the recovery side logical drives in the mirror relationship is read only until they are promoted, but during the testing of your recovery plan you want a READ/WRITABLE logical drive for ESX to register. In short, configure mirroring, mapping/partition layout, and multipathing design as desired for the DS4700 first then proceed with the rest of SRM/SRA pre and post configuration. If you administer both the ESX and storage layers then its straight forward, but if you're in a large enterprise with a different storage group and possibly SAN/NETWORK group, you'll want to coordinate with these guys as well. Just from my own personal insight, the lack of communication can really cause problems in the design of your SRM strategy. Hope some of this helps.