AppSync: Virtual Machine Restore fails when mounting datastore on ESX host

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Upgrade to vCenter 6.5, and/or upgrade to AppSync 3.5 was involved in situations where this issue occurred.

When restoring a copy of a Virtual Machine from AppSync, the service plan fails with the following error.
  
Failed to mount datastore <datastore_name> on ESX <host_name>. Check the ESX on the VCenterServer for tasks and events, or alarms. Refer the troubleshooting guide if it's a HostPlatformConfigFault Exception.

Cause

AppSync issues a "queryUnresolvedVmfsVolume" command to vCenter as part of the process to mount the datastore to the ESX host. 

VCenter does not return a response in a timely manner and as a result, AppSync fails the restore.

Server Logs:
 
11-17-2017 08:54:22.795 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.vcenter.VCenterServiceBean] [AppSync Server Name] [] Executing checkForVisibility for ESX: <host_name>
11-17-2017 08:54:22.826 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.vcenter.VCenterServiceBean] [AppSync Server Name] [] Mount device:naa.600...xyz is visible on esx:<host_name> with state :ok
11-17-2017 08:54:22.826 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.vcenter.VCenterServiceBean] [AppSync Server Name] [] All target devices are visible on ESX:: <host_name>
11-17-2017 08:54:22.858 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.vcenter.VCenterServiceBean] [AppSync Server Name] [] the  scsiLun with uuid <UUID> is already attached.

11-17-2017 08:54:22.858 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.eventservice.EventServiceBean] [AppSync Server Name] [] EVENT [VM_000091]: Mounting the VMFS on ESX: <host_name>.

11-17-2017 08:54:22.858 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.vcenter.VCenterServiceBean] [AppSync Server Name] [] Issuing queryUnresolvedVmfsVolume to find out the volumes which are unresolved

11-17-2017 08:54:22.873 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.vcenter.VCenterServiceBean] [AppSync Server Name] [] Few more datastores are unresolved
11-17-2017 08:54:22.873 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.vcenter.VCenterServiceBean] [AppSync Server Name] [] rescanHBA : on ESX <host_name>
11-17-2017 08:54:24.811 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.vcenter.VCenterServiceBean] [AppSync Server Name] [] Retrying again after a rescan
11-17-2017 08:54:24.811 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.vcenter.VCenterServiceBean] [AppSync Server Name] [] Issuing queryUnresolvedVmfsVolume to find out the volumes which are unresolved


11-17-2017 08:54:34.453 INFO [Thread-629 (HornetQ-client-global-threads-1441291841)] [com.emc.archway.service.vcenter.VCenterServiceBean] [AppSync Server Name] [] Copy of the datastore with URL ds:///vmfs/volumes/<DATASTORE_ID>/is not found

Resolution

This issue is resolved in AppSync 3.7 which increases the number of retries for "queryUnresolvedVmfsVolume" and also increases the time interval between the retries.

Additional Information

Note: This issue may also arise when mounting a copy of a VMware datastore without restore, as the "queryUnresolvedVmfsVolume" command is also used this scenario.

Note: This change is not documented in the AppSync 3.7 release notes.

Products

AppSync
Article Properties
Article Number: 000057124
Article Type: Solution
Last Modified: 18 Sep 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.