VMware Cloud Community
zomb66
Contributor
Contributor
Jump to solution

vsphere5.5 + srm 5.5 = recovery unmount datastore error

Good afternoon.

Structure recently updated to vsphere 5.5 and to SRM 5.5.

Planned migration works well. There was a problem with Disaster Recovery.

Simulate the situation :

1) We have two protected VM, turn off the power at the hosts , I go to the recovery site and run the Disaster Recovery.

The following errors appear in the course of the recovery process. It's normal, because hosts due to inactivity.

Here is the errors :

Shutdown VMs at Protected Site - Error - Unable to communicate with the remote host, since it is disconnected. Unable to communicate with the remote host, since it is disconnected.

Prepare Protected Site VMs for Migration - Error - The operation is not allowed in the current connection state of the host. The operation is not allowed in the current connection state of the host. Failed to unregister protected VMs.

Change Storage to Read-only - Error - Failed to unregister protected VMs. Failed to unregister protected VMs.

2 ) Go to the recovery site , everything seems to be fine. SRM offers do again Recovery, because there were errors. Power ON hosts, do recovery and it was here that the problems begin. Begin to pour in error about the impossibility to unmount the datastore , namely :

Error - Cannot unmount datastore 'DS1' from host 'host1'. The resource 'DS1' is in use.

DS1 - datastore in the protected site , host1 - host in protected site, where powered on VM before recovery process

Remarkably, manually unmount the datastore this too does not work. Only helps to reboot the host again , but it does not matter .

Who can tell what's wrong or who have experienced this when working with SRM? kb is suitable for my case is not found.

Under 5.1 and it works fine .

Thanks in advance for your help

Tags (4)
0 Kudos
1 Solution

Accepted Solutions
zomb66
Contributor
Contributor
Jump to solution

Problem fix.

Default per host - /var/log/vsantraces -> simlink to datastore.

esxcli vsan trace set -p /var/log/vsan

View solution in original post

0 Kudos
1 Reply
zomb66
Contributor
Contributor
Jump to solution

Problem fix.

Default per host - /var/log/vsantraces -> simlink to datastore.

esxcli vsan trace set -p /var/log/vsan

0 Kudos