Hello,

Trying to install NetApp SRA in SRM.  SRA detected the NetApp controller at the remote site but I won't at the local site.  I always get this error message : Failed to load SRA from 'C:/Program Files (x86)/VMware/VMware vCenter Site Recovery Manager/storage/sra/ONTAP'. SRA command 'queryInfo' didn't return a response.

I have tried uninstall/reinstall SRM, SRA, Perl : nothing as changed.  If anyone have an idea about what could be the problem, it would be great to share it over here.

Thanks,

Hello,

Standard vSphere 5.5 environment, 1 vCenter server based on a Windows 2012 server.

1 Datacenter, sites as folders as they are connected via 1Gbit connections. ESXi hosts have Enterprise license.

It seemed a good idea to use the standard vSphere replication to create a copy of our single vCenter server to our backup site.

vSphere replication is replicating several "critical" VMs with all of the data to the backup site. Less critical servers are covered via a standard backup tool.

I now have a chicken / egg problem.

I need the webinterface to manage / restore the replicated vCenter server

I need a vCenter server in order to use the webinterface.

How does the full SR suite cover this problem?

Or do I need to fall back on my standard backup tool to backup and restore the vCenter server?

Bonno Bloksma (VCP5)

Hi all,

I'm fairly new to SRM but have been plugging away setting up a new environment which is using:

vCenter 5.5 u1  (Both Sites)

Solutions Enabler 8.0.1.0-1953

EMC SRDF Adapater (SRA) = 5.6.0  VMAX 20k

EMC SRDF SRA Utilities (VSI) = 5.7.0.2

SRM = 5.5.1.8569

I've been following documentation provided by Cody Hosterman  ~which is superb and has gotten me almost to the end.  I've been able to successfully fail over (Recovery) a VM using a test Recovery Plan from Site A to Site B. It worked great.

We are not using TimeFinder (not licensed) and so when we perform a recovery the expected behavior happened that the SRDF link has been broken. The state of the R1 device at Site A has become Write Disabled. The R2 device in Site B has become Read/Write and the state of the device group is in "Failed Over". This is in Asynchronous SRDF mode.

Upon trying to "Reprotect" the group, I see errors relating to configuring the storage to reverse direction.

http://i.imgur.com/zWiGtT5.png

I've checked the EmcSrdfSra log as suggested on the now primary site SRM server and it appears that there is an error shortly after a new consistency group is created.

http://i.imgur.com/5hZT8HQ.png

I've raised a support call with EMC with this directly as a first port of call but it is in it's infancy so I thought I'd ask if anyone has any clue what might be going wrong here. I've exhausted my googleFU skills and am at the stage of trying to get some experienced eyes on the issue. I'm happy to provide more information if needed or answer any questions anyone might have.

Really hope someone can assist!

Thanks!

Ryan

Hi Everyone,

I have a one-site setup with vSphere 5.5, VSAN and NSX 6.1 deployed. There are two separate clusters: one for the management VM's and another for workloads. Currently I'm trying to make this infrastructure more resilient. We decided to use another site and deploy SRM 5.8 in a/p scenario. The requirement is to protect only workload VM's and not the management components. So, now I'm wondering what would be the best approach? Should I deploy a separate VCSA in the recovery site along with NSX Manager and Controllers? Or maybe we can just include only the NSX components in the recovery plan, power them on in the case of site failure, and use scripts or Orchestrator workflow to set the networking up?

BTW, I'll be using the Replication appliance with SRM.

What are your thoughts?

Thanks

KH

Buenas noches.

Quisiera saber que se debe configurar despúes de instalar SRA en los sites de Producción y Contingencia de SRM.

He visto los manuales e indican que se debe ejecutar srautil y completar ciertos valores; pero no entiendo que valores se deben colocar o que significa realmente en la pantalla siguiente:

Es realmente necesario configurar esos valores?  que hace el SRA? y esto reemplaza a las tareas de Test, recovery y reprotect de un recovery plan de SRM ?

Una consulta adicional; cuando se realiza el paso de Recovery, se detiene automáticamente la réplica de storage? El Reprotect invierte automaticamente el orden de replicación? o hay algunos pasos adicionales a realizar?

Gracias.

Recently upgraded to 5.8.1. and am attempting to take advantage of the new IP Rules and am noticing during some test recoveries that VM's are getting the same IP addresses assigned to them.  Its only happening in 20 % of the cases, but am at a loss as to why its assinging the same to different VM's.

Just curious if anyone else has experience this?

Hey guys

Currently have two sites, both using vCenter appliances and both have a Windows host for SRM 5.8. Do I install the SRA adapter on the SRM host or is it even possible to install it on the vCenter appliance since the SRA adapter is a SuSE host? Any input would be truly appreciated.

Thanks

Dear All,

Here is our setup upgraded from vSphere/SRM 4.1.

vSphere 5.5 Update 2

SRM 5.8

EMC Clariion and Mirror View Array

We are running SAP on VM protected by SRM. SAP VM got 4 VMDK vDisks attached to it. These 4 vDisks comes from 4 different datastores in turn 4 LUNs from storage. All these LUNs are put into single consistency group at array level to maintain data integrity.Now the issue is with Test DR. In 4.1 we do create snapshot in array manually and keep it disabled for SRM use. But in latest version its automatically creating snapshots at array level during Test DR via SRA commands. Fine enhancements!

But as I observe these snapshots for replicated LUNs are creating and getting committed one by one which means they have time difference when the snapshot is created. SAP application in VM when we start checking some time stamp accross all volumes. As it has differences Oracle database refuses to start (at least this is what I understand from application team). We have contacted EMC/VMware. VMware clearly said it is not in hands of them and pointed to EMC. Now the best part if EMC saying this is very special case and they dont have any solution in hand. This scenario was working perfectly under vSphere/SRM 4.1. Now customer is going mad after upgrading their setup!

Am I doing something wrong here in Test DR for SAP? How this can be specials case? SAP on VMware is not any simple application to ignore or to put generalize statements like its simply not there! If it is the case what EMC is saying this will affect all customers running SAP on VMware and discourage them to go after VMware/EMC duo!

Please share your thoughts and suggestions.

Thanks!

Warm Regards,

Hari.

Hi,

after installation of SRM I cant see the SRM icon in Web client. Then I investigated this issue and the problem is, that SRM service stops in few seconds after start.

In SRM log I see this error:

2015-03-13T09:57:55.221+01:00 [04928 info 'Vdb' ctxID=5ed8ea32] GetConnection: All existing connections in use; allocating new connection.

2015-03-13T09:57:55.221+01:00 [00984 verbose 'DrTask'] Task 'dr.storage.StorageManager.reloadAdapters0' completed (no result)

2015-03-13T09:57:55.221+01:00 [00984 info 'DrTask'] Work for task 'dr.storage.StorageManager.reloadAdapters0' completed - new state 'success'

2015-03-13T09:57:55.221+01:00 [00984 verbose 'PropertyProvider'] RecordOp ASSIGN: info.state, dr.storage.StorageManager.reloadAdapters0

2015-03-13T09:57:55.221+01:00 [00984 verbose 'PropertyProvider'] RecordOp ASSIGN: info.completeTime, dr.storage.StorageManager.reloadAdapters0

2015-03-13T09:57:55.221+01:00 [00984 info 'TopologyConfig'] Using drTaskCleanupTime '60'

2015-03-13T09:57:59.112+01:00 [04928 panic 'Default' ctxID=5ed8ea32]

-->

--> Panic: Win32 exception: Stack overflow (0xc00000fd)

-->    rip: 00007ffd5dbcf737 rsp: 000000000c863b50 rbp: 0000000007c168f0

-->    rax: 0000000000020048 rbx: 00000000076dad30 rcx: 00000000076dad30

-->    rdx: 0000000000000ad0 rdi: 00000000076dad30 rsi: 000000000c883dc0

-->    r8:  0000000000003a98 r9:  00000000002a3a00 r10: 000000000c843000

-->    r11: 000000000c853000 r12: 0000000000000001 r13: 0000000000000000

-->    r14: 0000000000000185 r15: 0000000000003a98

-->

--> Backtrace:

--> backtrace[00] rip 00007ffd6a58b23a

--> backtrace[01] rip 00007ffd6a45012f

--> backtrace[02] rip 00007ffd6a45135e

--> backtrace[03] rip 00007ffd6a5a21bc

--> backtrace[04] rip 00007ffd6a5a23c0

--> backtrace[05] rip 00007ffd6a59aef6

--> backtrace[06] rip 0000000069965129

--> backtrace[07] rip 00000000699642d6

--> backtrace[08] rip 00000000699649de

--> backtrace[09] rip 0000000069964c1d

--> backtrace[10] rip 000000006996502b

--> backtrace[11] rip 00007ffd80a23b1d

--> backtrace[12] rip 00007ffd809e8407

--> backtrace[13] rip 00007ffd80a22caa

--> backtrace[14] rip 00007ffd5dbcf737

--> backtrace[15] rip 00007ffd5da09ca1

--> backtrace[16] rip 00007ffd5da0094b

--> backtrace[17] rip 00007ffd5da003b6

--> backtrace[18] rip 00007ffd5da05312

--> backtrace[19] rip 00007ffd5d9de8ab

--> backtrace[20] rip 00007ffd5da01fc4

--> backtrace[21] rip 00007ffd5d9de47a

--> backtrace[22] rip 00007ffd5d9de367

--> backtrace[23] rip 00007ffd5d9b604b

--> backtrace[24] rip 00007ffd5d9b277e

--> backtrace[25] rip 00007ffd6aebf52e

--> backtrace[26] rip 00007ffd6aebb42c

--> backtrace[27] rip 00007ffd6aeb51e0

--> backtrace[28] rip 00007ffd6aecb9fd

--> backtrace[29] rip 00007ffd5dfa0824

--> backtrace[30] rip 00007ffd6b06a78e

--> backtrace[31] rip 00007ffd5e1d52c6

--> backtrace[32] rip 00007ffd5dfab167

--> backtrace[33] rip 00007ffd5df713d7

--> backtrace[34] rip 00007ffd5fcb567d

--> backtrace[35] rip 00007ffd5fccfbe0

--> backtrace[36] rip 00007ffd5fbe4ce9

--> backtrace[37] rip 00007ffd6b5c36ff

--> backtrace[38] rip 00007ffd6b6cf24b

--> backtrace[39] rip 00007ffd6b6ceb6e

--> backtrace[40] rip 00007ffd6b6c3f83

--> backtrace[41] rip 00007ffd6f86a510

--> backtrace[42] rip 00007ffd6f86a08f

--> backtrace[43] rip 0000000004bb7925

--> backtrace[44] rip 0000000004bb92e0

--> backtrace[45] rip 0000000004bbec36

--> backtrace[46] rip 0000000004bc046f

--> backtrace[47] rip 0000000004bc08b7

--> backtrace[48] rip 00000000003382b5

--> backtrace[49] rip 000000000033acc9

--> backtrace[50] rip 000000000033a8f9

--> backtrace[51] rip 00000000045064fa

--> backtrace[52] rip 00007ffd6a52b942

--> backtrace[53] rip 00007ffd6a531a51

--> backtrace[54] rip 00007ffd6a532797

--> backtrace[55] rip 00007ffd6a533888

--> backtrace[56] rip 00007ffd6a52afda

--> backtrace[57] rip 00007ffd6a52e049

--> backtrace[58] rip 00007ffd6a52d233

--> backtrace[59] rip 00007ffd6a52e8d3

--> backtrace[60] rip 00007ffd6a52eb53

--> backtrace[61] rip 00007ffd6a59d42a

-->

My environment:

vCenter 5.5U2 on Windows Server 2012R2

SRM 5.8.0.1 on separate Windows Server 2012R2

Oracle Database 12.1.0.2, using the vCenter DB instance, but separate user (schema)

Oracle client 12.1.0.2 64bit

Any idea?

Thank you

Martin

Hi all,

Did someone try to invoke the inventory mappings API? Any example?

I can't automate such process (add mappings in general).

Any help is appreciated.

Thanks!

Giulio

Hi,

At work, we're making preparations to test our DR preparedness of our Production environment with the following scenario.

Scenario:

At our primary Data Centre:

• Prior to the the network isolation, we'll do a final replication of all our vSphere replications
• Shutdown the servers
• Then the DC will be isolated to simulate the DR

At our Disaster Recovery Data Centre:

• Perform a Disaster Recovery of several recovery plans using SRM
• Manually recover some servers using vSphere replication using the recover option
• Ensure each service is available from our DR site

Typically once the primary DC is available again I'd hit the re-protect option and go back the other way however this time the idea is to essentially shutdown the virtual machines at our DR site and power on the virtual machines at our primary DC (we're not copying any changes back this time). I'm sure this part isn't an issue but I'm thinking of the mess that would be left behind in the vSphere replications (outgoing and incoming), and the state left behind in SRM (I.E. recovery plans would still think it's all recovered at our DR site). Unfortunately I cannot test what it's going to look like and why I need to do to clean it up however I'm assuming the clean up would look something like this (if anyone knows please advise):

Clean up (When both sites can once again talk with each other):

Obviously servers at our Primary DC have been powered back on and the servers at our DR will be powered off

1. Delete the recovered virtual machines at our DR site
2. Stop replication (possibly with the Force option). It's current state would be in a recovered mode. I don't think I can reuse them without first Stopping them which delete them.
3. Delete the recovery plans.

At this point I'd re-configure vSphere replication again and re-create any recovery plans to point back to our Disaster Recovery DC.

Has anyone done anything similar???

Cheers

Connection error: lost connection to srm server (SRM Server version 5.5.1.4) and i have seen the msg error as below

The request failed because the remote server took too long to respond (the command has timed out as the remote server is taking too long to respond)

And I tried to pairing again , but it can't fix this issue , but if I make Restart Service the Site Recovery Manager in window,it work and come back connected

Can anyone suggest for this issue to me,thank you.

Hi,

For a Windows Server 2012 recovery plan, I was attempting to run a command on a recovered vm in the post power on step however even though it succeeds in VMware, nothing is run inside the virtual machine.

Scripts on Windows Server to recover:

- C:\srm\srm.bat (it basically echo's some text out to a log file)

- C:\srm\srm.cmd (it basically echo's some text out to a log file)

Post Power On Step I call the following scripts on the recovered vm:

1. C:\windows\system32\cmd.exe /c c:\srm\srm.bat

2. C:\windows\system32\cmd.exe /c c:\srm\srm.cmd

When I perform a test recovery no text is echo'd into the log files. It's like neither script is executed, ... is there any gotcha's or prerequisites with calling scripts on Windows via SRM?

I'm experiencing an issue with a fresh installation of vCenter(VCSA 5.5U2d) and SRM(5.8.0 - 2336305).  I cannot pair the sites due to a username and password error.

Using a service account that is a local admin on the SRM servers and has the admin role in vCenter and SRM I get a request to accept the certificate for vCenter, and then it fails.

Using a domain admin account that has the admin role in vCenter and SRM I get a request to accept the vCenter certificate and then the SRM certificate, and then it fails.

Using administrator@vsphere.local obviously has the admin role in vCenter and SRM I get a request to accept the vCenter certificate and then the SRM certificate, and then it fails

I have tried pairing the sites using FQDN(what was used in the SRM installation), short name and IP with the same failure result.

All of the ports are open between the sites.

It may be noteworthy that in the SRM logs I have seen "unable to find site", but that may be there just because nothing has been paired yet.

Hi,

I would like to know how SRM works with live data for replicating SQL Server DB.

We have 2 large databases on two different servers. So, let us say we have a Disaster declared and we are trying to get the data from the recovery site. Will I be able to see the exact data or will there be a delay in the data replication? How does SQL DB replication work? Also, we noticed that as a DR Exercise, that we had the database that was not the same that was at the recovery site. Or something happened, that the SRM team did a refresh, and from that point the database did not sync and we were told by the DBA that, the he had to taken out all the data prior to the refresh was done. Because our previous cut of point was the previous night 8pm data.

So, just in general how does SQL replication work irrelevant if the data size is huge and will it have issues to sync?

Hi..

I have a dude respect to SRM array replication. Must I present luns replicated to host Esxi in site recovery? or SRA do that?

What process SRA do during test, recovery and reprotect??

I have IBM SVC and SRM 5.5

Thanks

Hi folks,

i'm new to the vmware community, i needed to implement a new SRA for cloudbyte, i found the SRM api and sdk , but it does not mention anything about the implementation and api's to be implemented for a new third party SRA.

does vmware provide any documents on a NDA ?

thanks

Hello,

I don't understand why my create protection group checkbox is alone as I have 4 datastore to protect (see image below).

Any idea ?

vsphere 5.1u3

vcenter 5.1u3 (windows)

SRM 5.1.3

EMC recoverpoint 4.1SP1 P1

EMC VNX 5300 FCoE

recoverpoint SRA 2.2

Regards.

Hi,

I have a virtual machine that is being replicated using vSphere Replication + I've configured a SRM recovery plan so the virtual machine is Managed By SRM.

In a DR situation:

• To recover a vm that's managed by VR all I need to do is connect to vCenter at your DR site via the vSphere web client and click Recover.
• To recover a vm that's managed by SRM all you need is to get to a vSphere Full client at your DR site that has the SRM plugin installed before you can recover.

My question:

Just say in a DR event that SRM at the DR site was busted (so I couldn't recover VMs managed by SRM) but I can connect to the vSphere Web client and recover vm's managed by VR, is there a way to manually change the virtual machines managed by SRM so they're managed by VR again???

Cheers

Hi

wonder if anyone can help. We are comparing SRM support for various 3PAR SRA's and have found big discrepancy with the VMware interop matrix's and with HP's own matrix's.

Qn: Do VMware or HP certify the SRA or is testing independent?

Qn: where do we stand for support if HP says its supported but VMware don't?

Thanks

I have attached some screenshots for clarity