As for the "ReturnCode" error .... v1.00.35.03 of the SRA for the DS4700 has an error. In the command.pl and the command.pm files there is string value, $XML_RETURNCODE = "Returncode"; This needs to be changed to "ReturnCode" with a captial C. I made the change to the script and it fixed the XML error that I was getting. I am assuming that the SRA version will be updated on the VMware site.

Now my next error in the logs are that there is an invalid snapshot of the volume. I am assuming that this is really a flashcopy issue. We are working with IBM to get the proper Flashcopy feature code activation on the recovery side DS-4700.

Using IBM DS4000/FastT Storage Manager, you can define Host Groups to quickly map the VMFS LUNS to a group of ESX servers at the same time. When a LUN is mapped to a Host group up can assign the LUN ID from 0 to xxx. If you map a LUN to an individual server you can also assign the LUN IS from 0 to xxx. The problem comes when the are identical LUN IDs used between a Host Group mapping and individual hosts. The Storage Manager application allows this and somehow can tell the difference between Host Group and an individual host. I think the SRA requests the host mappings and sees two mappings that use the same LUN IDs. It is not aware that one of those ID's is a part of a Host Group.

My workaround was to change the LUN Id's for the DS4700 to insure they were unique. After making the change we no longer received the Duplicate ID's error.

Thanks

#1] 2008-10-07:: 10:45:12:INFO:failover:exit failover.....
1
1 Error:
1
1 ",
1 msg = "Message exceeds database maximum string length."
1 }
1] ,
1 msg = "Message exceeds database maximum string length."
1 }
2008-10-07 10:45:26.071 'Cancel-RecoveryContext-16-17-Task' 3848 verbose Task destroyed

I've attached our log for the error. Any insight would be appreciated. If you think this is a bug in the SRA code ... that OK, just let me know. I'm getting tired of chasing this one. Is there any other information that would be helpful?