I am trying to set up Protection Group type of "Individual VM's" and I receive this error.  We are using Vcenter 6.0, SRM 6.1, and VR Appliance 6.1.  The sites are paired, the VR service is running, everything appears fine.  I have repeatedly checked NTP and the times on the vcenter server, the ESX hosts and the VM's and all seem to be right.  I have included the logs for analysis.  My current date 12/8/2015 and the time that I attempted the creation of the Protection Group was at 10:36AM so that one can look at that time in the logs.  Thanks for the assistance.  Note, I am using a trial license of SRM now that will expire on 12/27/2015 until I get my order through my procurement system.

I recently performed an SRM failover and 1 of the 6 VM's in question wouldn't power up after.

On inspection of the .vmx file, I saw that it seemed to lose a mapping of one of it's hard disks. Thankfully I had a copy of the original .vmx so it was relatively easy to identify the correct Disk mapping.

I'm wondering why this may have happened ?

The first few Hard Disks were mapped as follows and were all ok after the SRM,

scsi1.virtualDev = "pvscsi"

scsi1.present = "TRUE"

scsi1:0.deviceType = "scsi-hardDisk"

scsi1:0.fileName = "myservername02_1.vmdk"

scsi1:0.present = "TRUE"

scsi1:1.deviceType = "scsi-hardDisk"

scsi1:1.fileName = "myservername02_2.vmdk"

scsi1:1.present = "TRUE"

scsi1:2.deviceType = "scsi-hardDisk"

scsi1:2.fileName = "myservername02_3.vmdk"

scsi1:2.present = "TRUE"

The last Disk should have been mapped as follows after the SRM

scsi2.virtualDev = "pvscsi"

scsi2.present = "TRUE"

scsi2:0.deviceType = "scsi-hardDisk"

scsi2:0.fileName = "/vmfs/volumes/VMFS_SharedStorage_3154_BPM_LOG1_3696/myservername02/myservername02.vmdk"

scsi2:0.present = "TRUE"

instead it was mapped as

scsi2:0.fileName = "/vmfs/volumes/565fc9d6-4eb63031-9ce1-0025b506011e/myservername02/myservername02.vmdk"

Does anyone know why this may have happened and more importantly, what could be done to prevent it from happening again ?

Unfortunately, a different Team looks after Storage so I'm not able to directly answer any Storage related questions you may have

thanks

I'm looking for the way to delete srm protection group using wsdl, please help me to find it out. I'm using SoapUI to execute SRM wsdl and I have MOB id of protection group.

Let me know if any way to delete protection group using its MOB id in SRM 6.0.

Hi all,

I have recently put in charge of a vBlock and my manager wants SRM installed and configured, I'm fine with SRM, have installed and configured it on other sites.

What I was hoping someone could help me with is the storage back end stuff.

I know SRM needs to replicated from the protected site to the recovery site, so what I am unclear on how the LUNS should be setup initially, then journalled and added to an RP consistency group.

Has anyone done this on a VNX storage array, any help, guidance, suggestions would be massively appreciated.

Thanks

Hi,

In the beginning, we have first certification test case failed at SetupNfsTests,

below are the log messages about failure, seems to be referred to Configuration parameters:

...

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] ,120 INFO  [main] - 'LogResultListener.onTestStart():76' Running test: configureNfsHosts

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] ,232 INFO  [pool-4-thread-2] - 'DrTestVcEnvManager.setupDatastores():292' Adding datastore RecoPH to host kevinesxic.qa.qxxx.com.tw

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] ,242 INFO  [pool-4-thread-1] - 'DrTestVcEnvManager.setupDatastores():292' Adding datastore replica_for_reco to host kevinesxie.qa.qxxx.com.tw

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] ,763 INFO  [main] - 'LogResultListener.logMethodResult():238' TestNGMethod Outcome: FAILURE, configureNfsHosts

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] ,764 ERROR [main] - 'LogResultListener.logException():256' Exception thrown in configureNfsHosts: com.vmware.srm.main.core.test.TestException: Exception occurred in one of the threads: List of exceptions:

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] [0]: com.vmware.srm.main.core.test.TestException: Unable to find NFS datastore replica_for_reco

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.core.test.base.DrTestVcEnvManager.addDatastore(DrTestVcEnvManager.java:348)

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.core.test.base.DrTestVcEnvManager.setupDatastores(DrTestVcEnvManager.java:294)

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.core.test.base.DrTestVcEnvManager.setupDatastores(DrTestVcEnvManager.java:267)

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.tests.bat.env.BatEnvTests.configureHosts(BatEnvTests.java:469)

2015-12-14 19:58:11 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.tests.bat.env.BatEnvTests$7.run(BatEnvTests.java:233)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.main.util.task.SimpleCallable.call(SimpleCallable.java:36)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.main.util.task.SimpleCallable.call(SimpleCallable.java:17)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at java.util.concurrent.FutureTask.run(Unknown Source)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at java.lang.Thread.run(Unknown Source)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng]

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] [1]: com.vmware.srm.main.core.test.TestException: Unable to find NFS datastore RecoPH

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.core.test.base.DrTestVcEnvManager.addDatastore(DrTestVcEnvManager.java:348)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.core.test.base.DrTestVcEnvManager.setupDatastores(DrTestVcEnvManager.java:302)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.core.test.base.DrTestVcEnvManager.setupDatastores(DrTestVcEnvManager.java:267)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.tests.bat.env.BatEnvTests.configureHosts(BatEnvTests.java:469)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.tests.bat.env.BatEnvTests$8.run(BatEnvTests.java:242)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.main.util.task.SimpleCallable.call(SimpleCallable.java:36)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at com.vmware.srm.main.util.task.SimpleCallable.call(SimpleCallable.java:17)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at java.util.concurrent.FutureTask.run(Unknown Source)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng] at java.lang.Thread.run(Unknown Source)

2015-12-14 19:58:12 CST [ SRA       ] [0] INFO:      [java]    [testng]

...

Could anyone kindly help us to point out what's/where's wrong with Configuration parameters setting ?

Below is some of our Configuration parameters setup in the test, If you need extra information, please let us know, thanks.

Dictionary object holds test parameter information

  Volume path to empty NFS datastore for FVT for NFSDATASTOREVOLUMEPATH     replica_for_prot

  Number of parallel workflows to run during FVT for NUMBEROFPARALLELWORKFLOWS     2

  SRA opaque values for protected site array [ Note : Please input either NA or None, if this is not applicable for SRA ] for PROTECTEDSITEOPAQUEVALUES     NA

  SRA opaque values for recovery site array [ Note : Please input either NA or None, if this is not applicable for SRA ] for RECOVERYSITEOPAQUEVALUES     NA

  Name of empty datastore on replicated LUN for FVT for REPLICATEDNFSDATASTORE     replica_for_reco

  XML ID for SRA address tag(s) for SRAADDRESSTAG     NA

  SRA Name for SRANAME     workbench353srm

  Enter the SRM Version (eg : If SRM 6.0, enter 6.0 ) for SRMVERSION     6.0

...

Thank you very much,

Nicole

After installation of vCenter 5.5 Update 3b, SRM 5.5 no longer functions.  The vmware-dr logs show several SSL Exceptions "error: class Vmacore::Ssl::SSLException(SSL Exception: error:140000DB:SSL routines:SSL routines:short read)".

The VMware product interoperability matrixes for SRM have never shown any of the a/b/c/d/etc releases of vCenter, so I don't know if this is supposed to be working or not.

Hi guys,

I going to plan an installation of two ESX Cluster in two different location in the same building.

I trying to archive a RTO less than 8 minutes, my solution is based on two site with it's own vcenter and SRM server and with array based replication.

I have one simple question, if I have to test a recovery plan I can go on the source site and start the recovery plan for a single VM or a group, but what happen if my site A fail completely? In the site A I have all the VM anche the Virtual Center e the SRM Server.

The prodedure starts automatically from a "remote" site input? Or I have to go into remote site and start a remote plan manually?

Thanks

So I have been taking my time installing VC6, installed 2 external PSC's and 2 vCenter Servers and setup of VMCA as subordinate ca a pain but it was done and completed and no issues as of this point. THEN I SRM 6.1 is installed on each of the vCenter Servers. When I try and see the other site to pair I am getting the following error.

I have seen the following KB's 2109074, 2121689 and 2121701. Is this really the only way of getting this fixed? I haven't done them yet in hopes someone else has found a better and quicker fix. So frustrating with these certs issues, VMware can't get things done simple. 

Error

Cause:

Failed to connect to Lookup Service at

https://mydoamin.com:443/lookupservice/sdk.

Reason:

com.vmware.vim.vmomi.core.exception.CertificateValidationException:

Server certificate chain not verified

Thanks in advance,

Dear All,

Can we assign a Snapshot LUN with existing signature to vShere Cluster which is part of VMware SRM?? What would be the impact.

Hello community,

i have a following design and update question about vSphere 6 with SRM.

In out of our subsidiaries we have the following installation configured:

- VMware vSphere 5.5 U3 enviroment with Site Recovery Manager installed that is running on 5.8.
- Two vCenter server running within a linked mode configuration, so you only need to access one vCenter server to see both sides.

No we would like to update to vSphere 6 and here I have some question how to dit it in the best way.
Would it be a good thing or maybe it is mandatory to have an external Platform service controller installed in the vSphere environment and then start the upgrade to vSphere 6, or should each side have its "own" PSC.

Thank you for some hints and in formations from your side.

After install SRM 5.8(with embeded DB ) on the same server as VC 5.5U2 with no errors, I login in via web client,but not site recovery manager icon displays on the home inventory.

but in the other site which is been setup as the same way, I can see the icon,and it works fine

has anybody experience the same issues?

By the way, on the vsphere client plug-in,I can see the "Site recovery manager" plug-in

We recently installed SRM (V5.1.3.8765) in two separate locations. We are using Compellent SRA for VMware SRM(6.2.2.7) also at both locations.

Local:

VCenter Server 5.1.0.35539

EXSi 5.0.0,3086167 & 5.1.0,3070626

Remote:

VCenter Server 5.1.0.35539

EXSi 5.0.0,3086167

When I try the test I get Error - Failed to recover datastore 'xxxxxxxxx'. VMFS volume residing on recovered devices '"172"' cannot be found.

I have tried changing the settings for: storageProcider.hostRescanRepeatCnt and storageProvider.hostRescanDelaySec.

I have reviewed the logs for both VMWare and the Compellent

I see this error in the VMware log located under c$\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs:

error 'SoapAdapter.HTTPService'] Failed to read request; stream: <SSL(<io_obj p:0x000000000d9bf9d8, h:2996, <TCP 'xx.xx.xx.xx:8095'>, <TCP 'xx.xx.xx.xx:64346'>>)>, error: class Vmacore::SystemException(An established connection was aborted by the software in your host machine)

And this errror in the  Compellent log located under c$\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\SRAs:

2015-12-15T12:11:34.502 | Warning  | [DiscoverDevices (Source SC: 6727) (Dest SC: 38335)] Error getting restore points from Source [Execption: No DrScReplicationControl found [SourceSn: 6727] [DestSn: 38335]]

Test information [RestorePoint: 593] [SourceVolume: xxxxxxxxx]  [VmWareSraViewVolumeHistory: 172] [VmWareSraViewVolumePitc: 514] [VmWareSraViewVolumeTimeStr: 2015-12-10T09:17:28] [Dest SC: 38335] [Dest Volume Index: 172] [Source SC: 6727] [SourceVoIndex: 109]

TargetDevice key="172" >

                <Name>Repl of xxxxxxxxx</Name>

                <Snapshot id="238">

                    <Identity>

                        <Lun initiatorGroupId="6727.2716386042">8</Lun>

                        <Lun initiatorGroupId="6727.4286167776">8</Lun>

                    </Identity>

                    <RecoveryPoint id="172.514">

                        <Name>Latest</Name>

                        <Time>2015-12-10T09:17:28</Time>

                    </RecoveryPoint>

                </Snapshot>

            </TargetDevice>

Can anyone assist me with this?

Thanks,

Lisa

i want to install srm ( lab) on vmware workstation . is it possible ?

which sql setup i can install for srm .

SQLManagementStudio_x64_ENU.exe

Hi,

I have a problem in Vmware SRM,

I can't connect the SRM with the Message:

Connection error: lost connection to srm server

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)

But:

The plugin is Ok

The replication continues Ok

The ports is Ok

Permissions is OK

Ping is Ok

The problem is, The click to start SRM client and: return the error..

Someone can Help.

Thanks.

hi

i want to install srm 6.1 . There are 3 options oracle, sql and embedded vPostgreSQL in setup. which is the best option any handicap for choice ?

note : thare are  4 cluster and 1400 virtual machines in my company with one vcenter. and we maybe 250 virtual machines replication to dr site with hp 3par or vmware replication .

hi,

when i add a pair site . i get error . how to solve this problem

I've NFS placeholder datastore name as ProtPH in primary side but Certification test still throwing exception on unable to find ProtPH datastore.

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng] [0]: com.vmware.srm.main.core.test.TestException: Unable to find NFS datastore ProtPH

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at com.vmware.srm.core.test.base.DrTestVcEnvManager.addDatastore(DrTestVcEnvManager.java:348)

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at com.vmware.srm.core.test.base.DrTestVcEnvManager.setupDatastores(DrTestVcEnvManager.java:302)

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at com.vmware.srm.core.test.base.DrTestVcEnvManager.setupDatastores(DrTestVcEnvManager.java:267)

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at com.vmware.srm.tests.bat.env.BatEnvTests.configureHosts(BatEnvTests.java:469)

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at com.vmware.srm.tests.bat.env.BatEnvTests$7.run(BatEnvTests.java:233)

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at com.vmware.srm.main.util.task.SimpleCallable.call(SimpleCallable.java:36)

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at com.vmware.srm.main.util.task.SimpleCallable.call(SimpleCallable.java:17)

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at java.util.concurrent.FutureTask.run(Unknown Source)

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

[Jan  5 2016 12:08:24 : SRA       ] [0] INFO:      [java]    [testng]   at java.lang.Thread.run(Unknown Source)

Is there any specific volume path of this NFS datastore or any alternate way to solve this issue?

Getting error "SRA command ‘discoverArrays’ failed. Failed opening session for user to site mgmt IP" while adding recoverpoint.

Looking at the SRM logs on the SRM server did not really provide much more information

I'm running into an issue with configuring the Array based Replication.

On Site A:

SRM 5.8 - Build 2336305

SRA 2.3.0 for Nimble storage

Physical:

BladeSystem c7000 Enclosure G2

ProLiant BL465c Gen8 -1

iSCSI:

iqn.1990-07.com.emulex:b4-b5-2f-58-57-11

iqn.1990-07.com.emulex:b4-b5-2f-58-57-11

ProLiant BL465c Gen8 - 2

iSCSI

iqn.1990-07.com.emulex:b4-b5-2f-58-e5-79

iqn.1990-07.com.emulex:b4-b5-2f-58-e5-79

ProLiant BL465c Gen8 - 3

On Site B:

SRM 5.8 - Build 2336305

SRA 2.3.0 for Nimble storage

Physical:

BladeSystem c7000 Enclosure G3

ProLiant BL465c Gen8 - 1

iSCSI

iqn.1990-07.com.emulex:38-63-bb-37-35-91

iqn.1990-07.com.emulex:38-63-bb-37-35-91

ProLiant BL465c Gen8 - 2

iSCSI

iqn.1990-07.com.emulex:38-63-bb-37-e6-b9

iqn.1990-07.com.emulex:38-63-bb-37-e6-b9

ProLiant BL465c Gen8 - 3

When trying to configure the Array replication Site B shows it's working fine. But on Site A I get a duplicate initiator error message.

Here is the following error on Site A BL465c - 1 error:

Discover Replicated Devices xx.domain.com Duplicate initiator 'iqn.1990-07.com.emulex:b4-b5-2f-58-57-12' found in SRA's 'discoverDevices' response.

2015-06-30T10:52:57.182-07:00 [02892 verbose 'PropertyProvider' opID=1fd9ba22] RecordOp ASSIGN: info.progress, dr.storage.ReplicatedArrayPair.discoverDevices16

2015-06-30T10:52:57.213-07:00 [02892 verbose 'Storage' opID=1fd9ba22] XML validation succeeded

2015-06-30T10:52:57.213-07:00 [02892 error 'Storage' opID=1fd9ba22] Duplicate initiator ID 'iqn.1990-07.com.emulex:b4-b5-2f-58-57-11' at (43:8):

--> <Initiator id="iqn.1990-07.com.emulex:b4-b5-2f-58-57-11" type="iSCSI"/>

2015-06-30T10:52:57.213-07:00 [02852 verbose 'PerformanceMonitor' opID=1fd9ba22] Performance monitor Token 0 of lock PersistableRWLock-3175 Locked took 7.488 seconds

2015-06-30T10:52:57.213-07:00 [02852 verbose 'PersistableRWLock' opID=1fd9ba22] Releasing Write lock 'PersistableRWLock-3175'

2015-06-30T10:52:57.213-07:00 [02852 verbose 'Storage' opID=1fd9ba22] Releasing read op lock on 'array-pair-3136'

2015-06-30T10:52:57.213-07:00 [02852 verbose 'PerformanceMonitor' opID=1fd9ba22] Performance monitor Token 0 of lock PersistableRWLock-3137 Locked took 7.504 seconds

2015-06-30T10:52:57.213-07:00 [02852 verbose 'PersistableRWLock' opID=1fd9ba22] Releasing Read lock 'PersistableRWLock-3137'

2015-06-30T10:52:57.213-07:00 [02852 info 'Storage' opID=1fd9ba22] Dr::Storage::VmomiLayer::DiscoverDevicesExecutor::DiscoveryComplete: discover devices completed

2015-06-30T10:52:57.213-07:00 [02852 error 'Storage' opID=1fd9ba22] Failed to discover devices at local site: (dr.storage.fault.DuplicateInitiator)

Any help or suggestions would be appreciated. Thanks in advance.