do you have resolve this problem ? I have the same message..
Failed to retrieve datastores:, Bad Request ,could not create proxy for rpa RPA...
Thank you very much.
If you have no warning during checkup process then :
First don't care of warning for Recoverpoint cluster IP.
Do not put your temporary RPA1 IP.
Then take care if you have clone your first RPA for 2nd RPA deployment in my case temporary IP was not set...
I have try different settings and still have some issue. I probably miss something regarding this point :
Applying a new network configuration in Windows
An example of how to manage your network configurations in Windows 2008 and 2012.
1. Download the relevant glue script from the RecoverPoint for VMs page on the EMC ECN
On the production VM, add the glue script to the registry by creating a key called IP in
the registry path and adding the full path of the script. For example:
3. Navigate to Protection > Consistency Groups, expand the desired consistency group,
and select the relevant copy.
4. Click the Edit Copy Network Configuration icon and click Save as… to export the
current network configuration to a CSV file.
I have set the following registry key :
Is there something misconfigured ??
After creating the registry entry and copying over the script - did you create a Windows scheduled task? That is needed in some cases and I had to do that for mine to work after I copied over the script, made the registry entry, and edited the CG variables.
In task scheduler you can do the following so that it does it on the first boot during a test/failover (screenshots are from a test a while back....but I haven't touched much so they should still work):