Hi
I am facing the following problem with SRM 5.8 (vCenter Server 5.5 U2), while configuring Protection Groups as the following :
The SRM Server on both Side is licensed as below, and the used VMS are zero.
I have re-installed the license key again and restarted SRM Service and Server per the below VMWare KB, with no use
please help and advice.
regards
Najeeb.
Has anyone else seen this error with VRMS?
I have two sites setup in SRM5.
Each site has a VRM server deployed, configured, and connected.
Each site has a single vSphere Replication server deployed and registered as well.
Summary tab shows them as connected via IP (did not use DNS due to other problems I had read), one site shows 2 source VMs, datastore mappings are correct, permissions are correct (run as admin).
So when I try and tell it to "synchronize" I receive a "HmsGroup.OnlineSync" for object "GID...." on Server "xxx.xxx.xxx.xxx" failed. An unknown error has occurred."
Anyone else run into this or could give me some pointers on how to troubleshoot from here?
Thanks.
hello,
i would like to know what is the best practice to change vmware srm edition from standard to enterprise. i must change due to number of VMs that can be protected limitation.
tkx.
I'm scheduled to run a planned recovery on our Production servers this coming weekend. We will do a recovery, testing and then reprotect and fail back.
I've been through this with a group of development and test servers and it has gone well. The one question I have is about the site to site resource mappings, such as folder and network.
I have these defined from the protected site to the recovery site. In my testing with development servers it doesn't appear that creating mappings are needed from the recovery site to the protected site when doing a failback.
My assumption is that these are not needed as long as they are defined the other way. Is this correct?
Any other pointers about doing a test recovery are also appreciated. 
Hello,
Is there a time limit on running Recovery Plan in a test mode without Performing Clean up?
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.
Hello All:
I have a couple quick questions I was hoping someone could address in regards to Array Based replication on an initial setup I am starting to lab. Below will state my BARE minimum setup.
3 datastores in each location
1 - will contain the VMS that will be replicated via ABR for DR and SRM testing.
1 - will contain vCenter and the SRM VMs in each location (I am assuming you do not want to replicate these VMs as they exist in both locations already and other vms to NOT be replicated).
1 - Placeholder datastore for the VM files in secondary and primary for failback.
Does that sound valid? I just want to be sure I do not have to replicate the SRM or vCenter primary vms for any reason (I could not find documentation on this).
Also from my storage provider, I found a snippet in the replication adapter documentation stating - "The recovery/secondary volumes remained unmapped"
So should I not connect my secondary volumes in the secondary site off the bat? To me that just seemed logical to do so. I could not find documentation on the secondary site. All the write ups I saw were the user in the primary site.
Any clarification anyone could provide would be great.
The GUI for specifying Recovery and Protected IP settings is limited to specifying 2 DNS server addresses.
Can you specify more than 2 if you use dr-ip-customizer to configure this?
It appears from looking at Mike Laverick's book you can do this.
As we are looking for a BCDR solution, it turns out it will cost us a bundle, e.g. Unitrends, Datto, Veem etc.
Now that VMware 6 is out, is there any native VMware capabilities that I can leverage to do the following ....
1- to achieve our Business Continuity/Disaster Recovery plan?
2- to do automatic replication locally and thru WAN efficiently,e.g. take the snapshot and replicate the changes and compress them for transport locally or remotely?
3- to do incremental snapshot to a secondary site so we can easily spin up the VMs in case the primary site is down?
4- to do traditional backup in which we can do file level recovery for our data file such as MS Office files, row-level recovery for SQL Server, specific email level recovery for our Exchange Server, with the SLA we determine?
what's the inexpensive alternatives for performing the backup of our VMware Infrastructure - Acronis, Ahsay, etc?
5- to do cloud backup?
We have 2 sites, one with Essential Plus Kit and the other with just Essential Kit.
1- To achieve the above, do I have to upgrade the Essential Kit to Essential Plus Kit?
2- Is SRM included in Essential Plus Kit so I can do automatic/orchestrated fail-over? If not, do I have to buy 2 copies for each site or just 1 copy since we have way less than 75 VMs?
3- How much approximately I have to spend or is it justifiable to just buy Veem or any of those product to handle all the above?
Thanks
Hello,
VMWARE 4.1 Hosts,
Vcenter 5.0, SRM 5.01
We recently shut down a main branch and performed a SRM recovery at the second site. The recovery went smooth except I show three VM's that are still being manager by the SRM manager Extensions.
I have 8 other VM's that I can manage fine after the recovery. How do I change the manage by option for individual VM's?
I am wondering if anyone has tried to configure SRM protection on MSCS VMs. Below links suggests following contents:
Cluster across the boxes:
You can spread the MSCS cluster across a maximum of two ESXi Server instances. You can protect only one virtual machine node of any MSCS cluster on a single ESXi Server instance. You can have multiple MSCS node virtual machines running on an ESXi host, as long as they do not participate in the same MSCS cluster. When running MSCS in a cluster-across-boxes configuration, Site Recovery Manager only supports two-node MSCS clusters.
If I am not mistaken, the steps would be as follow:
Can anyone confirm if this is tested and if yes what would be correct steps?
Kind Regards,
Kedar
I am having an issue where I cannot get the SRM sites to pair, we are running 5.1 update 1 for everything and the corresponding SRM release. I tend to think part of the problem is SSO seems to be slow. We tend to have problems with authentication where it will just time out sometimes. I am waiting for support to look at the logs but thought I would post the question here. Network latency between sites is LAN speed ( basically no latency) and all performance for both Servers is normal. SRM is loaded on the same server as vCenter. Basically when you try and run the pair it gets through the second step of Authentication ( even though it takes a while) then when it tries to pair (The complete connections step) sometimes it will make it through connecting to the vCenter and cert validation for it but fail at connecting to the SRM instance then sometimes it will fail right at the beginning and not connect to the vCenter. The error says that it timed out waiting for a response from host but gives it's own IP. Looking in the logs the only kind of error I ever see is 08284 error 'SoapAdapter.HTTPService' ] Failed to read request; stream: <SSL(io_obj p:0x0000000006e1b0c8, h:2504, <TCP 'local server IP:8095'>, <TCP 'local server IP:51120">>)>, error: class vmacore::SystemException(An established connection was aborted by the software in your host machine) . Otherwise in the log it shows probing for the other VC and finding it and its certificate but the actual pairing fails, no authentication errors being denied or anything. Have tried looking around and cannot find anything with that error for pairing.
Hi There!
My understanding is that SnapMirror doesn't do any quiescing, so as a result you will only get crash consistent backups?
My question is, when using the NetApp Storage Replication Adapter with Site Recovery Manager, do you now get quiescing support, as SRM can work alongside the Array to orchestrate the recovery properly?
Cheers,
Bilal
We're currently testing VMware SRM 5.8 on 5.5 u2 VCenter Servers.
I was testing a Recovery Plan today that hung due to there being 2 network cards on a VM's protection profile but I'd removed one of the NICs from the VM after creating the protection profile..oops...anyway, the SRM Server service crashed on the Recovery side during the test and now I get the message that the Test was interrupted and to perform the Test again immediately. I ran the test again and the same behavior happened.
One of the vms from that Recovery Plan is still powered on the recovery side on the test network. I'd like to shut it down and clean everything up manually but that won't fix this particular Recovery Plan. For that I assume I need to clean up the database as recommended in this article: VMware KB: VMware vCenter Site Recovery Manager recovery plan fails to complete
But that's for a SQL database and we're using the embedded DB -- how would I do this for the embedded database?
I tried calling VMware but they don't give support on trials......
Thanks!
Hi All-
Trying to get some clarification on what the volume LUN numbers are in theory suppose to do on failover and failback. In the whitepapers for the storage we are using it states, "keep the volume LUN numbers upon failover, and reuse them upon failback"
This makes sense, however in our test failovers the LUN number say 50, gets changed to 1 when it gets mounted in the warm site. Can this be statically defined, my understanding it this is explicitly handled by the SRA and no intervention is needed. However would in a actual failover, changing to LUN number 1, affect the failback? I could not find any documentation online in regards to this.
Any input would be appreciated, just trying to understand this piece.
I have vCenter running in my HQ site (Protected Site) and i have another vCenter running the DR site (Recovery Site),
I made my SR setup in both sites and every thing is working with no issues,
We have a new branch with a new vCenter and we want to protect this site, how can we achieve this? do we need to have a new SRM installation in both Sites?
In another word can we have 3 sites SRM scenario? or it will be a new SRM installation?
I have a customer who upgraded his vCenter servers at both sites from 5.5U1 to 5.5U2, a requisite for SRM 5.8.
After what seems to be a successful SRM installation at both sites, I do NOT see the SRM icon available from either site.
Tried restarting the VMware vCenter Inventory Service
SRM Server and Embedded Database services are running
I checked the below and the ExtensionManager value, com.vmware.vcDr is in fact present.
Notes:
1. SRM is installed on the respective vCenter servers using the embedded ProstgresSQL DB
2. vcEnter is also using the embedded DB - There are only 3 hosts per site
3. The total number of protected VM's is anticipated to be 12
Any ideas?? I know it's a new product, but here we are.
I'm preparing to move the database from one of my SRM servers from one database server to a new one.
The old database server is running MS SQL server 2005 (32 bit) and the new server is running MS SQL server 2014 (64 bit).
I had attempted to move the database previously to a MS SQL 2012 server and failed. Further research showed that SRM 5.1.2 or any other version of SRM isn't supported on MS SQL server 2012 SP2 only SP1. I've upgraded SRM to 5.1.3 so it will be compatible with MS SQL 2014.
Questions: Does it matter that the new database is 64 bit? Do you still use a 32 bit DSN?
Should I upgrade the Native SQL client on the SRM server?
Hopefully the move will work this time. Support said all that was necessary to move it was to:
1. Stop the SRM service
2. Move the database to the new server.
3. Reconfigure the ODBC connection
4. Restart the SRM service
When I move it last time the service would start and the stop. Not sure if that can be attributed to the unsupported database SP, somehow I'm suspicious that wasn't the problem.
Hello,
We have installed and configured SRM 5.5.1 in Main site and DR site. In DR site we have two hosts and no shared storage.
Each have one vsphere replication appliance deployed and both the sites connected and we have also replicated two virtual machines successfully.
Next step we have configured protection group and recovery plan as well.
But when we test a recovery plan it gives a error "unable to access virtual machine configuration file"
Is it necessary we must have a shared storage? Can't we use local datastore on each host to power on the machines.
Regards
Karthik
We are planning on moving our hosts to a new vCenter and don't want to do a huge amount with SRM (it is installed on its own VM in the environment and is using an SRA).
From having a look around I believe I should be able to do a repair on the existing SRM install and point it to the new vCenter, during the repair I assume it will ask for the IP address of the new vCenter? Following this I hope to upgrade to 5.5.8 from 5.0, could I possibly do the upgrade and repoint at the same time?
I have seen the following KB article, but I assume that I wont need to follow it if the installer updates the IP address for me?
Many Thanks!