Confused by New DataStore Protection Groups - SRM 6.0 on Dell EqualLogic SAN
Forgive the daft question, however here we go.
On 5.5 we had 6 Datastores on our EqualLogic san, and a protection group for each. Now on SRM 6.0 We can only create Array based Protection groups on the Datastore Protection Groups that have been auto created, but this has missed 4 of my Datastores, so I can not protect all my VMs, what have I missed.
thanks in advance
John
Hi,
I need multiple arrays pairs in one protection group.
We I get new array pair I should be able to add to existing protection group only.
When I try to create protection group at any given point, I am able to select only one array pair.
If we can add multiple array pairs to one protection group, how?
Thanks,
Ramu
I've been using SRM5 with host-based replication pretty extensively and for the most part is has been solid. I am using it to protect 18 VMs at my production site. I am now trying to configure a couple of VMs at the recovery site to replicate back to the production site. I was able to go through the wizard, watched it create the virtual disk, but when looking at the vSphere replication section in SRM, the status for these VMs is 'not active'. If I highlight one and select 'synchronize now' it either does nothing (status remains 'not active') or I get an error saying that 'An ongoing synchronization task already exists' and the following info in the error stack:
Call "HmsGroup.OnlineSync" for object "GID-5be7451c-c57d-4f6b-bb8e-01cddec9297e" on Server "192.168.XXX.XXX" failed.
An unknown error has occurred.
The server it is referring to is the VRMS server at the recovery site. Additionally, in the recent tasks area I see the message 'vSphere Replication operation error: Virtual machine is in an invalid state."
I have rebooted everything in the environment, including the VR servers, VRMS servers, Virtual Center servers (which include all the databases), vSphere Host servers, and the VMs, at both sites. Verified there is plenty of storage on the target datastore. I even removed the VMs from the inventory and re-added them, but still get this error.
Ok now the best part - when I look at the target datastore, it appears that the VM has actually been replicated successfully. I see all the virtual disks that I'd expect to see, and all the hbrcfg files, with 'modified' timestamps that correspond to the last time I attempted to force replication. So just a GUI issue or what? Anyone else ran into this yet?
I plan to open a support ticket but want to make these errors visible to all. For the errors, I have replaced names but left the important content. We had several issues with ESXi v6.0, vCenter 6.0, and SRM 6.0. I recommend hold off on v6.0 products until VMware releases a U1 patch.
#1
Permission related blocked SRM views and certain functions not executing
When using SRM as any other user aside from administrator@vsphere.local, you run into permission related blocked views and certain functions not even initiating. If you click around, you can sometimes get the view to populate. In some situations, it is impossible to execute a recovery. I have tried using AD accounts that are nested in groups with Administrator permission and even not nested. If I log in as administrator@vsphere.local, there are no issues.
#2
"Cannot unmount volume 'Datastore Name: datastore1 VMFS uuid: <id>' because file system is busy. Correct the problem and retry the operation."
SRM fails to unmount the datastore from the protected site across all ESXi hosts. The behavior is inconsistent in regards to which host it can't unmount from. If I immediately rerun the recovery without making any changes, it will complete without issue. I can also manually unmount the datastore without issue.
#3
Recovered datastore 'datastore1' is not accessible to host 'host1'.
Warns about the datastore not being acccessible on the recovery site during the recovery. When I check the recovery cluster, the datastore is visible on all hosts. I can simply rerun the recovery without any changes and it will work properly.
Hi. I'm running SRM 5.1.1 with vCenter 5.1 Update 1. Primary and secondary sites separated by physical firewalls. I've followed the kb on ports:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1009562
I've tested with telnet and I can successfully connect from primary SRM to remote vCenter over 80, and vice versa from remote SRM to primary vCenter. Each vCenter can successfully communicate with their own local SRM server over 8095. In the primary vCenter I'm able to successfully establish reciprocity, and after I'm prompted for the remote vCenter creds, I see both sites successfully connected.
Now, when I hop over to the remote vCenter (recovery site) I'm able to establish reciprocity between both sites, but when the prompt comes up to enter creds for the remote vCenter (primary site), I get an error that comes back as "Unable to connect to the remote server"
Not sure where the issue resides. Any help most appreciated.
Thanks
Greetings,
I'm currently trying to test my recover plans for all of my protection groups and I'm getting the following error message:
Failed to create snapshots of replica devices. ( I include a screen shot of the error) Per the message, the cause is Storage Port not Found, Either the Storage port information provided in NFS list is incorrect else Verify the "isIP4" option in ontap_config file matches the ipaddress in NFS Field. Any suggestion? Thanks for any feedback as always!
is there any way to reapply the global change of a timeout value to individual VM's other then unprotecting them all and reprotecting?
For example, the VMware tools timeout, if I adjust after protecting a bunch of VM's it seems like if I want to reflect the new value I have to unprotect and reprotect?
I am doing an installation of SRM into an existing ESX environment. At the moment I have my original VC called VC4 which has 12 ESX hosts split across two Datacentres. Storage is presented from the two Data Centres to all ESX hosts and replicated between Data Centres.
I have installed a second VC called VC20 in mixed mode. I had initially understood that mixed mode would allow the VC20 server to use the resources in VC4, however this does not seem to be the case.
I need to confirm that for me to proceed with the configuration that I either need to configure additional ESX hosts into VC20 which will allow me to proceed with resource mappings or would I be better reallocating resources from my existing VC4 server and move 6 of the ESX servers to VC20 and leave 6 against VC4, effectively separating my Data Centres.
Also, what are the benefits of mixed mode installation for Virtual Centre.
I ran a test of my recovery plan with my domain controllers and they cannot ping anything, it says "unable to contact ip driver general failure". Has anyone come across this before? I found some forums about the SID being identical so I built a new DC from a deployment server, not a clone, and it assigned the same SID as the other DC's.
Hello,
I needhelp in resolvingbellow problem:
WhenI'mtrying to replicate vm in second vCenter by going to VR Replication tab in Classic client
a windowispopping and asking me to providecredentials for vCenter.
I'mputting the credentials in the window but when I click OK it'spoppingagain and againall the time.
On first vCenter I amable to replicatevirtualmachines.
I'musing vCenter 5.5 and SRM 5.5
My configuration:
vCenter view
SRM sites
InstalledVRs for eachsite
We have been using SRM for a number years to replicate VMs using vSphere Replications to our alternate Datacenter about a mile way from our main datacenter. That has worked well outside of resizing a VM's disk. Now we have new challenges. We would like to be able to replicate VMs on Site A to Site B and to Site C. We use vSphere Replication, no LUN replication. We would really like to use SRM to do it all, but the functionality isn't there yet. We have looked at vCloud Air to get us to site C, but the price per TB is too expensive even for higher education pricing. Does SRM play well with other Replication technologies such as Recoverpoint for Virtual Machines? We are curious to find out if we can use SRM to get us from Site A to Site B on a select number of VMs and use Recoverpoint for VMs(or something else) for a small list of critical VMs from Site A to Site C.
Does anyone have any thoughts or ideas?
Hi
i have
2 netapp storage : FAS 2552
i want to run SRM for Active -Passive Site
this 2 site MUST be synchronous replication with to storage but just have 300 Mbs speed in Fiber Optic
SRM work correctly ?
Hi,
I am developing a vSphere Web Client plug-in to talk with SRM (VMware vCenter Site Recovery Manager) 5.8 or 6.0 via its SOAP APIs.
One typical user case is that when end user selects a virtual machine under one vCenter, our plug-in will check the corresponding SRM server and list all Protection Groups for user which are protecting the selected virtual machine.
[Environment]
Protected Site: 10.102.7.78
Protection Group: srm-protection-group-7484 (PG-VSI), type=san, state=READY
Protected VM: vm-162 (Yuli_CRR_5.8_CG1_OS) / protected-vm-7543
Protected VM’s datastore: datastore-161 (snap-5824c9ba-Yuli_CRR_5.8_CG1)
Recovery Site: 10.102.7.79
Protection Group: srm-protection-group-7389(PG-VSI), type=san, state=TESTING
Recovered VM: vm-221 (Yuli_CRR_5.8_CG1_OS) / protected-vm-7426
Recovered VM’s datastore: datastore-222 (snap-7a7588ae-Yuli_CRR_5.8_CG1)
Recover Plan: srm-recovery-plan-7500 (RP-VSI)
[Issue]
The issue I encountered is that for a virtual machine (e.g. id is vm-162, name is Yuli_CRR_5.8_CG1_OS) under the protected-site vCenter, our plug-in can find the protection group (e.g. id is srm-protection-group-7484) on the protected-site SRM server if the virtual machine is protected by this protection group. But after doing test fail-over, for the corresponding virtual machine (e.g. id is vm-221, name is Yuli_CRR_5.8_CG1_OS) under the recovery-site vCenter, our plug-in can not find the protection group on the recovery-site SRM server.
Actually, on recovery site, the protection group does exist (e.g. id is srm-protection-group-7389), but the id of its protected virtual machine is vm-162 (instead of vm-221). So vm-221 cannot be found in all protection groups and hence no protection groups will be listed for end user.
[Question]
1. In test fail-over case, why the id of protected virtual machine by protection group srm-protection-group-7389 is vm-162, rather than vm-221? This makes our plug-in not working.
2. Are there any ways to allow our plug-in to know vm-221 does be protected by srm-protection-group-7389? If there are no reasonable approaches, our plug-in will be blocked by this kind of issue.
[More Info]
More details info (e.g. environment, sample code, logs), please check the attached doc.
Thanks in advance,
Eric
Hi all,
Trying SRM 5.8 in my lab before the production deployment, and I'm running into an issue configuring resource mappings. I was able to successfully pair the sites, but after I add a new resource mapping pair, I get "unable to retrieve resource mappings data" message from the GUI.
Checked the SRM logs and don't see anything relevant... Hoping that someone can provide an insight on where to look to fix this issue. Thanks!
Hi All,
I'm confused about how to use the Placeholder Datastore.. What is best practices ?
I knew that we do not need to give very big datastore for placeholder right ? For example, Is it enough 5-10GB for placeholder datastore ? What size we should use recommend ? I have 200 Virtual machine replicated .How many placeholder datastore i should use ?
Do you recommend to use datastores for placeholder which virtual machines stored?
Thanks
I'm running into an issue with configuring the Array based Replication.
On Site A:
SRM 5.8 - Build 2336305
SRA 2.3.0 for Nimble storage
Physical:
BladeSystem c7000 Enclosure G2
ProLiant BL465c Gen8 -1
iSCSI:
iqn.1990-07.com.emulex:b4-b5-2f-58-57-11
iqn.1990-07.com.emulex:b4-b5-2f-58-57-11
ProLiant BL465c Gen8 - 2
iSCSI
iqn.1990-07.com.emulex:b4-b5-2f-58-e5-79
iqn.1990-07.com.emulex:b4-b5-2f-58-e5-79
ProLiant BL465c Gen8 - 3
On Site B:
SRM 5.8 - Build 2336305
SRA 2.3.0 for Nimble storage
Physical:
BladeSystem c7000 Enclosure G3
ProLiant BL465c Gen8 - 1
iSCSI
iqn.1990-07.com.emulex:38-63-bb-37-35-91
iqn.1990-07.com.emulex:38-63-bb-37-35-91
ProLiant BL465c Gen8 - 2
iSCSI
iqn.1990-07.com.emulex:38-63-bb-37-e6-b9
iqn.1990-07.com.emulex:38-63-bb-37-e6-b9
ProLiant BL465c Gen8 - 3
When trying to configure the Array replication Site B shows it's working fine. But on Site A I get a duplicate initiator error message.
Here is the following error on Site A BL465c - 1 error:
Discover Replicated Devices xx.domain.com Duplicate initiator 'iqn.1990-07.com.emulex:b4-b5-2f-58-57-12' found in SRA's 'discoverDevices' response.
2015-06-30T10:52:57.182-07:00 [02892 verbose 'PropertyProvider' opID=1fd9ba22] RecordOp ASSIGN: info.progress, dr.storage.ReplicatedArrayPair.discoverDevices16
2015-06-30T10:52:57.213-07:00 [02892 verbose 'Storage' opID=1fd9ba22] XML validation succeeded
2015-06-30T10:52:57.213-07:00 [02892 error 'Storage' opID=1fd9ba22] Duplicate initiator ID 'iqn.1990-07.com.emulex:b4-b5-2f-58-57-11' at (43:8):
--> <Initiator id="iqn.1990-07.com.emulex:b4-b5-2f-58-57-11" type="iSCSI"/>
2015-06-30T10:52:57.213-07:00 [02852 verbose 'PerformanceMonitor' opID=1fd9ba22] Performance monitor Token 0 of lock PersistableRWLock-3175 Locked took 7.488 seconds
2015-06-30T10:52:57.213-07:00 [02852 verbose 'PersistableRWLock' opID=1fd9ba22] Releasing Write lock 'PersistableRWLock-3175'
2015-06-30T10:52:57.213-07:00 [02852 verbose 'Storage' opID=1fd9ba22] Releasing read op lock on 'array-pair-3136'
2015-06-30T10:52:57.213-07:00 [02852 verbose 'PerformanceMonitor' opID=1fd9ba22] Performance monitor Token 0 of lock PersistableRWLock-3137 Locked took 7.504 seconds
2015-06-30T10:52:57.213-07:00 [02852 verbose 'PersistableRWLock' opID=1fd9ba22] Releasing Read lock 'PersistableRWLock-3137'
2015-06-30T10:52:57.213-07:00 [02852 info 'Storage' opID=1fd9ba22] Dr::Storage::VmomiLayer::DiscoverDevicesExecutor::DiscoveryComplete: discover devices completed
2015-06-30T10:52:57.213-07:00 [02852 error 'Storage' opID=1fd9ba22] Failed to discover devices at local site: (dr.storage.fault.DuplicateInitiator)
Any help or suggestions would be appreciated. Thanks in advance.
as per the vsphere replication architecture whatever the changed block information that is sent by vsphere replication agent are captured by vsphere replication server in the form of redo logs and once the all the blocks are captured then redo logs gets collapsed but in MPIT they are maintaining it. Now my query is what is the size of redo logs in both the cases with MPIT and without MPIT.
I was make two site,but I don't know how to test ,I hope someone can support a word ,to help me test SRM ,thanks !
Hello
I'm having some trouble pairing our sites in a new deployment using SRM 5.8.
When trying to pair the sites I get the following error message:
The error refers to the SRM server on the same site as the pair operation is being initiated from. I get the same error message if I try the pair operation from either side.
Can anyone help me with this?
Thanks,
Richard
Dear All,
I have a question, we have one main production site and two disaster recovery sites. helf load is in one Dr site while half is on other Dr site in case if main production site fails. Our management wants to use SRM. Is it possible in our case, i mean one main site and two recovery sites? SRM should recover half vms on one Dr site and half on other? mean one to many, one protection and two recovery sites?
thanks in advance.