I just went through more or less the same scenario as you. But with a client's production environment.
They were running vsphere 5.5 u2, View 6.0.1, vRA 5.8 and SRM 5.5. I performed all upgrade steps in the correct order, but I haven't been able to get vSphere replication and SRM running without losing the configuration. Which in case of the vRA is n't that bad as it detects the old replica's as seeding points. And SRM 6.0 is much easier and less labour intensive to configure than the old one
What do you need to do: you need to reconfigure both the vRA appliances (https://<ip addr>:5480). If you are using self signed certificate, as in my case, you're going to have a problem with the certificate of the appliance. It was expired and I needed to create a new one for each appliance.
I suppose that's where my problems started, as even after reconfiguring the appliances I couldn't get it to work. I could create a connection from site A to site B, but from site B to A wouldn't work.
I always got "connection error"
In the end I decided to scratch the vRA's and redeploy them. Which was great, as after I've configured them, I could make the connection between both sites in both directions, and all was well. NOT:
There are another few issues with vSphere Replication 6.
- Sometimes the web client won't show the destination datastores, and you'll have to restart the webclient on the source site.
- When I got it to show the datastores, every new job ended with "permission denied", so if you want to add a new replication job, you need to log with the default SSO administrator of your environment, or it won't work. Believe me, I've tried.
Additionally, I hope you've read the release notes, as they tell you that the default vSphere Replication roles lose all their rights after an upgrade. I can't confirm this, as I ended up, removing everything and deploying new vRA's.
I suggest you read the release notes, as every obstacle I ran into was described in the release notes. (only the thing that only the SSO administrator can create replication jobs might have been explained clearer..
I can't understand how the guys at VMware managed to make such a mess. vSphere Replication was such a wonderfull product: reliable, quick and easy to setup, and with version 6, the upgrade (or installation) such an incredible mess. Though once configured and up&running, it seems to work well.
Best of luck.
(p.s. if the service keeps starting and stopping, after you've reconfigured the vRA, you need to configure NTP in the appliance (as explained in the release notes)
Thanks for the update. I actually deleted the appliances and redeployed vRA 6.0 and both appliances registered correctly with vCenter and appeared in the web client and i reseeded.
I haven't created any new jobs yet but ill keep that in mind when creating new jobs.
Totally agree with you on VMware messing up vSphere Replication with the new release.