SOAP APIs of SRM 5.8 or 6.0 do not work when query the protected virtual machines in test failover case.

Hi,

I am developing a vSphere Web Client plug-in to talk with SRM (VMware vCenter Site Recovery Manager) 5.8 or 6.0 via its SOAP APIs.

One typical user case is that when end user selects a virtual machine under one vCenter, our plug-in will check the corresponding SRM server and list all Protection Groups for user which are protecting the selected virtual machine.

[Environment]

Protected Site: 10.102.7.78

                Protection Group: srm-protection-group-7484 (PG-VSI), type=san, state=READY

                Protected VM: vm-162 (Yuli_CRR_5.8_CG1_OS) / protected-vm-7543

         Protected VM’s datastore: datastore-161 (snap-5824c9ba-Yuli_CRR_5.8_CG1)           

Recovery Site: 10.102.7.79

                Protection Group: srm-protection-group-7389(PG-VSI), type=san, state=TESTING

                Recovered VM: vm-221 (Yuli_CRR_5.8_CG1_OS) / protected-vm-7426

         Recovered VM’s datastore: datastore-222 (snap-7a7588ae-Yuli_CRR_5.8_CG1)

                Recover Plan: srm-recovery-plan-7500 (RP-VSI)

[Issue]

The issue I encountered is that for a virtual machine (e.g. id is vm-162, name is Yuli_CRR_5.8_CG1_OS) under the protected-site vCenter, our plug-in can find the protection group (e.g. id is srm-protection-group-7484) on the protected-site SRM server if the virtual machine is protected by this protection group. But after doing test fail-over, for the corresponding virtual machine (e.g. id is vm-221, name is Yuli_CRR_5.8_CG1_OS) under the recovery-site vCenter, our plug-in can not find the protection group on the recovery-site SRM server.

Actually, on recovery site, the protection group does exist (e.g. id is srm-protection-group-7389), but the id of its protected virtual machine is vm-162 (instead of vm-221). So vm-221 cannot be found in all protection groups and hence no protection groups will be listed for end user.

[Question]

1. In test fail-over case, why the id of protected virtual machine by protection group srm-protection-group-7389 is vm-162, rather than vm-221? This makes our plug-in not working.

2. Are there any ways to allow our plug-in to know vm-221 does be protected by srm-protection-group-7389? If there are no reasonable approaches, our plug-in will be blocked by this kind of issue.

[More Info]

More details info (e.g. environment, sample code, logs), please check the attached doc.

Thanks in advance,

Eric