SITE RECOVERY MANAGER SRM

Written by Sam McGeown on 23/7/2014
Published under VMware
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.
Written by Sam McGeown on 16/5/2014
Published under VMware
Yesterday saw another fantastic London VMUG with lots of quality sessions and opportunities to network with peers and friends. The committee seem to do a fantastic job every time and this one was no exception, so thanks to Alaric Davies, Jane Rimmer, Stuart Thompson and Simon Gallagher! One of the best things for me about the VMUG is the chance to chat with some of the smartest and most influential people in the VMware world – a trip to the coffee table provided a great opportunity to “chew the vfat” with two of the VMUG’s biggest characters, Mike Laverick and Ricky El-Qasem – all before any sessions had started.
Written by Sam McGeown on 6/3/2014
Published under VMware and vSphere
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.
Written by Sam McGeown on 5/3/2014
Published under Microsoft and VMware
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).