Hi,
We have HP 3Par storage and some of the LUNs are configured replication (storage base replication). recently i have installed SRM successfully on both sites (Main-DC and DR-site).
the problem is when i export the LUN from DR-site storage (replicated LUN) to Disaster recovery vSphere host, it fails to attach/mount on the server. i have installed the HP SRA (storage replication adapter on both sites).
is there any further requirements or configurations.
thanks,
Hi everyone,
I'm having issues with this SRA version 2.1! The installation went just fine on both sites. Pairing and mapping is functional between two VCenters.
I have VCenter 5.1, SRM 5.1 running together on a W2K8 R2 on both sites.
After the SRA installation, i tried to "Add Array Manager" on VSphere Client SRM GUI, and i got the error: "Unable to find any array script (SRA) files. You must install SRAs before adding an array manager"
If i try to "Rescan SRAs" i have this error message: "Failed to load SRA from 'E:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/array-type-recoverpoint'. SRA command 'queryInfo' didn't return a response"
Tried to restart/reinstall several times, but it didn't work!
I have exactly the same symptoms on both SRM servers!
Did anyone face this problem?
Thank you
Hello All,
I would like to know your thoughts around protecting SQL Server VM's using SRM.
Is this something that is supported and is anyone actually doing this?
I understand that SRM will successfully bring the VM online but SQL might come up in recovery mode and we would have to rely on SQL backups to get things back.
Am I correct in my understanding.
Many thanks,
Evan
We are running VMware SRM 5.0 and RecoverPoint 3.4 SP2. Running vCenter 5.0 and ESXi 5.0. The problem we are getting and the answer from VMware SRM and EMC RP support are conflicting each other. Our SRM failover process failed due to DR replicated LUNs were not detected during HBA scan. VMware support said that the Replicated LUN does not have to be added the VMware Storage Group on our VNX5300 (DR). The LUN is only added to the RP Storage Group. SRM/RP will present the luns in VMware as part of the SRM failover process. EMC tells us that the replicated LUN must be present in both VMware and RP Storage Group.
The failover process does not complete until we added the replicated lun into the VMware Storage Group. However, we previously tested other SRM protected LUNs and this was never required. Can someone provide the specific details on the RecoverPoint requirement to add the replicated LUN to the VMware Storage Group?
thanks
Hello,
I use vSphere 5.0 U2 with SRM 5.0. Storage is a NetApp V3210 snapmirrored to a FAS2240-4.
I did a recovery in SRM and I found that the datastore in vCenter was renamed snap-xxxx-datastore_name. Why was the datastore renamed? Can I prevent SRM to rename the datastore? Is it possible to get the datastore named back to what it was originally? If yes, how can I do it?
Thanks,
Frank
I am running windows server 2012 trying to install SRM 5.1 but the install keeps failing with error:
Failed to update Perl installation directories.
Details:
Can't open perl script "E:\Program": No such file or directory
I have referenced these knowledge base articles and setup still fails:
Server is standalone, not running anything but VMtools. Fully updated with windows updates, UAC is disabled.
Anyone else know how to fix this?
Curious - since upgrading to SRM 5 we have seen additional snapshots (additional in that they are in addition to the usual replication/snapshots that have long been functioning) in our P4000 system - are these "extras" only related to the "synchronize storage" option of the new recovery plan test process? I presume so - they do take up space though and have not yet gone away automagically? Any ideas?
Hi All,
we have already SRM 5.1 running with vSphere replication from two protection sites (SiteA / SiteB) to one recovery site (Site C). The recovery site is a cold site, that means we have only two small host running which manage the replication. For real DR or for rehearsals is the procedure to build hosts, put this to the cluster of the recovery site and start the DR plans. I know that this is not the best solution, but this is the process.
Now, we want to keep this solution for the most VMs but additional connect one of the protection site (Site A) with SRM for some high production machines to the other protection site (Site B) which will be then the recovery site for the high production machines. That means SiteB will be a protection site for hosted machines and recovery site for the high production VMs from SiteA.
Is this possible and supported with SRM 5.1 and vSphere Replication?
Hi,
Is it at all possible to add steps to clean up process? I have no experience with previous versions of SRM but my colleague made use of them and we seem not able to do it in 5.1.1.
This 5.1.1. install is fresh and no upgrade from 4. It should not be a permission thing either as I have tested with account that has full SRM privileges.
Currently we are adding a clean up step to end of test plan but that is rather messy.
Any ideas?
Hi. I will be starting an SRM deployment soon with 5.5 and Dell Compellent using their SRA. However what I have been reading leads me to believe that when this is install, I will not be able to vMotion nor Storage vMotion.
From the Dell Compellent SRA documentation:
Dell Compellent SRA Limitations
The following features are not supported by the Dell Compellent SRA:
And from the SRM documentation:
If your storage array supports consistency groups, SRM is compatible with vSphere Storage DRS and vSphere Storage vMotion. You can use Storage DRS and Storage vMotion to move virtual machine files within a consistency group that SRM protects. If your storage array does not support consistency groups, you cannot use Storage DRS and Storage vMotion in combination with SRM.
So am I reading right that if I have SRM installed, any protected vms cannot be vmotioned or storage vmotioned??
Thanks!
I had to uninstall reinstall Virtual Center in my primary site last week. This broke SRM.
This error was in the logs on the SRM server:
Vmacore::Exception' "Registration with the local VC server is not valid"
[00928 error 'Default'] Application error: Registration with the local VC server is not valid. Shutting down ...
I've beeen trying to reconfigure SRM without success using the commands from this KB article:
My question is which certificate should I be using the thumbprint from, the Vcenter servers, or the certs for the SRM servers themselves?
I have a scenario where we have a sql cluster that will be protected by SRM and replicated to the DR site. What issues if any would be encountered during a DR event if Vcenter and SRM databases are installed on the cluster that will be shutdown replicated and restarted in the DR site? I have always installed these databases on the local non-replicated Vcenter servers.
Would the database going down cause a issue with SRM?
Thanks!
Design is v7000 to v7000 Unified.
I created a full administrator level user "sradmin" on both SVC. I logged in and validated that athentication is working.
I checked that both CIM intefaces (TCP port 5989) are open and listening on both SAN controllers. I have a test SRM lun allocated two different hosts in two seperate datacenters hosted by two seperate vCenter servers. All the rest of SRM configuration has gone well but when I go to "Add an Array Manager" I get the below error
SRA command 'discoverArrays' failed. Invalid Array ID.
Refer to IBM SAN Volume Controller troubleshooting
The IBM documenation on this topic http://pic.dhe.ibm.com/infocenter/strhosts/ic/topic/com.ibm.help.strghosts.doc/PDFs/SVC_Adapter_for_VMware_VC_SRM_2.1.0_…
Page 14 is 90% of all that matters and no real detail.
...lacks details about how the application (SRM Agent: IBMSVCSRAUtil ) is setup. It launches and is vary vague as to fields and terms are not even correct (refers to "MDisk Group ID" which I can only surmise that this is referring to "mDisk Pool" name.
The Clint then as an "OK" button which you click and nothing happens. I don't know if this is expected or not. It go to next screen as noted in PDF but no matter what I input into the tiny boxes.. nothing changes..... though it now does show as having SRM agents to SRM (see attachments)
Hopefully someone has this working and can clarify what I am missing.. I am sure it is something simple.
Hello Everyone,
I would like to ask if I can setup a 1 Primary Site to 2 Recovery Site using SRM array based replication? Is this a supported configuration?
Thanks in advance!
Hi
I have been running VMWare Site Recovery Manager for a while, but now my trail license has expired.
So i have bought some license for "vCenterSite Recovery Manager (VM)", i have bought 50 VMs license.
I have installed the license on both the protected and DR site, and restart
"VMware vCenter Site Recovery Manager Server" service on both site.
But still when i want to configure a new VM for replication i got "There are not enough lkicenses installed to perform the operation"
Is it the wrong license i have bought?
Regards Kenneth Dalbjerg
I'm using VDR (2.0.1.2374) to make a backup of my virtual machines (Windows 2003 and 2008 and Linux - about 100 VM´s) and identified that the FIRST backup of some VM´s is incremental. I've deleted ALL backups, formatted disks destination ... unsuccessfully. How can I restore an entire VM if I only have incremental backups? How do I force the execution of a FULL backup?
Hi All,
I am currently exploring the possibility of using Site Recovery Manager for database DR scenarios.
Before I go any further and actually try running some scenarios, I would be interested if anyone of you has attempted to do the same and if you actually managed to get past the disaster situation, i.e. with primary VM being [shut] down and activating the DR VM.
The other important aspect I would be interested in is the certification: is the Site Recovery Manager certified for recovering VMs running databases?
And if yes, which databases is it certified with: Oracle 10/11, SQL Server 2005/2008, DB2 9.x, etc?
If the answers are well known to my question, please just point me to the right source through a link - that should be enough.
Thank you,
Dan
Hi all,
I have 2 IBM SVC (6.2) in both protection site and recovery site, after installed and configured SRM, the "test failover" worked well, however the "failover" failed which returned the following message:
Error: failed to promote replica devices. SRA command 'failover' didn't return a response.
I have also tried vSphere+SRM 5.0 and 5.1, SRA 2.1 and 2.2, non-preconfigure and preconfigure in SRA, still failed.
Is there anyone has some ideas about this issue, thank in advanced.
Hallo.
Right now I'm considering SRM implementation for couple of database virtual machines (mssql, oracle - linux and windows, progres - linux). I know that in case of recovery both storage mirroring (sync) and srm software mirroring (async, min 15min RPO) will startup machines and database in inconsistent state. I know that database mechanism probably will recover the database and it should work. But this behaviour is very different from behaviour of standby database where you can always trust the second database. It is very difficult to convince db adm. to switch their system to SRM.
So I need some arguments and well documentations of best database practices in SRM environment.
Hi,
I have a site which has been running SRM 4.0 using array based replication on IBM DS4700 arrays. I'm now attempting to update both sites to vSphere 5.x and SRM 5.x.
The DS4700s have been upgraded to Firmware version 7.60.63, which is the latest available from IBM for the DS4700. According to VMware's compatibility site, the latest version of SRM supported is 5.0.1, and the latest SRA is version 05.00.3550.0017.
When I go to the SRM Downloads page, there's a message regarding SRAs:
"Storage Replication Adapters for this release are available for download from the latest maintenance release for this version of Site Recovery Manager."
This is SRM 5.0.2; which allows me to download ONLY version 05.10.3500.0016 which, according to its user guide does not support DS4x00:
"This SRA supports the following IBM DS Series storage subsystems:
• DS5300 / DS5100(FC only)
•DS5020 / DS3950 (FC only)
•DS3500 (FC and iSCSI)"
For the record, I tried it and got a lot of XML errors.
I think VMware has only recently changed the website for downloading SRM, as last week I was able to find and download version 05.00.3550.0021 for the DS4800.
Can anybody help me out with IBM DS3000/DS4000/DS5000 SRA version 05.00.3550.0017? Or can VMware look into making these older SRAs downloadable again?
Cheers,
Chris
