Hi Guys,
When we run Test Recovery , in documentation it says storage snapshot will be taken and all HBA scan will be started on all ESXi servers at recovery site.
I did test recovery plan in our LAB it just created new Folder and add vmdk files to this folder. Virtual machine which was started in Test Recovery hard disk
pointed to this new folder.
No scan was run to find new storage and test recovery plan did not create any new snapshot LUN.
Hey all,
Firstly apologies for the lack of information or if this has already been asked...
A customer has a Linux vm with two vNICs (Production (192.168.x.x) and Management (10.100.x.x in the Production site and 10.101.x.x in the DR site)). When the vm is failed over SRM has been setup to change the management IP but NOT the production IP.
The hosts file looks like this prior to fail over:
[root@SERVER1 ~]# cat /etc/hosts
127.0.0.1 localhost
::1 localhost
192.168.0.1 SERVER1
10.100.0.1 SERVER1-mgt
and like this after fail over:
[root@SERVER1 ~]# cat /etc/hosts
127.0.0.1 localhost
::1 localhost
192.168.0.1 SERVER1
10.100.0.1 SERVER1-mgt
10.101.0.1 SERVER1
When the VM is in the DR site the customer is reporting problems connecting to the VM/App and if they manually edit the hosts file to remove the 10.100.0.1 entry and add "-mgt" to the 10.101.0.1 entry the connection issues are resolved.
Apologies if this is an obvious mistake that has been made, however is there a way to stop SRM adding the new entry to the hosts file or only editing the entry suffixed with "-mgt"?
Thanks,
James
Hi
When using VMware HA and SRM, can the datastores that SRM will failover to the recovery site, host the HA heartbeat ? Can locking issues arise when HA is using the datastore and SRM wants to failover the datastore?
Gabrie
I have my VMware infrastructure in place and working fine. I recently setup SRM 5.0.1 and have my vCenter servers linked. We have 2 EqualLogic arrays. All licensing is in place. Replication is working.
I have one LUN with one VM that I am testing with. I am using array-based replication and I have the SRA installed and configured. I can successfully "Test" a recovery plan and "Recovery" a recovery plan. I cannot "Reprotect" a recovery plan. I have tried making changes to the config on everything I can think of, I have removed and reinstalled a bunch of things but I keep getting the same failed result at the same place (step 1). The error I get is this:
Error - Failed to reverse replication for device 'iqn.2001-05.com.equallogic:0-8a0906-6d36aa101-acf001baf644f75a-carbon-syr-jsmith.1'. SRA command 'prepareReverseReplication' failed for device 'iqn.2001-05.com.equallogic:0-8a0906-6d36aa101-acf001baf644f75a-carbon-syr-jsmith.1'. Replicate back task failed or not started Use the Group Manager to check the failback or replicate back task, remove the failed task
I cannot figure out what is wrong so if anyone can help it would be appreciated. I do not see anything in any logs that I can find. I am stuck and do not know where to look. Replication is enable for both inbound and outbound on both SANs. Not sure what to put up here so let me know what I can post to help.
Thank you.
To add moro information, this is from the report (screenshot attached):
| 1. Configure Storage to Reverse Direction | Error - Failed to reverse replication for device 'iqn.2001-05.com.equallogic:0-8a0906-6d36aa101-acf001baf644f75a-carbon-syr-jsmith.1'. SRA command 'prepareReverseReplication' failed for device 'iqn.2001-05.com.equallogic:0-8a0906-6d36aa101-acf001baf644f75a-carbon-syr-jsmith.1'. Replicate back task failed or not started Use the Group Manager to check the failback or replicate back task, remove the failed task | 2012-03-30 13:56:44 (UTC 0) | 2012-03-30 13:56:56 (UTC 0) | |||||||||
| 1.1. Protection Group syr-jsmith protection group | Error - Failed to reverse replication for device 'iqn.2001-05.com.equallogic:0-8a0906-6d36aa101-acf001baf644f75a-carbon-syr-jsmith.1'. SRA command 'prepareReverseReplication' failed for device 'iqn.2001-05.com.equallogic:0-8a0906-6d36aa101-acf001baf644f75a-carbon-syr-jsmith.1'. Replicate back task failed or not started Use the Group Manager to check the failback or replicate back task, remove the failed task | 2012-03-30 13:56:44 (UTC 0) | 2012-03-30 13:56:56 (UTC 0) | |||||||||
| ||||||||||||
I know is sounds silly but if my protected site disappeared in a disaster, will I be able to bring up my protected VMs in the recovery site? Of course provided that I have the necessary infrastructure available in the recovery site.
Thanks in advance
Hi all,
Anyone to have expirience with new code of IBM Storwize v7000, level 7.1 with SRM 5.1 ?
Thanks,
HI Group,
I am trying clone our prod 2012 Domain Controller so that we can use it in our Test Lab which is isolated from production
We tried to clone the DC , copy VM to Lab network, started the VM but DC is not working as normal. So we seized all FSMO roles
and added registry key = Repl Perform Initial Synchronizations =0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
Value name: Repl Perform Initial Synchronizations
Value type: REG_DWORD
Value data: 0
Still it is not working, for example when we open Active directory users and computers we get error Naming information cannot be located.
Is cloning of DC is supported for DC 2012 for test lab use in VMware VSphere 5.1.1?
Hi guys
We currently have SRM 5.1 running with RPA 3.5 SP2 on EMC VNX. My question is, would is the impact to SRM, the protected VM's and the actual device, should the storage admin change the RPA password for the username managing the consistency group? Also, what is the impact should he change the name of the consistency group?
What procedure is involved? i.e does he have to deselect the ownership of SRM from the consistency group, then rename / change password?
and as aforementioned - the impact
thank you kindly gents
Looking to migrate from one instance of SRM to another. Trying to understand if there is a way to backup a recovery plan and restore it without the SQL db side of things? Also would be moving from 4.1 of SRM to 5.1
AFTER INSTALLATION GETTING ERROR
C:\Users\Administrator
aFTER THIS ERROR NOT OVING FORWARD
So I'm just trying to plan for contingencies. There is some evidence that a vcenter 5.0 system has DB issues - it may perhaps require that we "start from scratch" to repair the db (things are not that bad right now, but there are a couple odd things that I don't know how to fix, so I just want to plan ahead "in case" support tells me somewhere down the line, that I need to do this).
Is it possible to "delete and re-create" the vcenter DB and then just "reconnect" SRM to it, without losing all the SRM config and having to re-install it also from scratch?
If it is possible - how?
in the event that SRM has configured autofailover, Does SRM require similar hardware (in term of model, processor) for both Primary & Secondary Site?
Hi all -
I recently deployed a multi-site SRM 5.1 configuration. (2) sites are failing over to a DR site. All sites appear to be functioning okay - the VM placeholders are on the DR site and I don't see any issues. However, on the (1) production site, (2) plugin entries show up when I attempt to load the SRM plugin. Here's what it shows:
When I load either of the SRM IDs, it loads the same SRM site. I tried restarting the vCenter server, SRM server, and uninstall and reinstall the SRM extension on the vCenter server which didn't help. I'd like to somehow remove the <default> entry option when I load SRM. Is there any way to do this easily? Thanks!
Just a quick question.
Can SRM produce syslogs to a log Server?
Obviously there aren't any visible switches... however can it be enabled via CLI or other means?
Hi all
I am attempting to install the pluggins for SRM so I can start using SRM and testing it before putting it into production.
Our EMC colleague gave me 3 pluggins to install.
These two had to be installed on the vCentre which was done successfully:
emc-vsi-pm-5.3.0-vmware-vsphere-WINDOWS-x86
emc-vsi-sv-5.3.0-vmware-vsphere-WINDOWS-x86
I was then given this and told to install once the top two where installed:
emc-vsi-sra-5.3.0-vmware-vsphere-WINDOWS-x86
But of course it doesnt work and returns message which is attached.
We had an EMC person which was suppose to assist us with this but this did not happen and due to time constraints I have to continue and try it myself.
Our set up
vCentre 5.0 in primary site
vCentre 5.0 in recovery site
SRM 5.0 installed on own server in primary site
SRM 5.0 installed on own server in recovery site
Both sites are linked through SRM successfully.
EMC symmetrix
I have mapped folders, datacentres in the SRM between sites but I am now at the array replication part.
Any help would be great.
Hope I have covered enough information...
I’m wishing to upgrade from SRM 5.01 to 5.1.1. My VC is
currently 5.01 and will also be going to 5.1.1.
I note from the product interoperability matrix that Vcenter
5.0 will only support SRM 5.0, 5.0.1 & 5.0.2 so somethings going to break
one way or another as if I upgrade VCenter first to 5.1.1 the that only works
with SRM 5.1 & 5.1.1.
So the question is, do I upgrade VC to 5.1.1 first then
upgrade SRM to 5.1 and then be able to upgrade it to 5.1.1 immediately after (SRM
cant go from 5.0.1 straight to 5.1.1 but it can go to 5.1) or do I upgrade SRM
first to 5.1 then upgrade the VCenter? I’m thinking the latter for it means at
no point should SRM have an issue with the installed version of the Vcenter.
Anyone see a flaw with this?
Hi all -
I recently deployed a multi-site SRM 5.1 configuration. (2) sites are failing over to a DR site. All sites appear to be functioning okay - the VM placeholders are on the DR site and I don't see any issues. However, on the (1) production site, (2) plugin entries show up when I attempt to load the SRM plugin. Here's what it shows:
When I load either of the SRM IDs, it loads the same SRM site. I tried restarting the vCenter server, SRM server, and uninstall and reinstall the SRM extension on the vCenter server which didn't help. I'd like to somehow remove the <default> entry option when I load SRM. Is there any way to do this easily? Thanks!
Just a quick question.
Can SRM produce syslogs to a log Server?
Obviously there aren't any visible switches... however can it be enabled via CLI or other means?
Hello,
Im trying to figure out a way to failover with SRM without changing network settings of the virtual machines.
Lets say there are two data centers both have a single ISP connection (bgp multihoming) and a darkfiber(layer 3) running between data centers.
Each data center has a vCenter Server with SRM on it and use array level replication with NetApp snapmirror.
In the scenario where protected data center has a power outage and we start the recovery process on the disaster recovery site.
All the virtual machines are now running on the disaster recovery site all good and well.
The power outage on the protected site is over and the ESXi server are starting up again.
How does SRM deal with the virtual machines that are still on the protect site (possibly running) which are now also running on the disaster
recovery site? This would result in ip conflicts and a split brain scenario. Does anyone have a answer or tips concerning this problem?
And is there any automated communication between the SRM servers after the protected site comes back online?
Kind regards,
Jayson
Hi, good day to all of you..
Does anyone's here ever implemented or tested Oracle RAC protected with Vmware SRM ?
Does VMware SRM 5.1 support Oracle RAC?
As i know, the RAC VMs shared they virtual disk to another RAC VMs. in my configuration the RAC-B VMs had 7 virtual disk mapped to RAC-A VMs and all works fine in production environment and they've plan to protect this RAC VMs with VMware SRM 5.1. we are using Array Based Replication with EMC RecoverPoint as the SRA.
When i try test failover my protection group which is containing those two VMs, the RAC-B VMs not able to start with the following error
The mapping virtual disk prevented the VMs from boot up, and there is no snapshot either from the RAC-A or RAC-B.
Then i edit the VM Start up action from Recovery Plan, im setting the RAC-B to not power on at recovery site. and manually map the virtual disk after test failover, and the RAC-B still can't booting up.
Please give me some enlightenment, how to map the virtual disk after failover to recovery site.
Thanks Before
Rgds
Dika