dear all
Hi
i have a question about SRM is this feature for active - active datacenter ?
for example i have a datacenter with this ip range : 10.0.0.x
if run srm my disaster recovery site has same ip adress or it can a different ip range 10.0.1.x ?
best regards
Anyone seen this before when pairing site 1 to site 2, the other way around is fine no error, time is all in synch between servers and adminstrator@vsphere.local credentials work fine.
Hello all,
I am currently working on an implementation of SRM.
My setup consists of Vmware SRM server build 3037005, vCenter 6.0, ESXi 6.0.0 and IBM Storwize Family Storage Replication Adapter.
Pretty much everything is up and running, I am able to recover some test VMs to the recovery site, but so far I have not been able to reprotect the VMs in the secondary site.
After running the recovery plan completes I am left with my machines up and runnning in the TR site.
When I try to reprotect the VMs I get errors.
The recovery plan fails at the stage where it should reverse the replication.
messages shown are:
Failed to reverse replication for failed over devices. SRA command 'ReverseReplication' failed. Invalid connection parameters.
The protection groups hangs in the status 'Reprotecting'.
From what I found in documentation this should be a temporary status and it should, change to one of these values:
Group returns to OK or Not Configured state when reprotect is successful. If reprotect fails, the group goes to Partially Reprotected state.
When I look at the information in the Array Pair screen, I see these errors:
Unable to find a matching consistency group at the local site for the remote consistency group "TEST-01"
Unable to find a matching consistency group at the remote site for the local consistency group "TEST-01"
In the list of array pairs the status has changed to "? unknown"
I already updated the SRA to version 3.2.0 but it has not changed anything.
There is one primary question I am curious about. The SRM servers with the SRA on it have the configuration utility for SRA.
If I run this utility I get a warning that it is unable to connect to the peer array in the other data center.
So it has no issues login in to the storage box that is in the same datacenter, but cannot logon to the remote storage box.
Since this is a warning I am assuming it is not critical, but I need confirmation on this
Before I start initiating changes in the network to make this possible, I want to be sure it has to be possible to reach the remote storage box with the SRA.
Any help or insights is greatly appreciated,
JJ
what could be the cause of this and its work around?
Can anyone share what will be the impact of these failures in SRM? Can the machine replication continue to run or not? Can the machine be recovered or not? in any of these failures.
1. vCenter Failure (Protected or Recovery Site)
2. SRM Server failure (Protected or Recovery Site)
3. vSphere Replication Appliance Failure (Protected or Recovery Site)
Hello Guys
I have been trying to protect vm's on SRM. But everytime I try to do it, it fails with error : com.vmware.vcDr.dr.fault.InsufficientLicensesFault.summary
It says : There are not enough Licenses to Perform this operation.
I checked all the licenses we have and none are expired.
Any Idea ?
If in recovery site routing tables needs to be updated at router then can it be done in automated manner once the machines get recoverd at recovery site?
Can single workload have multiple recovery sites?
today i created srm resource pool mapping with keeping reverse mapping enabled and then i deleted it and created it again without reverse mapping but still it was showing reverse mapping = yes. Just want to know why it is not getting cleaned up even i deleted it recreated it. Is it product bug or something else?
Why it is only supported with SPPG?
In an SRM failover, is it really normal that the data is not the same with the PROD VM?
Replication medium is host based replication and the replication status is okay.
The issue here is even in during test recovery fail over, ther is data discrepancy from the PROD site.
Example, a DB is successfully replicating but after test recovery, about 1TB of the PROD VM data is missing specially the DB data.
Another we encountered is that after a test recovery fail over, data discrepancy is around 100GB.
But after doing cleanup and a second test fail over is initiated, data is already the same.
I saw the KB Calculating Bandwidth Requirements for vSphere Replication (2037268) | VMware KB on bandwidth requirement calculation as well as this in one of VMware Doc
You calculate vSphere Replication time to ensure that it occurs within the stated RPO:
•Average daily rate of change = 10 percent
–100 GB VMDK file that changes 10 GB per day
•RPO is 1 hour
–Average hourly change rate = 0.10 / 24 = 0.00416
•Size of hourly replication data is 426 MB
–100 GB x 0.00416 = 0.416 GB (426 MB)
•Transfer time for one sync per hour at 9 mbps is 6.6 minutes
–3,573,547,008 bits / 9,000,000 bps = 6.6
Where is Latency consideration in this KB? Is this calculation willl remain same in these two scenarios's?
Link Speed is 9mbps:-
What If i am replicating the VM between Hyderabad and Bangalore Site = ?
What If i am replicating the VM between Bangalore and US site = ?
Scenario:
Recovery Plan 1: APP1, DB1, WEB1
Recovery Plan 2: APP2, DB2, WEB2
SRM can do datacenter migration/disaster avoidance:
1. If failover is initiated, PROD VMs do a last replication, power down PROD VMs and power on DR VMs?
2. If Recovery Plan 1 is initiated failover, VMs in the Recovery Plan 2 will not be affected right. same if recovery Plan 2 is initiated?
3. Will SRM stop the replication of Recovery Plan 1 VMs (vSphere Replication/Array Based Replication) only and not the Recovery Plan 2 VMs (Recovery Plan 2 VMs replication ongoing)?
4. If Recovery Plan 1 VMs are powered on the DR site and reprotect is initiated for this recovery, only Recovery Plan VMs 1 will be replicating now from DR to PROD without affecting the PROD to DR replication of Recovery Plan 2 VMs?
We are in the midst of configuring SRM 4.1.2.
We have a very basic configuration:
Protected Site:
3 x Dell R710
ESXi 4.1u1 / vSpehere 4.1u1 (VC Server)
Dual channel QLogic FC HBA multipathed via 2 FC switches
Compellent C30 based SAN (Dual controller)
Recovery Site:
4 x Dell 2950
ESX 4.1u1 / vSphere 4.1u1 (VC Server)
Single Channel QLogic FC HBA (Multipathed to Compellent storage via iSCSI)
Compellent C20 based SAN (Dual Controller)
50MBps EPL between the sites with "Replicate Active Replay" selected on the Compellent. (This is caught up to realtime MOST of the time)
We have a recovery plan set up to recover 5 VMs off of three protection groups. Two of the VMs use RDMs, the rest are all VMDK based. Compellent Enterprise manager is running at the recovery site.
When I go to test this recovery plan, about one out of every 7 or 8 times it completes without issue.
About half the time it will fail on one of the three "Prepare Storage" tasks with the error "Error: Failed to connect to management system address while executing 'testFailover' command.", however the other two storage tasks will complete successfully. (This seems to me to be a problem with the communication between SRM and the SRA, or the SRA not liking to handle multiple requests simultaneously, but I can't prove it.)
The other half of the time I get a failure on some of the low priority VMs that states one of the follwing:
Compellent states that everything looks good. VMWare was troubleshooting the issue and says it might be because we don't have multiple paths to the storage on the DR site. However, when I look at the storage when connected to the VC server, all the LUNs show up. I enabled multipathing at the DR site via FC/iSCSI and we're still getting the same errors randomly. The VMware engineer is looking into this still, but they haven't come up with much yet. I've upped the HBA rescan count on the recovery site to 2 scans and that seemed to help a little, but it's not sure fire.
I don't know where to go from here. The fact that it works SOME of the time is what really gets to me. When it works, it works well and does exactly what we are looking for!! Something has to be configured correctly for it to work at all, but I'm unsure as to where to go from here. It's really putting a cramp in our project.
I do always have the option of telling my CIO that we will be ready for one out of 7 disasters, but I don't think that's going to go over very well :-)
Anyone been here before or worked through these types of issues?
Hello
I configured SRM and performed Test failover. But it failed with following error
Error - Failed to create snapshots of replica devices. Failed to create snapshot of replica device 300. SRA command 'testFailoverStart' failed for device '300'. Device is already in test failover [Device: 300] Run Stop Failover Test on key
I tried changing settings based on suggestions on google but nothing worked.
Hello
Is IP Customization mandatory while setting up SRM? Or SRM automates this process?
Hi,
Have been reading up a lot on vcenter but unable to find the answer to this
Can SRM failover the vcenter server from site A to site B?
In the PROD site, there is an EMC SAN storage and on the DR site, there is also a corresponding DR EMC SAN storage.
During SRA configuration on both sites, I assume that the EMC storage in the DR site should have been mapped/zoned/visible to the DR ESXi hosts in order to be mappings will be made?
I am receiving this error when trying to setup a protection group for single vms.
I have verified all connections ok and Time is synced across all devices.
Is there something I am missing ? I have configured one single vm for replication , but when I try to create protection group under site recovery it states it cannot connect to production site.
I have a fairly strange issue
I have been trying to install the latest version of SRM with the embedded database. Everything works ok and the installation goes through without any issues.
I am using the latest version of the VCSA for vSphere 6
There is no firewall between the VCSA and the SRM windows vm and they are all on the same subnet
I have verified that SRM has deployed by making sure the object is registered under vcenter and it is there by going to http://vcenter_name/mob
The only problem I have is that I cannot see the icon on the home page and it is not listed under client extension
I have tried removing the extension and re-installing SRM several times but each time I cannot get the icon to appear on the home page
Just wondering if anyone has seen this problem