Installing SRM VNXe SRA – Failed to load SRA, ‘queryInfo’ didn’t return a response
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 220.127.116.11.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. The Java installation will still try and load an en_GB module and fail. The solution is as follows:
Edit “<SRM Install>\storage\sra\EMC VNXe SRA\command.pl” in notepad and replace:
system("jre/bin/java -jar EmcVNXeSra.jar");
system("jre/bin/java -Duser.country=US -Duser.language=en -jar EmcVNXeSra.jar");
Rescan the SRAs within SRM to load the VNXe adapter details.
#LonVMUG 15th May – another great VMUG!
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.
The first session of the day, after the obligatory coffee and biscuits, was presented by Itzik Reich of EMC’s ExtremIO talking about the all-flash offering. For a non-native English speaker I was thoroughly impressed with how he engaged with the audience and spoke. My main take-away was that you can’t treat flash in the same way as magnetic disk – it’s not just a faster version of the traditional spinning platter but requires a whole new approach as to how it’s used and managed. That may sound obvious but I think a lot of solutions treat flash as such, imposing magnetic disk concepts like RAID which don’t make the best use. Flash != magnetic disk, don’t treat it the same! (more…)
Installing VMware Site Recovery Manager (SRM) 5.5 in the Lab
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 aiming to cover SAN based replication in a later post.
Below is the list of hosts and VMs running for this exercise:
- ESXi-01 – my “Protected Site” – this is running DC-01, VC-01, SRM-01 and VRA-01 (to be installed later)
- ESXi-02 – my “Recovery Site” – this is running VC-02, SRM-02 and VRA-02 (to be installed later)
- DC-01 – this is my domain controller, I’m only going to use one DC for both “sites” as I don’t have the compute resource available to have a second running. This is also my Certificate Authority.
- VC-01 – this is my primary Virtual Center server, it’s a Windows 2012 R2 server. It is managing ESXi-01.
- VC-02 – this is my “recovery site” and it’s a Virtual Center Server Appliance (VCSA). It is managing ESXi-02
- SRM-01 – “protected site” SRM server, base install of Windows Server 2012 at this point
- SRM-02 – “recovery site” SRM server, base install of Windows Server 2012 at this point
- WEB-01 – this is a really, really, basic Ubuntu web server I’ve deployed from a template to use for testing.
Right – without further ado, let’s get stuck in!
Generating and Installing CA Signed Certificates for VMware SRM 5.5
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). Where the process fails is during the “configure connection” stage, if either one of your vCenter servers does not have CA signed and the other does (throws an error that they are using different authentication methods) or that you are using self-signed certificates for either SRM installation (throws an error that the certificate or CA could not be trusted).
SRM server ‘vc-02.definit.local’ cannot do a pair operation. The reason is: Local and remote servers are using different authentication methods.