We are currently trying to implement VMware Site Recovery Manager.
Our existing environment consisted of two physical data centers connected with a 1gbps link. Both sites were managed via a single vCenter server located at our primary site running vCenter 5.5 Update 2 installed on Server 2008 R2.
Each site has an IBM Storwize v7000 running code level 7.3.0.9. Our primary site is using the second generation v7000 with compression enabled. Our disaster site is using the first generation v7000 without compression but the volumes are thin provisioned. We had an outside IBM vendor help us configure replication between the two v7000’s. Some of our volumes are replicating using change volumes while a few volumes are simply a global mirror. The replication is running smoothly – no issues.
Our hosts at the primary and disaster recovery sites have been zoned to see the volumes and the host mappings on the v7000 have been created.
We have since deployed a second vCenter server at our disaster recovery site and migrated any DR servers from our primary vCenter and to the DR vCenter server. The new vCenter server is version 5.5 update 2 running on Server 2012 R2. So we now have two separate vCenter installations managing their own local inventory. These vCenter installations are not linked. Everything is functioning as it should.
We then installed VMware Site Recovery Manager version 5.8 on both vCenter servers without any issues. We then paired the two sites within SRM. At this point, everything is still going smoothly.
Our next step was to install the IBM Storwzie Family Storage Replication Adapter on both of the vCenter servers. The installation of this appeared to be straight forward. I went ahead and downloaded and installed the IBM Storwize Family SRA version 2.3.0.1.141126 from the IBM website. Now this is where things get a little confusing. According to the SRA documentation, I’m supposed to launch the IBMSVCSRAUtil.exe utility, select “Standard” for the volume type, and then enter the pool ID in the Test MDisk Group ID field. Then click Ok. Both of our v7000’s only have a single pool and the ID is 0 on both. I'm confused as to whether or not we're a Non-preconfigured environment or a pre-configured environment and if we need to worry about the Protect Source/Target Vols fields.
Now the documentation indicates to launch SRM and rescan for SRA’s. At this point SRM sees the IBM SRA at both sites and indicates the status as OK. No problems.
The next step is to Add Array Manager. This is where things fall apart. I select the option to “Add a pair of array managers”. The problems begin when I reach the Configure Array Manager portion of the wizard. For the CIM Address of Primary SVC, I’ve tried entering all 4 IP addresses I have for each v7000. From my understanding each controller of the v7000 has an IP and then there’s a virtual IP. On top of that there’s also an IP that we use for replication. I’ve tried all 4 IP addresses. I’ve here and receive the error shown in the screenshot below. The superuser account is exactly the same on both v7000’s. I’ve also tried creating a new user on both v7000’s called “srm” with the same password and assigned it the Copy Operators role - same problem.
If I repeatedly click next it will finally allow me to continue through the wizard. On the Configured paired array manager page I simply swap the CIM Addresses and make the primary the DR v7000 and the secondary the protected site’s v7000. Once gain I’ll continuously receive the same error regarding discoveryArrays failed. And once again clicking next repeatedly will eventually allow me to continue. Then I complete the wizard.
I can now see both array managers in SRM. They are enabled but when I select them I receive this error.
At this point I decided to go back to the utility and run the Check Configuration option. It fails.
I’m not sure if I have a problem with the SRA, v7000, or both. Any information would be greatly appreciated. Thank you for your time.
I also tried posting this topic on Spice Works, VMware SRM and IBM Storwize SRA Issues - Spiceworks.
