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

Over the last ten years, virtualization has evolved to become an industry best practice to reduce costs, improve availability, accelerate time to value and simplify management.People strive to find the perfect  disaster recovery plan for it department. Below list of articles for disaster recovery plan and business continuity plan help you to understand detailed step by step procedure to install and configure VMware SRM. VMware Site Recovery Manager (SRM) is a disaster recovery  and business continuity solution from the VMware,which automates the transfer of virtual machines to a local or remote recovery site.

VMware SRM works perfectly with the existing vSphere software and it operates as an extension of vCenter server. SRM automates the recovery or migration of virtual machines between protected site and a recovery site.This list of tutorials will help you to understand step by step procedure to implement your disaster recovery plan and business continuity plan using VMware Site Recovery Manager.

Disaster recovery plan and business continuity plan Tutorial

This tutorial’s targeted audience are system administrators, VMware administrators and storage administrators, who want to implement disaster recovery plan for IT department using VMware Site Recovery Manager along with HP Virtual Storage Array.

Disaster Recovery :

VMware Site Recovery Manager (SRM 6.0) Part 1- Overview and Architecture

This article will help you to understand the overview  and Architecture of the VMware Site Recovery Manager.  It also provides high level recommendations to implement your Disaster Recovery plan for your IT using SRM and SAN replication software.

VMware Site Recovery Manager (SRM 6.0) Part 2 – VMware SRM 6.0 installation

This article will help you to understand various pre-requisites to install SRM and also detailed step by step procedure to install your favorite disaster recovery  and business continuity solution

VMware Site Recovery Manager (SRM 6.0) Part 3 – Configuring SRM Site Pairing

This article will help you to understand  the procedure to pair your primary protected site with your disaster recovery site using Site Pairing option in VMware SRM.

VMware Site Recovery Manager (SRM 6.0) Part 4 – Installing Storage Replication Adapters (SRAs)

This article will help you to understand what is Site Replication Adapters (SRA) and how to install SRA to work with VMware SRM. Storage Replication Adapters (SRA) is a program provided by a storage array vendor that enables vCenter Site Recovery Manager to work with the vendor’s array.

VMware Site Recovery Manager (SRM 6.0) Part 5 – Configuring SRM Array Manager

This article will help you to understand the procedure to configure SRM array manager.  VMware site recovery manager uses this information to discover the storage array available to SRM host and the replicated LUNs for it.

VMware Site Recovery Manager (SRM 6.0) Part 6 – Creating SRM Resource Mappings

This article will help you to understand the procedure to configure resource mappings between your primary protected site  and disaster recovery site. This step is required because we use 2 different vCenter servers installed that are not linked by common data source.

VMware Site Recovery Manager (SRM 6.0) Part 7 – Configuring SRM Folder Mapping

This article will help you to understand the procedure to configure folder mappings between your primary protected site  and disaster recovery site. This step will help you for better management and planning by organizing the Virtual machines into the mapped folder after the Disaster Recovery plan is executed.

VMware Site Recovery Manager (SRM 6.0) Part 8 – Configuring SRM Network Mapping

This article will help you to understand the procedure to configure Network mappings between your primary protected site  and disaster recovery site. This is very important step to configure the proper network mapping between your Protected site and Disaster recovery site. This ensures that VMs that are powered on at the Recovery Site will be accessible across the network.Network mappings can only be related to Virtual machine port groups

VMware Site Recovery Manager (SRM 6.0) Part 9 – Configuring SRM Placeholder Datastores

This article will help you to understand the procedure to configure Placeholder datastore for your primary protected site  and disaster recovery site. A placeholder datastore is used to store the placeholder virtual machines at the recovery site. A placeholder datastore reserves a place for protected virtual machines in the recovery site’s inventory.

VMware Site Recovery Manager (SRM 6.0) Part 10 – Creating SRM Protection Group

This article will help you to understand the procedure to create SRM Protection group. Site Recovery Manager Protection groups can be created to group virtual machines for protection. SRM protection groups will be different for array-based replicated virtual machines and vSphere replication replicated virtual machines

VMware Site Recovery Manager (SRM 6.0) Part 11 – Creating SRM Recovery Plans

This article help you to understand the procedure to create your Disaster Recovery Plan using VMware SRM. vCenter Site recovery manager recovery plan is a automated plan for recovering protected virtual machines to the recovery site. SRM recovery plan includes one or more protection groups. This is also called as disaster recovery plan and business continuity plan

VMware Site Recovery Manager (SRM 6.0) Part 12 – Running SRM Test Recovery

This article will help you to understand how to test your disaster recovery plan and business continuity plan without disturbing the actual production workloads using the SRM test recovery option.

VMware Site Recovery Manager (SRM 6.0) Part 13 – Cleaning up Test Recovery

This article will help you to understand the procedure to clean up your test recovery after executing  your disaster recovery plan and business continuity plan.

SAN Replication using HP Store Virtual VSA:

HP StoreVirtual VSA transforms your server’s internal or direct-attached storage into a fully-featured shared storage array without the cost and complexity associated with dedicated storage. StoreVirtual VSA is a virtual storage appliance optimized for VMware vSphere and Microsoft Hyper-V environments.It creates a virtual array within your application server and scales as storage needs evolve. The ability to use internal storage within your environment greatly increases storage utilization, and eliminates the costs and complexity associated with dedicated external storage.Its built-in high availability and disaster recovery features ensure business continuity for the entire virtual environment. It is free replication software from HP.

VMware SRM 6.0 Array Based Replication Part 1 – Deploying HP Store Virtual VSA

This article will help you to understand the procedure to deploy the HP store Virtual appliance in top of hypervisor. This article also talks about 2 different replication options available to use with VMware SRM. First one is storage array replication and second one is free replication software “vSphere replication” from VMware to leverage the virtual machine replication.

VMware SRM 6.0 Array Based Replication Part 2 – Installing HP Store Virtual VSA Centralized Management Console (CMC)

This article will help you to understand the procedure to install HP Store Virtual VSA Centralized Management Console (CMC) in windows server. The HP VSA centralized management console allows us to centrally manage VSA appliances and other tasks like adding hosts, presenting storage to host, configuring replication between VSA appliance, etc.

VMware SRM 6.0 Array Based Replication Part 3 – Configuring HP StoreVirtual VSA Management Group

This article will help you to understand the procedure to Configure Virtual Storage Array appliance and create VSA management group using HP VSA Centralized Management Console (CMC)

VMware SRM 6.0 Array Based Replication Part 4 – Adding ESXi host to HP VSA Management Group and Presenting Storage to ESXi

This article will help you to understand the procedure to add ESXi host to VSA  management group and Preset Storage to the ESXi host and add them as a Datastore to store Virtual machine.

VMware SRM 6.0 Array Based Replication Part 5 – Configuring HP StoreVirtual VSA Replication

This article will help you to understand the  procedure to configure the Storage replication between your Protected and Disaster recovery site using Free software HP storeVirtual VSA.

I hope this tutorial will help you to understand and implement your disaster recovery plan and business continuity plan using VMware’s disaster recovery  and business continuity solution. Please share it in social media like Google, Facebook and twitter, if you feel worth sharing it.

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,

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.

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.

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.

my sites have the vcenter server embeded on platform services, two sites one production one disaster recovery, when try to pair the sites from site production I get  "failed to acquire Token from SSO server at 'https://mysite-dr/sts/STSService/mydomain'". Can any one help slve this problem?

Hello,

I have a question in regards to SRM 6.0. and I am not sure if anyone has worked on it before.

Do I need to have two different vCenters to utilize the recovery features of SRM between two sites ?

Or it can work fine if there is only one vCenter managing both sites ?

I am asking about an environment where we are deploying SRM 6.0, vCenter 6.0 and vSphere 6.0

Regards

Hello,

I'm preparing to configure my array manager but I have a few questions.  This is a demo environment, however the XIV I am connecting to also hosts production machines.  I'm trying to understand exactly how much access I'm going to giving my demo environment once I have entered the information below.

Am I correct in assuming that my demo hosts will only be able to perform tasks against the storage LUNs which have been specifically presented to it?  I'm just want to understand how this works so that I am able to assure the stake holders of the production machines that this does not present any risk at all to their machines.

I know misconfigurations can happen, particularly in a demo environment, I just want to know for sure that although I am connecting to the XIV itself I can't do anything to VMs which the ESXi hosts do not have visibility of.

Thanks.