i have a producrion site and DR L2 ( same ip address when Fail Over).

i need to do  a real test, this way.

1 disconnect the Two Prod And DR

2 bring up the DR when No change In The Production Site ( All Is Online)

3 Do a Test At the Dr To All Servers

4 Stop All At the DR

5 connect Back The Prod to the DR

6 Syn back The Prod To DR.

Thanks for working Answer.

Assistance required for simple high level plan for the above, assuming all other parts are done ie ESXi is it a simple 1 step upgrade for do I hav eto go to 6.0, 6.1 etc etc

In SRM 6.1 when SPPG is used then what will happen if failback is triggered but before failback in Old recovery site few VM were created  with the same policy that was the part of protection group. As per my understanding "those VMs will get the protectio" only old vm's connected with the same policy will get the protection with reprotect. Just want to know the expert view in the same.

Can someone here provide some documents on the recommended configuration of VMware for EMC to make it work for SRM?

I am talking about some used cases so I can compare this.

Most of the configuration is made in the EMC Solutions enabler and editing of the srdfsrmsra xml file, which is for the part is manual since every VM to be protected will be added or just in case be removed and that what feature of EMC will be used, This would require constant backup of the XML file and reconfiguration in the Solutions enabler. I even heard that VM device groups created in the EMC solutions enabler is removed after a test recovery is made. Test recovery plan and planned migration scenarios will need different EMC configuration.

I am looking for an automated one time configuration which can both work in different SRM scenarios.

Has someone experienced using the EMC SRDF Utilities plugin in vCenter where EMC configuration will be configured? Ours is installed but is not working properly.

SRM: 6.1.1

vCenter: 6 U2

SRA: 6.1

VMAX technology: clone and snap

Hi,

Does anyone know if there are any issues when using vSphere Replication to replicate a SQL cluster as part of an SRM solution for DR?

Thanks in advance for your help!

Hello all,

Making good progress in my SRM environment.

Proof of concept failovers are working flawlessly, gone back and forth several times without any issues.

I did notice one thing that bothers me.

While setting up my production disks I looked at the Array Based Replication screen in SRM and noticed the replication direction was pointing the wrong way in my screen.

Array pairs were presented as copying from TR site to my production site.

I had the storage team check and they verified replication was going from production site to TR site.

I restarted SRM servers and then the direction was presented correctly again.

When I look now, again I see one consistency group presented as copying in wrong direction.

I restarted SRM but this time it did not change it.

Next week I need to failover this consistency group. I am worried it will fail because SRM may be confused about the status.

Has anyone seen this kind of behavior before?

JJPP

Hello,

I'm having trouble removing a VM from a SRM protection group. The VM has been deleted before removing from the protection group.

The error is:

Invalid: The VM is no longer protected

This VM is not replicated by VR.

Is there a way I can manually remove this VM?

Thanks!

Hello,

After completing a failover of, say, a 40GB virtual machine from site A to site B, if we choose to click on the reprotect button to reverse the replication back from site B to A, does SRM replicate the full 40GB VMDK of the virtual machine from Site B back to Site A or is there some sort of method that SRM maintains deltas so that we don't have to replicate the full virtual machine back?

This will help us with planning how long it would take to failback our infrastructure if we choose to failover to another site.

Thank you.

Setup is as follows:

• vSphere 6
• 1 vcenter server (vcenter01) and 1 PSC (PSC01) at protected site
• 1 vcenter server (vcenter02) and 1 PSC (PSC02) at recovery site
• Each vcenter server is pointed at its own PSC
• There is no load balancer involved

During the protected site SRM install, when it asked which PSC to choose, I chose PSC01 which then allowed me to select the appropriate vcenter server, vcenter01.  When I installed SRM at the protected site I was not able to choose PSC02.  It gave me the error "failed to find a vcenter server from platform services controller".  If I told it to use PSC01 I was then able to select the appropriate vCenter server (vCenter02) for the recovery site.  My question, is this normal?  I assumed I would target the recovery site instance of SRM at the recovery site PSC. 

thank you

I have a customer who asked me what happens when his MPLS goes down. I told him that he would have the most recent replication that has happened is what he would have to work with. since he will be running an active passive model to a hosted data center he just needs to make sure that the replication of the Protected VM's is happening at a manageable RPO for the business.

I guess the real question I have is around the DNS. he said the public DNS is also on the MPLS or WAN. So what would he need to do to protect that in the event of a fail over?

When I am trying to create protection groups, when I try to associate the LUNs to be protected; it is not found in the SRM.

But the LUNs is perfectly visible via vsphere or web client.

Storage is VMAX3

SRA is version 6

Does re installing the array manager will resolve this?

While Site Pairing everything goes correct...connection to remote vcenter server, certificate validation, connection to remote srm server, certification valiidation and reciprocity 9everything goes fine).

After i say "finish" it prompt for Protected vCenter and Recover vCenter Username and Password.

Then i get error saying "No Client connection to SRM Server for IP/vCenter remote"

Please help in resolving the issue. I get the same error prompt from both sides

I am using SRM 5.8, wanted to use new API feature to create folder, network mapping using powercli.

$web01 = New-WebServiceProxy("http://" + $srmServerAddr + ":9085/srm.wsdl") -Namespace SRM01

$srm01 = New-Object SRM01.Srmbinding

$srm01.url = "https://" + $srmServerAddr + ":9007"

$srm01.CookieContainer = New-Object System.Net.CookieContainer

$mof01 = New-Object SRM01.ManagedObjectReference

$mof01.type = "SrmServiceInstance"

$mof01.value = $mof01.type

$srmApi01 = ($srm01.RetrieveContent($mof01)).srmApi

$protection01 = ($srm01.RetrieveContent($mof01)).protection

$recovery01 = ($srm01.RetrieveContent($mof01)).recovery

$mapping = ($srm01.RetrieveContent($mof01)).InventoryMapping

PowerCLI C:\> $srm01.AddFolderMapping

OverloadDefinitions

-------------------

void AddFolderMapping(SRM01.ManagedObjectReference _this, SRM01.ManagedObjectReference primaryFolder, SRM01.ManagedObjectReference secondaryFolder)

I checked all the options to find primaryFolder MoRef but does not find any, can some point to how to map the folder using PowerCLI?

Regards,

Shyam Dhawale

Hi

I have a customer who has vSphere 5.5 (inc vCentre) and SRM 5.8.

We are looking to upgrade to 6 u2 (not 6.5 at this point as a couple of the hosts do support it).

The preference is to install a new instance of External PSC with a new vCentre server 6, rather than upgrade.  Can we build the new version 6 environment and build a new SRM 6 environment alongside the existing SRM 5.8 and migrate into it?

Thanks

Hello,

Using SRM 5.8, I have 3 esxi servers on the recovery site. One of them needs to be placed in maintenance mode and possibly shutdown for hardware diagnostics. Is there a particular process I should follow to do this? Currently there are a few SRM-related objects on this server. How will they move without breaking?

Regards

Hi,

Is it possible to recover a VM using SRM ( array based replication ) that has discs spread out on multiple luns, and only recover 4 out of 5 discs( luns ) ? Assuming the 4 luns the desired discs are being replicated.

Thanks

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,

I am using vCenter Server Appliance 6.0 Update 1 with VMware-srm-6.1.0-3037005.

I found some error in SRM server log.

Dose anyone know how to solve this issue?

2016-11-22T16:08:50.734+08:00 [00248 verbose 'SessionManager'] Logging into remote site with token. Remote site = 'site-1026', locale = 'en'

2016-11-22T16:08:50.734+08:00 [00248 verbose 'Vmacore::Xml::Security'] Verification of signature Reference URI: `#_e98444a0-b77e-49b1-993e-6e88655240af' ; is-valid: true

2016-11-22T16:08:50.734+08:00 [00248 verbose 'Vmacore::Xml::Security'] Missing reference count: 0

2016-11-22T16:08:50.734+08:00 [00248 verbose 'Vmacore::Xml::Security'] Verification of signature SignedInfo: is-valid: true

2016-11-22T16:08:50.734+08:00 [00248 verbose 'Default'] Found security token in request message

2016-11-22T16:08:50.734+08:00 [02804 trivia 'SsoClient'] opId=52c9510d-f67d-d07d-666b-a53e944107a3 START operation SecurityTokenServiceImpl::ValidateSubject

2016-11-22T16:08:50.734+08:00 [02804 trivia 'SsoClient'] Validating subject of token SamlToken [subject={Name: Administrator; Domain:VSPHERE.LOCAL}, groups=[{Name: Users; Domain:vsphere.local}, {Name: Administrators; Domain:vsphere.local}, {Name: CAAdmins; Domain:vsphere.local}, {Name: ComponentManager.Administrators; Domain:vsphere.local}, {Name: SystemConfiguration.Administrators; Domain:vsphere.local}, {Name: LicenseService.Administrators; Domain:vsphere.local}, {Name: Everyone; Domain:vsphere.local}], delegationChain=[], startTime=2016-11-22 08:08:59.183, expirationTime=2016-11-22 08:13:59.183, renewable=false, delegable=true, isSolution=false,confirmationType=0]

2016-11-22T16:08:50.828+08:00 [02804 trivia 'SsoClient'] Result: true

2016-11-22T16:08:50.828+08:00 [02804 trivia 'SsoClient'] opId=52c9510d-f67d-d07d-666b-a53e944107a3 END operation SecurityTokenServiceImpl::ValidateSubject

2016-11-22T16:08:50.828+08:00 [02864 info 'SessionManager'] Logged in remote site for session '52676', remote site = 'vcsa2.test.com' site-1026, principal = '{Name: Administrator; Domain:VSPHERE.LOCAL}', locale = 'en'

2016-11-22T16:08:50.968+08:00 [00248 verbose 'SessionManager'] Logging into remote site with token. Remote site = 'site-1026', locale = 'en'

2016-11-22T16:08:50.968+08:00 [00248 error 'SessionManager'] SRM session '52676' is already logged in to remote site 'dr.site.RemoteSite:e050c009-2e34-4068-b1ad-dc5f27c8e3d3:site-1026'.

2016-11-22T16:08:51.218+08:00 [02864 verbose 'DrAuthorizationManager'] Normalizing 8 trusted principal names.

2016-11-22T16:08:51.420+08:00 [00428 verbose 'SessionManager'] Logging into remote site with token. Remote site = 'site-1026', locale = 'en'

2016-11-22T16:08:51.420+08:00 [00428 error 'SessionManager'] SRM session '52676' is already logged in to remote site 'dr.site.RemoteSite:e050c009-2e34-4068-b1ad-dc5f27c8e3d3:site-1026'.

2016-11-22T16:08:51.810+08:00 [02804 verbose 'SessionManager'] Logging into remote site with token. Remote site = 'site-1026', locale = 'en'

2016-11-22T16:08:51.810+08:00 [02804 error 'SessionManager'] SRM session '52676' is already logged in to remote site 'dr.site.RemoteSite:e050c009-2e34-4068-b1ad-dc5f27c8e3d3:site-1026'.

2016-11-22T16:08:52.013+08:00 [02804 verbose 'SessionManager'] Logging into remote site with token. Remote site = 'site-1026', locale = 'en'

2016-11-22T16:08:52.013+08:00 [02804 error 'SessionManager'] SRM session '52676' is already logged in to remote site 'dr.site.RemoteSite:e050c009-2e34-4068-b1ad-dc5f27c8e3d3:site-1026'.

2016-11-22T16:08:52.575+08:00 [02180 verbose 'SessionManager'] Logging into remote site with token. Remote site = 'site-1026', locale = 'en'

2016-11-22T16:08:52.575+08:00 [02180 error 'SessionManager'] SRM session '52676' is already logged in to remote site 'dr.site.RemoteSite:e050c009-2e34-4068-b1ad-dc5f27c8e3d3:site-1026'.

2016-11-22T16:08:52.949+08:00 [00428 verbose 'SessionManager'] Logging into remote site with token. Remote site = 'site-1026', locale = 'en'

2016-11-22T16:08:52.949+08:00 [00428 error 'SessionManager'] SRM session '52676' is already logged in to remote site 'dr.site.RemoteSite:e050c009-2e34-4068-b1ad-dc5f27c8e3d3:site-1026'.

2016-11-22T16:08:53.043+08:00 [00428 verbose 'HttpConnectionPool-000000'] [RemoveConnection] Connection removed; cnx: <SSL(<io_obj p:0x000000000a1efc38, h:-1, <TCP '0.0.0.0:0'>, <TCP '192.168.139.172:443'>>)>; pooled: 13

2016-11-22T16:08:53.199+08:00 [02804 verbose 'SessionManager'] Logging into remote site with token. Remote site = 'site-1026', locale = 'en'

2016-11-22T16:08:53.199+08:00 [02804 error 'SessionManager'] SRM session '52676' is already logged in to remote site 'dr.site.RemoteSite:e050c009-2e34-4068-b1ad-dc5f27c8e3d3:site-1026'.

2016-11-22T16:08:54.681+08:00 [02180 verbose 'HttpConnectionPool-000000'] [RemoveConnection] Connection removed; cnx: <SSL(<io_obj p:0x000000000a1ee808, h:-1, <TCP '0.0.0.0:0'>, <TCP '192.168.139.172:443'>>)>; pooled: 12

2016-11-22T16:08:55.554+08:00 [02804 info 'DrSiteSiteManager' connID=371] Starting persistent connection monitoring

2016-11-22T16:08:55.554+08:00 [02804 verbose 'DrSiteSiteManager' connID=371] The newly started persistent connection is still waiting to connect

2016-11-22T16:08:55.554+08:00 [02804 verbose 'DrSiteSiteManager' connID=371] Dr::PersistentConnection::ConnectLocked: Attempting to connect

2016-11-22T16:08:55.554+08:00 [02864 verbose 'StubFactory' connID=371] Event broadcasted

2016-11-22T16:08:55.554+08:00 [02864 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to <cs p:000000000a44c680, TCP:192.168.139.172:443>; cnx: (null), error: class Vmacore::Ssl::SSLVerifyException(SSL Exception: Verification parameters:

--> PeerThumbprint: 50:84:CB:1C:AA:76:C7:57:A6:D2:0C:86:12:1D:35:09:F3:24:D2:3B

--> ExpectedThumbprint: Unknown command: `echo'

--> ExpectedPeerName: 192.168.139.172

--> The remote host certificate has these problems:

-->

--> * The host certificate chain is incomplete.

-->

--> * Host name does not match the subject name(s) in certificate.

-->

--> * unable to get local issuer certificate)

2016-11-22T16:08:55.586+08:00 [02804 warning 'Default'] Dr::Internal::StubExcTranslator : Error while calling stub for 'lookup.ServiceInstance:ServiceInstance'

--> std::exception 'class Vmacore::Ssl::SSLVerifyException' "SSL Exception: Verification parameters:

--> PeerThumbprint: 50:84:CB:1C:AA:76:C7:57:A6:D2:0C:86:12:1D:35:09:F3:24:D2:3B

--> ExpectedThumbprint: Unknown command: `echo'

--> ExpectedPeerName: 192.168.139.172

--> The remote host certificate has these problems:

-->

--> * The host certificate chain is incomplete.

-->

--> * Host name does not match the subject name(s) in certificate.

-->

--> * unable to get local issuer certificate"

2016-11-22T16:08:55.648+08:00 [02804 warning 'DrSiteSiteManager' connID=371] Failed to connect: (dr.fault.CertificateNotTrustedByDr) {

-->    faultCause = (dr.fault.CertificatePartialChain) {

-->      faultCause = (vmodl.MethodFault) null,

-->      name = "vcsa1.test.com",

-->      uuid = "e050c009-2e34-4068-b1ad-dc5f27c8e3d3",

-->      address = "192.168.139.172",

-->      port = "443",

-->      reason = (vmodl.MethodFault) null,

-->      msg = ""

-->    },

-->    name = "vcsa1.test.com",

-->    uuid = "e050c009-2e34-4068-b1ad-dc5f27c8e3d3",

-->    address = "192.168.139.172",

-->    port = "443",

-->    reason = (vmodl.MethodFault) null,

-->    msg = ""

--> }

Thanks.

i am trying to create protection groups but i get the following error:

"" Unable to find a placeholder datastore for the host/cluster , Any placeholder datastores registered with the SRM server that were deleted and recreated in the vCenter Server will need to be removed and re-added as a new placeholder datastore with the SRM server as well. ""

i have already uninstalled SRM and installed it with new settings with no success, still getting this error.

is there any workaround or a solution without removing the VMs from the vCenter Server inventory and re-replicate again.??

regards

We performed an SRM failover/failback between two sites (successfully). On the recovery site we notice that the replicated luns that were mounted during failover, now show as unmounted during failback. Should SRM have followed that unmount with a detach, so no devices would be showing on the recovery side hosts?

I ask because we recently patched the hosts at the recovery site, which meant they got rebooted. After reboot, the previously unmounted luns are now showing as mounted. To be more specific, they are simply mounted (connected) to the ESXi hosts at the recovery side. The actual datastores associated with those luns have not been mounted.

Is this the behaviour of SRM after a failback? Should we have expected to see the recovery hosts with no evidence of those replicated luns (i.e. SRM should have unmounted and then detached the luns)? I'm not even certain that would suffice as the lun mapping at the storage side still exists. I suppose a full unmount would be unmount - detach - unmap. I don't believe SRM goes that far when unpresenting the replicated datastores from the recovery hosts during a failback. Any clarification would be appreciated.

Thanks