srm

Sunday Arriving in early on Sunday as the local flight choices are more limited from Bristol than perhaps a larger Airport, very fortunate to have a hotel so close to the VMworld venue, perhaps not so great for the evening activities but I am happy with it this way around. Other than registration (4pm-8pm) and hopefully catching up with a few folk who have also arrived early. In the evening I had the pleasure to meet many awesome people from the vCommunity.

So vROps 6.1 has gone GA! What have the guys at VMware added? I have listed what I consider the hi-lights below The maximum of 8 nodes has been doubled to 16! SSO integration has been added (requires vSphere 6.0) **Support for SRM has been added ** vRealize Hyperic functionality has been added With the addition of End Point Operations Management, the value of vRealize Hyperic functionality has been extended to the vRealize Operations Manager core product, without the need to deploy vRealize Hyperic

Quick post to cover a fix for installing the VNXe SRA when you encounter the below error: Failed to load SRA from ‘C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/EMC VNXe SRA’. SRA command ‘queryInfo’ didn’t return a response. The components installed (in this order) are: vSphere 5.5 SRM 5.5 UNISphere CLI 1.5.4.1.0027-1 VNXe SRA 5.0.0 The root cause is that the system locale is EN-GB rather than EN-US, however even changing the locale does not resolve the issue.

I’ve been playing about with a compact SRM install in my lab - since I have limited resources and only one site I wanted to create a run-through for anyone learning SRM to be able to do it in their own lab too. I am creating two sites on the same IP subnet (pretend it’s a stretched LAN across two sites) and will be protecting a single, tiny Linux web server using vSphere Replication.

I’m fairly new to SRM, but even so this one seemed like a real head-scratcher! If you happen to be using CA signed certificates on your “protected site” vCenter and “recovery site” vCenter servers, when you come to linking the two SRM sites you encounter SSLHandShake errors – basically SRM assumes you want to use certificates for authentication because you’re using signed certificates. If you use the default self-signed certificates, SRM will default to using password authentication (see SRM Authentication).