I have a requirement of creating protection group which includes 30 datastores and 450 vms.

Any suggestions ? I haven't come across such huge protection group. How does this work as expected in real world ?

SRM version : 8.1

Hello, could you help with a case that I have

I wonder if it's possible to protect a vCenter and SRM VMs using SRM?

We have Two vCenter Servers, one on each site, they both have their own PSC however vCenter 2 is connected to PSC of vCenter 1, that means if vCenter 1 will be down, vCenter 2 will still work albeit somewhat limited with just it's own connected hosts. Each Site has it's own SRM Instance installed as a Windows VM (SRM 8.1.2) with VNX + MirrorView SRAs.

Is it possible to do a planned migration of a array-based replication Protection Group which contains vCenter and SRM VMs (vCenter 1 site) to the other site? Is that even doable? Or should I turn off those VMs on Site 1 and do a Disaster Recovery option (or even Forced Recovery)? It's just for test purposes, our clients wants to make sure everything is up and running correctly.

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

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?

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

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?

Hi

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

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?

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

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

How to Run Power shell script in SRM 8.2 Pre Script Action . Kindly suggest

Note : SRM 8.2 is appliance

Im  testing SRM evaluation version at  the moment Im  using replication  appliance for replication and SRM on windows

I would like add storage  replication adaptors for array based  replication  but I don't  have such  option, -

I would  like  to  know  if on full licence I will be able  to add new SRA and  this  version  this  will be possible if  have storage from different  vendors ( I have already  drivers  for both adaptors  from EMC and HP)

I  have  following storage

on site A- EMC Unity and HP mse 5052 storage on site B

i install SRM appliance 8.2, but due to some challenge we uninstall it. i un-register from one site and delete the SRM VM, but from second site i delete VM directly without un-register.

now i install Windows base SRM 8.1, installed successfully but showing as below. is there any way to clean it.

VCenter has failed and was replaced with a new instance of vcenter, but when I try to remove the old one from SRM 8.2 appliance, breaking site pair fails. Assumption is it can’t connect to the removed vCenter(PSC). Any suggestion how to clean it up?

Hello All,

I installed a pair of SRM 8.1.1 servers associated with respective vCenter servers (6.7U1) in Protected and Recovery Sites. Create a new pair operation was successful as well. Protection Groups and Recovery Plans were created seamlessly.

After one day I started getting the following SRM errors:

srmxxx SRM Server cannot connect to VC Server at vcyyy:443/sdk'. Permission to perform this operation was denied.

srmxxx SRM Server cannot connect to SRM Server at 'srmyyy:9086/vcdr/vmomi/sdk'. Permission to perform this operation was denied.

srmyyy SRM Server cannot connect to VC Server at 'vcxxx:443/sdk'. Permission to perform this operation was denied.

srmyyy SRM Server cannot connect to SRM Server at 'srmxxx:9086/vcdr/vmomi/sdk'. Permission to perform this operation was denied.

We still have one External PSC ( that would be decommissioned soon) and all vCenters 6.7 with embedded PSC because we are during VMware Infra upgrading process.

I used domain administrator account namely administrator@vsphere,local on both sides.  I could not find any additional information in SRM logs.

Reconfigure Site Pair operation was already done and it does not help. Change installed SRM from Windows 2012 R2 Control Panel is blocked due to UAC restriction that is imposed by GPO domain policy.

How can we explain that administrator@vsphere.local account can generate "Permission to perform this operation was denied" error?

Of course log on to the vCenter Appliance via mentioned administrator account is still successful.

What can be a nature of this kind of error? Should I suspect Firewall Settings issue or internal SRM problem?

Is it possible that External PSC that is currently not associated with any SRM server can be a disruptive source?

Any suggestions would be appreciated.

is SRM 5.5 still available for purchase or trial in lab for site failover test in preparation to upgrade to new VMWare version?

Hi,

I have SRM configuration deployed in environment. All version 8.2 and vCenter with version 6.7. Protected site and recovery site vCenters are in linked mode.

Setup is like below:

Protected Site: Site1 with SRM appliance SRM1 and VR appliance VR1

Recovery Site: Site2 with SRM appliance SRM2 and VR appliance VR2

Issue is when I go to Site Recovery option on vCenter, I see two options for Open Site Recovery one for protected and other for recovery, and when I clink them I can only open protected site SRM UI and recovery site SRM UI fails.

Protected site SRM UI link is as SRM1.fqdn/dr

But as I checked, recovery site SRM UI is changed to VRM2.fqdn/dr, so when I clink on open site recovery from vcenter is fails to load as it re-directs me to SRM2.fqdn/dr

As of now, all is working fine now, both sites connectes, pairing is ok, VR is working and also recovery is working. But the management UI link is changed to VR appliance instead of SRM appliance.

Any suggestions here?

Hello,

I'm having an issue installing SRM 6.0.0-2700495 in my vCenter 6 environment vCenter Server 6.0.0, 2776510 (appliance).

There error is:

The time skew between the Site Recovery Manager host and the vCenter Server is too large.

This is very odd since I set both the vCenter appliance and the host that it's running on are configured to use an NTP server (time.windows.com).  I have also tried setting the vCenter appliance to sync its time with the host.  As you can see from the screenshot, there does appear to be a time sync issue of approximately 5 minutes.

Any suggestions?  Is this error just another red herring or do I have an actual time sync issue??

Thanks.

vCenter version - 6.5

SRM version - 6.5

SRM is successfully installed on both the vCenter but when i goto vCenter>Configuration>vSphere Replication>Target Sites and tries to connect the remote site the connection fails with the following message:

The "Reconnect site" operation failed for the entity with the following error message.

Server https://172.16.137.250:8043 is not available.

In SRM logs, i see the following :

2018-12-12T16:31:41.130Z warning vmware-dr[06888] [Originator@6876 sub=LocalHms] Ping failed:

--> (hms.fault.NotAuthenticated) {

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

-->    faultMessage = <unset>,

-->    originalMessage = "java.util.concurrent.ExecutionException: com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 503",

-->    serverUuid = "edf5ce02-b654-4423-83ea-545fdd2a6205"

-->    msg = "Received SOAP response fault from [<cs p:0000020709167230, TCP:192.168.217.239:8043>]: checkCurrentSessionHealth

--> User is not authenticated."

--> }

--> [context]zKq7AVMEAQAAANeBiAAKdm13YXJlLWRyAAA/+wVobXMtdHlwZXMuZGxsAAEkxQV2bW9taS5kbGwAAZ/jBQILfBh2bWFjb3JlLmRsbAACHIwYAgkVIgN/TwJNU1ZDUjEyMC5kbGwAAyZRAgRkgwBLRVJORUwzMi5ETEwABdFwBm50ZGxsLmRsbAA=[/context]

2018-12-12T16:31:41.131Z verbose vmware-dr[05856] [Originator@6876 sub=StubFactory] Event broadcasted

2018-12-12T16:31:41.131Z verbose vmware-dr[06888] [Originator@6876 sub=StubFactory ctxID=1b50b77] Removed last known event. Starting the event timer...

2018-12-12T16:31:41.131Z verbose vmware-dr[06888] [Originator@6876 sub=ServerSingletonCache ctxID=1b50b77] Removed last known event. Starting the event timer...

2018-12-12T16:31:41.131Z warning vmware-dr[06888] [Originator@6876 sub=LocalHms HMSUM ctxID=1b50b77] The persistent HMS connection is down.

2018-12-12T16:31:41.134Z verbose vmware-dr[06916] [Originator@6876 sub=vmomi.soapStub[40]] Resetting stub adapter for server <cs p:0000020709167230, TCP:192.168.217.239:8043> : Closed

2018-12-12T16:31:41.582Z warning vmware-dr[06916] [Originator@6876 sub=LocalPbmServer] Ping failed:

--> (vmodl.fault.SystemError) {

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

-->    faultMessage = <unset>,

-->    reason = "Invalid fault"

-->    msg = "Received SOAP response fault from [<cs p:0000020708d14240, TCP:192.168.217.250:443>]: fetchResourceType

--> java.lang.RuntimeException"

--> }

--> [context]zKq7AVMEAQAAANeBiAAKdm13YXJlLWRyAAACIxJ2bW9taS5kbGwAACTFBQCf4wUBC3wYdm1hY29yZS5kbGwAARyMGAEJFSICf08CTVNWQ1IxMjAuZGxsAAImUQIDZIMAS0VSTkVMMzIuRExMAATRcAZudGRsbC5kbGwA[/context]

2018-12-12T16:31:41.583Z verbose vmware-dr[06876] [Originator@6876 sub=StubFactory] Event broadcasted

2018-12-12T16:31:41.583Z verbose vmware-dr[06916] [Originator@6876 sub=StubFactory ctxID=323996bb] Removed last known event. Starting the event timer...

2018-12-12T16:31:41.583Z verbose vmware-dr[06916] [Originator@6876 sub=ServerSingletonCache ctxID=323996bb] Removed last known event. Starting the event timer...

Hi,

Cant seem to find any documentation on this so i thought id post the question here.

Only just noticed, one of the scheduled snapshots has been In-Progress for the last month. I've tried to delete it but without success. What's the safest way to stop and delete this. i know the root cause of the issue, which i have fixed but need to safely remove/delete this.

running SRM version 6.5.1

there are several other volumes being snapshot'd every couple of hours.

Is it a simple case of ensuring no other snapshot is in-progress, restarting the SRM service on the SRM Server? and if that fails, any other suggestions?

thank you