Solved!
Go to SolutionT
ThomDaleyPPI
1 Rookie
•
108 Posts
0
5396
July 5th, 2016 07:00
Auto SRM mode
Hi,
I am running into an issue with RP and SRM. When I go to run a test, it errors out with a message that the CG is in manual SRM mode and that no operations can be performed on it. The recommended fix is to switch it to auto SRM mode in the group policy for the CG, the problem is there is no manual or auto setting that I can find, it just lists SRM and that's it. Has anyone else run into this issue?
Thanks.
2883
0
Posted July 5th, 2016 07:00
2884
0
Posted July 5th, 2016 08:00
Hi Ankur,
Here is the error message from SRM:
And here's the group policy setting in group policy on RP:
I don't see auto or manual anywhere.
2883
0
Posted July 5th, 2016 08:00
Hi Ankur,
I already have that setting in place and SRM sees the VMs and RDMs as protected through RP. The error says it needs to be in SRM Auto mode. Do you know where I can find that?
Thanks for the quick reply.
2884
0
Posted July 5th, 2016 08:00
Whenever Ive implemented SRM this was the only setting in RP I needed to make. I have never seen this "SRM Auto mode" Are you sure the Managed By is set to RecoverPoint?
2884
1
Posted July 5th, 2016 09:00
Hi Ankur,
I'm probably going to open an SR. I'll double check the release notes, thanks for the help.
Thom
2884
0
Posted July 5th, 2016 09:00
The only thing I could find was this, but it looks like you have SRM selected. Are you certain you have the right supported mix of RP/SRM/SRA?
You might want to open a SR if you do.
2884
0
Posted July 5th, 2016 10:00
If you do please share the SR#
2884
0
Posted July 5th, 2016 12:00
I just went through the compatibility guide and SRA 2.2.03 running with 6.0 is not compatible with XtremIO 4.0; it looks as though I'm going to have to upgrade to vSphere and SRM version 6.1.
1285
0
Posted July 6th, 2016 08:00
Hi Thom,
I have seen this message before. Firstly, ensure that the SRA is configured to use the DR cluster IP address. Secondly, ensure the RP user that SRM is using has RP admin privilege. Thirdly, the logs may show that one of the storage settings may need extending, possibly, storage.commandTimeout from 300 to 1800. This requires a restart of the SRM service.
Regards,
Rich
RecoverPoint Corporate Systems Engineering
forshr
2 Intern
•
1126 Posts
3808
0
Posted July 6th, 2016 09:00
Can you clear the current external management settings for the CG(s) using the clear_externally_managed_parameters CLI command and then reset them using the config_external_mgmt CLI command with the external_application parameter being SRM and the managed_by parameter being EXTERNAL_APPLICATION.