Namaste to all,
Whenever I am connecting to SRM through vSphere client, it is taking long time to connect and I am getting an error message (please see the attached image) and after 4 or 5 attempts I am able to connect. Later, it is getting disconnected automatically and once again it takes at least 10 minutes and multiple attempts to connect to SRM. I am using 5.1 version. Kindly let me know why is this happening? Thanks in Advance
It has always bugging me to know what really happens when you run a Test recovery plan, a Planned Migration and an Unplanned Failover.
Appreciate if someone could shed me some light on what does really happend when you start the above mentioned processes.
I presume all works the same...
Thanks,
Rushdi
Hello there,
I have a totally non-technically question concerning Site Recovery Manager. For Budget Planning purposes I need the price of the annual SnS Cost for SRM Enterprise as well as the SnS Cost of each protected Machine. Unfortunately I only found the list-prices for
SRM Enterprise (US$ 12375,-) and the license-cost for each protected Maschine (US$ 495,-) but NOT the cost for SnS which is also required.
Can anybody help me out?
Thx...Andy
Hi Vmware family,
Right now I am working on SRM, I deployed VR appliance successfully, but when I am trying to configure it (by clicking on the link in vSphere replication tab), the webpage displays an error saying 'The page cannot be found,' so experts kindly let me know what is preventing me from configuring the VR appliance? What is the solution for this? Thanks in advance.
HI Gurus,
I am in the middle of upgrading SRM 5 to SRM 5.1 for vSphere replication.
I am trying install and register the VR appliance 5.1.
On the configuration tab I have populated the info: and tried to generate the certificate and start the service.
It comes up with the following msg.
Self-signed certificate installed successfully.
Warning: Bad service status: execv() arg 2 must contain only strings.
The info i have populated are as follows:
VRM Host: vrm host ip address
VRM Site Name: virtual appliance of DR site (FQDN)
vCenter Server Address: DR vCenter server address FQDN
vCenter Server Port: 80
vCenter Server Admin Mail: administrators email
Thanks in advance!
I'm using SRM 5.0 in my environment with ESXi 5.0 U1 as hosts and two vCenter 5.0 U1 as management without Linked Mode in two sites. I prepared my environment to run a Planned Failover for migration. 7 VMs replicated with Recovery Site without any issues. A few hour before starting Migration, test in bubble network was implemented without any issue. But, when Recovery button pushed for Failover, 4 of 7 VMs migrated and 3 VMs failed with below error (Immediately) after successful sync.
Error - Error creating failover image from group instance 'RGID-daad650c-1079-4aa5-af7d-33c806ba9b27' of group 'GID-2c4e4488-c1d7-4c88-b4ea-2416187e21bd' on VR Server 'localhost.localdom' (address '10.13X.X.X'). Can not determine datastore for datastore UUID '50a090a7-8e9ba1cc-db7f-00237d5fe0b8'.
any ideas?
Hi Guys,
I am trying out SRM 5.0 and everything seems fine. However, I noticed that there are some difference in status icon.
behind is the vCenter accessed from a remote machine (with flower-like icon), on top is the vCenter accessed directly from the vCenter Server (with lightning icon). Can someone explain this?
Thanks,
Marc
I am getting the following attached error when trying to configure the replication for a particular vm. this error occurred in a lab environment. I successfully ran a recovery process to the DR site once and after that re protect operation also succeeded. and then i tried to run the recovery process from the production site to DR again. at that time i got this error. please help me to resolve this.
thanks
Hello Everyone,
I am new with SRM and I am planning to run a DR test with for one especific production environment with 9 virtual servers. After the recovery we will have some application functional validation that will be performed by the application owner and some key users, then we will need to failover the application back to our production datacenter and we are struggling to find a way to failover back without overwriting the production data. Is there any feature on SRM 5.0 that it will failback the servers within the original RPO and discard the chages made in the recovery site? I did some researches and I found that we can only do that through SAN side by taking a snap of the original LUN before start recovery.
Thank you so much!!!
VMworld 2013... see you there!!!
Rafael Campos
I have configured SRM 5.1 with Vcenter 5.1. After this I have deployed vsphere replication appliance also but while configuring this appliance I have selected configuration mode as "Configuration using embedded database". On this configuration page I am not seeing anywhere to put vcenter credentials. I have put vcenter server address , port and admin mail id. And after this when I am clicking on save and restart service. I am getting error "vCenter Server connection failed: Cannot complete login due to an incorrect user name or password." I am not sure from where it is picking vcenter username and password and where can I specify this information ?
Hello,
Main Site, I have 3 hosts 5.1 update1a with attached 16 RDM’s in 3 cluster MSCS. I’ve applied the KB 1016106 fix, and it worked.
When performed with 5.1 SRM failover and failback to rescan the HBAs take long and hangs esxi hosts. At boot takes 3 hours to do.
When checking perennelly-reserved parameter that I am returned to be false.
The SRM 5.1 has a mechanism that does this? Help
regards
Has anybody else experienced issues with SRM and customising IPs?
I have 24 VMs which I recover using SRM. When I'm not using the customise IP option, they recover fine besides manually entering their network settings. However when I customise each VM with their appropriate IP settings, the recovery always fails.
I have found the issue to be SRM ignoring the priority groups when it comes to these activities for each VM:
- Configure Storage
- Configure Test Network
- Guest Startup
- Customise IP
- Guest Shutdown
Then the VM priority order actually works from this point for:
- Power On
- Wait for VMware tools
After SRM finishes the "Create Writeable Storage Snapshot" step, it then completes ALL of the steps highlighted in red for every single VM at once! This is causing the cluster to overload and pretty much cause every VM to fail.
VMware have acknowledged this as an issue and suggested I try the work around of using blank steps with a prompt to resolve the issue. However it doesn't fix it. I've successfully ran several recovery jobs using Customise IP with only 3 VMs and it works perfectly because it isn't starting many VMs at once.
I have raised a feature request with VMware however I've been told it is too late to be looked at for the up coming release. So it 'might' be addressed in the following one....if they consider fixing it.
The way I see it at the moment, if customise IP can't even work with 24 VM's (SRM starter pack is 25) then it is completely useless. It's a shame because it was one of the main selling points as to why I picked a VMware + SRM solution.
Has anybody else experienced this issue and if so, do you have a temporary fix for it?
Regards
Leigh
We installed SRM with vSphere Replication. Our first single VM replication job has been stuck at 0% - Initial Full Sync for over 24 hours.
How should I troubleshoot?
Thanks,
Sang
Hi all,
I am looking for some help on SRM 5.1 with recoverpoint instalation.
I alredy instaled SRM 5.1 on both sites and the two sites paired now. I am confused about the Recoverpoint version works with SRM 5.1.
Please post the link to download the approperate EMC Recoverpoint version.
I am looking for some updadated document on SRM with recoverpoint instalation. I alredy got below mentioned two but it is too old.
I am getting an error every time I login in to vcenter and connect to SRM plugin. I am attaching the screen shot, then I have to type my login credentials for pairing the sites.
Thomas
I'm running SRM 5.1 with vCenter 5.1 with EMC Recover Point 3.5 SP1.P2.
When I do a test failover or a planned failover. It fails because the ESX hosts on the DR side are unable to mount the datastores. When I log into EMC Unisphere the ESXi hosts on the DR side are not in the storage group. If I put the hosts into the storage group I can run the failover.
I was under the impression that you wouldn't have to do this and the Recover Point SRA/Recover Point would talk to the VNX SAN and add the hosts to the storage group automatically on failover.
EMC is telling me that the SRA won't do that. VMware is telling me that it should do it.
Anybody else integrated Recover Point into SRM before?
So far I have been using SRM with the fat Windows client and SRM plug-in. (Version 5.1)
Has anyone been using SRM with the Web client? I can't seem to find how to (eg) create Protection Groups and test failover. Is this even supported in the Web client yet (is there some "plug-in" for it?), or do I need to continue using the fat client for SRM activities?
Thanks.
When I add a prompt as a Recovery Plan Step it does not wait to be dismissed before it continues. The timeout option is greyed out and set as 5 minutes by default. It does wait for 5 minutes before it continues but there doesn't seem to be a way to increase the timeout. It merely sets it back to 5 minutes. Can anyone help?
Hello,
Currently we are trying to setup a new DR site with SRM that is not a flat network with our main site. The setup is as follows
10.70.10.x /24 Main site
Active Directory Server/DNS (AD01)
Active Directory Server/DNS (AD02)
vCenter Server (VC01)
SRM Server
Exchange Server (EXCH01)
All other VM's
10.70.20.x /24 DR site
Active Directory Server/DNS (AD02)
vCenter Server (VC02)
SRM Server
Space for recovered VM's
Setting up the replication and recovery plans is fine but I was wondering what the best practice was when changing the IP's and if there is any other ways around this like DNS masking or something. From the reading I have been doing it would appear the best way to have SRM set this up is do an IP address change during the failover and then have it run the DNSscript to change the DNS records on the active AD controller. My concern with this is the Exchange server as the rest of the servers won't have a problem with the IP address change/ DNS change and the AD01/AD02 will not be replicated. Also while reading up no the IP change / DNS change it would appear there is no way to actually run a Test Recovery Plan with DNS change as the changes are always made to the production DNS servers even though the rest of the VM's will be in the isolated network SRM creates for a test recovery plan.
So to recap my questions are
1.) Is there anyway to get around the IP change when your DR site is not on a flat network/same network
2.) How does Exchange handle the IP address change / DNS change
3.) Is there anything special that would have to go into the DNS script if we do change ip / dns for exchange or for testing
4.) Is this the most efficient way to accomplish this DR failover
Thanks
Is it possible to change the hostname of the server hosting SRM? We are looking to migrate from physical to virtual and the plans were to standup a new vcetner and srm server. Trying to understand implications on the SRM side of changing the hostname.
Hi All,
I am trying to enable vSphere Replication (VR) on windows VM ( server 2012), everything works fine but Guest OS Quiescing is grayed out.
Vcenter and VR in Base and DR is version 5.1.1.
Any suggestion will be great help.
Thankyou...