Great work - thank you very much for sharing!

Okay, my question is, is it possible to "Recover" a vCenter and SRM virtual machines with the SRM? Unfortunately vMotion is out of question, same goes to the HA.

Is a planned migration possible? We want to test the scenario when the whole site has to go offline but without losing data INCLUDING vCenter and SRM virtual machines.

Okay, I couldn't edit my answer so I add a new comment.

I tested the SRM VM recovery and I got two things, Planned Migration is not possible. I started the migration from the Site 2 SRM instance and Recovery Plan got stuck at Shut Down VM at protected site step.

After that I did a Forced Recovery and that really messed up some stuff, yes, SRM machine got switched to the other DC however it really screwed the MirrorView setup on VNX Storage, hosts that had any of the VMs from the switched datastore got stuck and their management agents just refused to work and communicate with vCenter. The thing that helped with this was a MirrorView Synchronization and switching Secondary to Primary Image.

I'm probably gonna test switching vCenter with both scenarios and write back, It might be useful to somebody since there is literally no information about switching SRM and vCenter using SRM.

We deployed the SRM appliance, when we browse the website on :5480 we are getting error java.exception: connection refused. Any workaround please. TIA.

Please read the first post in my signature and try another response.

Author : Iliyan Iliev

URL : http:////docs.vmware.com/en/Site-Recovery-Manager/8.2/com.vmware.srm.install_config.doc/GUID-52AFACF8-BEEF-43DE-BE4F-8B8DE802C8D7.html

Topic Name : Reconfiguring the Site Recovery Manager Virtual Appliance

Publication Name : Site Recovery Manager Installation and Configuration

Product/Version : Site Recovery Manager/8.2

Question :

Need to rename the 3PAR replicated storage used with SRM.  Can the be done dynamically or should I first remove the Recovery Plan and Protection Group and then recreate them?

Hi

We are using vSAN stretched cluster. Strat to look at SRM as site reocvery orchsteration motor. Does SRM requires 2 vCenters ?

Yes, you need multiple vCenters.

The regular way

1. Install SRA on Vcenter servers from the respective Storage vendor

2. Input Storage Management Ip address and login credentials.

I have a requirement where the VMware in different network and Storage management IP addresses are in different network. There is a strict firewall rule which cannot be comprised. Thinking of having API Proxy in between which can route.

Does this solution work?

Author : Iliyan Iliev

URL : http:////docs.vmware.com/en/Site-Recovery-Manager/8.2/com.vmware.srm.admin.doc/GUID-71946C95-1C68-4572-8F3F-BA2D0ECB2242.html

Topic Name : Configure Array-Based Replication

Publication Name : Site Recovery Manager Administration

Product/Version : Site Recovery Manager/8.2

Question :

Example: To create a snapshot how the rest API calls are made from SRM to Storage Array

Moderator: Moved to Site Recovery Manager

After double-checking with engineering:

You should first remove the Recovery Plan and Protection Group and then recreate them.

Thank you for the confirmation.  That is what I have done and all works fine.

Hello,

The actual communication to the storage array is handled by SRA. SRA is vendor specific component. It's up to the storage vendor how to implement the communication between SRA and their storage array, SRM has nothing to do with that.

SRM 8.2 communicates with the SRA using a simple command entry point - in SRM Windows it's a perl script (command.pl) and in SRM Virtual Appliance it's just "command" that transfers the data to the SRA packaged as a Docker container.

For more details I would recommend to check the attached SRA specs:

1) Sra20Spec.pdf - this is the main SRA spec document describing all the SRA commands format of requests/responses etc.

2) Sra20ContainerizedSRAs.pdf - this is an appendix specially that explains the containerized SRAs for VA

Regards,

Kris

I have a site with failed SRM server, no information can be restore/recovered from the host. Data replication is array based (RecoverPoint). vCenter version is 6.5.

What is the recommend way to approach to restore SRM functionality for the site?

Moderator: Moved to Site Recovery Manager

Hi all

We are using vCenter 6.0 and SRM 6.1.1, and working well for few years, and then we need to upgrade the vCenter 6.0 to U3. Once updated, then the SRM plug-in disappear in the vCenter. Then I go to check the compatibility matrix and found that vCenter 6.0 U3 need to work with 6.1.2, so I go to upgrade the SRM to 6.1.2. But unfortunately I still cannot see the SRM plug-in in the vCenter after upgrade. Then I go to check the vsphere_client_virgo.log and find the below error? Anyone have experience on this?

Log search by Error

[2019-11-22T13:44:58.216+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/rsls' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/rsls' already exists

[2019-11-22T13:44:58.220+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.rsls' version '6.1.2': a web application with context path '/vsphere-client/srm/rsls' already exists.

[2019-11-22T13:44:58.223+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.rsls' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

[2019-11-22T13:45:06.923+08:00] [ERROR] srm-topology-thread-4         c.v.srm.client.topology.impl.vmomi.osgi.VmodlContextInitializer   Failed to load package 'com.vmware.vim.binding.cis.metadata'. org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [com/vmware/vim/binding/cis/metadata/context.xml]; nested exception is java.io.FileNotFoundException: class path resource [com/vmware/vim/binding/cis/metadata/context.xml] cannot be opened because it does not exist

[2019-11-22T13:45:11.523+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/srm-bootstrap' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/srm-bootstrap' already exists

[2019-11-22T13:45:11.526+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.srmbootstrap' version '6.1.2': a web application with context path '/vsphere-client/srm/srm-bootstrap' already exists.

[2019-11-22T13:45:11.529+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.srmbootstrap' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

[2019-11-22T13:45:15.735+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/inventory-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/inventory-ui' already exists

[2019-11-22T13:45:15.738+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.inventoryui' version '6.1.2': a web application with context path '/vsphere-client/srm/inventory-ui' already exists.

[2019-11-22T13:45:15.741+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.inventoryui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

[2019-11-22T13:45:18.062+08:00] [INFO ] region-dm-12                  o.s.beans.factory.support.DefaultListableBeanFactory              Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1b1ee5b5: defining beans [addEditArrayManagerMutationProviderImpl,rescanSraMutationProviderImpl,arrayPairsMutationProviderImpl,discoverArrayPairsMutationProviderImpl,discoveredArrayPairsProvider,connectionParamProvider,arrayManagerStatusProvider,arrayManagerInformationProvider,arrayPairProvider,arrayManagerSiteProvider,storageDevicesProvider,arrayDiscoveryStatusFaultProvider,collectDatastoresProvider,discoveredArrayPairsIssueAdapterImpl,sraErrorIssueAdapterImpl,pingFailedIssueAdapterImpl,arrayManagersRootsProviderImpl,storageManagersProviderImpl,addEditArrayManagerMutationProvider,rescanSraMutationProvider,arrayPairsMutationProvider,discoverArrayPairsMutationProvider,org.eclipse.gemini.blueprint.service.exporter.support.OsgiServiceFactoryBean#0,org.eclipse.g...

[2019-11-22T13:45:18.062+08:00] [INFO ] region-dm-12                  o.s.beans.factory.support.DefaultListableBeanFactory              Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1b1ee5b5: defining beans [addEditArrayManagerMutationProviderImpl,rescanSraMutationProviderImpl,arrayPairsMutationProviderImpl,discoverArrayPairsMutationProviderImpl,discoveredArrayPairsProvider,connectionParamProvider,arrayManagerStatusProvider,arrayManagerInformationProvider,arrayPairProvider,arrayManagerSiteProvider,storageDevicesProvider,arrayDiscoveryStatusFaultProvider,collectDatastoresProvider,discoveredArrayPairsIssueAdapterImpl,sraErrorIssueAdapterImpl,pingFailedIssueAdapterImpl,arrayManagersRootsProviderImpl,storageManagersProviderImpl,addEditArrayManagerMutationProvider,rescanSraMutationProvider,arrayPairsMutationProvider,discoverArrayPairsMutationProvider,org.eclipse.gemini.blueprint.service.exporter.support.OsgiServiceFactoryBean#0,org.eclipse.g...

[2019-11-22T13:45:20.143+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/abr-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/abr-ui' already exists

[2019-11-22T13:45:20.146+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.abrui' version '6.1.2': a web application with context path '/vsphere-client/srm/abr-ui' already exists.

[2019-11-22T13:45:20.149+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.abrui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

[2019-11-22T13:45:24.440+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/group-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/group-ui' already exists

[2019-11-22T13:45:24.443+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.groupui' version '6.1.2': a web application with context path '/vsphere-client/srm/group-ui' already exists.

[2019-11-22T13:45:24.446+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.groupui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

[2019-11-22T13:45:28.706+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/plan-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/plan-ui' already exists

[2019-11-22T13:45:28.709+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.planui' version '6.1.2': a web application with context path '/vsphere-client/srm/plan-ui' already exists.

[2019-11-22T13:45:28.712+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.planui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

[2019-11-22T13:45:37.293+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/vm-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/vm-ui' already exists

[2019-11-22T13:45:37.296+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.vmui' version '6.1.2': a web application with context path '/vsphere-client/srm/vm-ui' already exists.

[2019-11-22T13:45:37.298+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.vmui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

[2019-11-22T13:45:37.306+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.core.model.CompositeException                     CompositeException

[2019-11-22T13:45:37.307+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353 com.vmware.vise.core.model.CompositeException: CompositeException

[2019-11-22T13:45:37.307+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353 com.vmware.vise.core.model.CompositeException: CompositeException

Log search by vcDr

[2019-11-22T13:44:56.415+08:00] [INFO ] vc-extensionmanager-pool-271  com.vmware.vise.vim.extension.VcExtensionManager                  Done expanding plugin package to /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353

[2019-11-22T13:44:56.416+08:00] [WARN ] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackageManifestParser            Plugin id mismatch between the registered extension key (com.vmware.vcDr)

[2019-11-22T13:44:56.416+08:00] [WARN ] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackageManifestParser            Plugin version mismatch for com.vmware.vcDr between the plugin registration info (6.1.2.16353)

[2019-11-22T13:44:56.421+08:00] [INFO ] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Deploying plugin package 'com.vmware.vcDr:6.1.2.16353'.

[2019-11-22T13:45:37.307+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353 com.vmware.vise.core.model.CompositeException: CompositeException

[2019-11-22T13:45:39.448+08:00] [WARN ] data-service-pool-307        70004163 100050 200040 com.vmware.vise.vim.data.adapters.search.impl.QueryExecutor       object with no server guid: urn:vri:cm:Service:e207e0da-b30c-4fb7-896b-2776ac26a58b_com.vmware.vcDr/MTAuMC4yMzMuMTA1 (class java.net.URI)

Best regards

Alex Tsang

First reboot vCenter web client and check again.

Then check this from release notes for SRM 6.1.2:

Site Recovery Manager disappears from the vSphere Web Client.

In a setup with federated vCenter Single Sign-On, Site Recovery Manager can disappear from the vSphere Web Client for one of the following reasons:

• You log in to either the protected site or the recovery site and the Platform Services Controller for that site is offline. The plug-in that was loaded last time you logged in is not deployed because a Platform Services Controller, vCenter Server, or Site Recovery Manager Server instance on that site that serves the Site Recovery Manager plug-in might be offline.
  Workaround: Restart the vSphere Web Client service.
• You installed Site Recovery Manager in a shared recovery site configuration, and you uninstalled one of the Site Recovery Manager instances that is registered with vCenter Server on the shared site. If you deleted all Site Recovery Manager data when you uninstalled the Site Recovery Manager Server instance, Site Recovery Manager disappears from the vSphere Web Client. None of the remaining Site Recovery Manager instances is available.
  Workaround: Restart the vSphere Web Client service.
• Site Recovery Manager Server on either the protected or the recovery site is offline. In this case, vSphere Web Client should download the Site Recovery Manager client plug-in from the remaining active site, but does not do so.
  Workarounds: Attempt these workarounds in order.
  1. Restart the Site Recovery Manager Server instance that is offline, or repair the connection between Site Recovery Manager Server and Platform Services Controller.
  2. If you cannot bring Site Recovery Manager Server online, uninstall and reinstall this instance of Site Recovery Manager Server.
  3. If you cannot uninstall Site Recovery Manager Server, for example because the virtual machine that it runs in cannot be started, unregister the Site Recovery Manager Server extension from the Managed Object Browser (MOB) of the vCenter Server instance for this site. You must then reinstall Site Recovery Manager.

And you can try:

Go to page: http://vCenter_Server_name_or_IP/mob

and check if you have registered SRM plugin, maybe you have plugin registered twice or something (login on administrator@vsphere.local user).

Here is KB how to do that:

VMware Knowledge Base

You can unregister SRM plugin and try to register it again.

Before you do anything, make a backup of vCenter, DB, SRM....

Moderator: Moved to Site Recovery Manager

Hello,

I have problem with SRM and two 3par.

My environment is configured in the following way:

protected site

a 3par 7200 (HPE 3PAR OS version Current 3.2.2.709 (MU6) + P99, P107, P119, P131, P135, P138, P139, P140, P149)

VMware-srm-va-8.2.0.3658-14761906

VMWare-vSphere_Replication-8.2.0-14761900

SRA version HPE3PARSRA_8.2.0.26.zip

Vcenter in vcsa 6.5.0 build 14836121 format

esxi 6.5.0 build 14990892

recovery site

a 3par 8200 (3.3.1.460 (MU3) + P49, P50, P53)

VMware-srm-va-8.2.0.3658-14761906

VMWare-vSphere_Replication-8.2.0-14761900

SRA version HPE3PARSRA_8.2.0.26.zip

Vcenter in vcsa 6.5.0 build 14836121 format

esxi 6.5.0 build 14990892

The 3par are in periodic sync replication

I created a recovery group on the 3par containing a lun with a vm. The vm is called testdr.

This recovery group was created to perform a test with srm.

I created a protection group that contains vm testdr and I created a recovery plan that contains only this vm.

First I tried to test the recovery plan and returned the following error:

Error- Failed to create snapshots of replica devices. Failed to create snapshot of replica consistency group DR-TEST.r38093. SRA command 'testFailoverStart' failed for consistency group 'DR-TEST.r38093'. Secondary volume <DR-TEST.r> is not exported to any host.

Please manually export the secondary volumes to corresponding host(s).

I solved the problem by exporting the lun to the revovery site.

In fact, I re-launched the test and it went well.

At this point I tried to do a recovery. I did a planned migration with storages synchronization.

The recovery plan is not successful and he reports the following error:

ERROR

Operation Failed Failed to demote source consistency group 'DR-TEST'. SRA command 'prepareFailover' failed for consistency group 'DR-TEST'. Unable to execute PrepareFailover command workflow. Additional information: [Errno 13] Permission denied: '/srm/sra/conf/data/rcgroupinfo_38093.xml' If the error is caused due to remote copy link down, you need to bring up the remote copy link and retry the operation. If the error is due to unexpected remote copy replication roles or group state, you need to check with your storage administrator for assistance. If the error is related to the network issue, you need to check if you have problem with your network connection.

I was looking on the internet to find a similar error in hpe

https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00068960en_us&docLocale=en_US

which is solved using the SRA version 6.5.6 which I cannot use.

Alternatively by reading the HPE 3PAR Storage Replication Adapter for 8.2.0 VMware® vCenter Guide Site Recovery Manager ™ User Guide it is stated that SRA parameters can be modified using the TpdSrm.exe command.

Unfortunately from what I understand this command is present only with SRA in windows version so I can't do anything.

Do you have any idea how to solve my problem?

How can I eliminate the recovery plan that is currently in an incomplete recovery state?

Thanks

Regards