If they are a separate pair then they should be OK to remain as-is, although just from an operational and management (not to mention consistency and troubleshooting) perspective, I'd probably upgrade the other pair to the same version as well. With ELM being in the picture, I'm not positive on how those vCenter extensions will play well together if they aren't at the same version across the SSO domain in question. It's certainly simpler to know that infrastructure X is all at version Y across your estate, if for nothing else.
Thanks for the reply. Both site pairs would eventually be upgraded.
I am just trying to work out if this needs to be big bang (not ideal) or can be phased with the other pair remaining on 6.5.1 working for a short period
I don't think it'd need to be a big bang, no. Just eventually I'd get them all in step.
Thanks. I wonder if anyone who has done this can confirm
my concern is that 8.1 merges the vSphere replication and SRM features into a single plugin/icon in the web clients (which then goes external to the new HTML5 interface in SRM 8.1)
what would happen to the plugins and buttons post upgrade for the old 6.5.1 site pair. I worry I would essentially be locked out of the older site pair and unable to access its GUI
same question for the vsphere replication icon, will it remain or disappear
a good one for some lab testing maybe but if anyone has done this id be very interested to hear!
This use case is supported - VC 6.5 with 2 x SRMs - 6.5 and 8.1 registered to it. The only drawback is - in SRM 6.5 UI you might started to see some annoying UI "unsupported version" errors, that can be safely ignored or you can avoid this, if you upgrade your SRM 6.5 instance to SRM 188.8.131.52 patch release - see VMware Site Recovery Manager 6.5.1 Release Notes
Unsupported version errors appear on every refresh operation in SRM 6.5 UI.
If user has SRM 6.5 and SRM 8.x registered under the same Platform Services Controller or under federated ones he will experience
unsupported versionerrors on every refresh operation in SRM 6.5 UI
This issue is fixed in Site Recovery Manager 184.108.40.206.
Hope this helps