AppSync: Unmount Filesystem Fails During Restore Phase
Summary: AppSync: Unmount Filesystem Fails During Restore Phase
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.
Symptoms
AppSync Event Log:
2018-01-17 14:14:08.133,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,HST_000016,abc,Failed to unmount one of the production file systems for restore: E:\, D:\. Ensure there is no other application using this file system.
2018-01-17 14:14:08.133,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,GENL_000039,abc,Restore operation failed. Performing cleanup activities.
2018-01-17 14:14:07.248,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,VSS_000041,abc,VDS filesystem unmount failed on host 11.1.1.1. See the host plug-in log and application event log for details.
2018-01-17 14:14:07.248,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,HST_000036,11.1.1.1,The file system E:\ is currently being accessed and cannot be unmounted to perform a restore.
2018-01-17 14:14:07.08,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,HST_000014,abc,Unmounting production file systems E:\, D:\ to prepare for restore.
2018-01-17 14:14:07.064,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,SQL_000046,11.1.1.1, Database DB_Test01_20180118 does not exist.
2018-01-17 14:14:08.133,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,GENL_000039,abc,Restore operation failed. Performing cleanup activities.
2018-01-17 14:14:07.248,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,VSS_000041,abc,VDS filesystem unmount failed on host 11.1.1.1. See the host plug-in log and application event log for details.
2018-01-17 14:14:07.248,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,HST_000036,11.1.1.1,The file system E:\ is currently being accessed and cannot be unmounted to perform a restore.
2018-01-17 14:14:07.08,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,HST_000014,abc,Unmounting production file systems E:\, D:\ to prepare for restore.
2018-01-17 14:14:07.064,Restore copy,abf8dbeb-13d1-4ccd-8557-1037b8a6d41d,SQL_000046,11.1.1.1, Database DB_Test01_20180118 does not exist.
AppSync Plugin Log:
2018-01-17 14:14:10.902 INFO [1648] [] [def] [b072adba-8da0-498e-a198-eceb285ff339] VdsAgent::VerifyNoVolumesInUse - filesystem : E:\ , volume guid : \\?\Volume{17be14bf-55eb-450e-ad3a-3b146a104247}\
2018-01-17 14:14:10.902 INFO [1648] [] [def] [b072adba-8da0-498e-a198-eceb285ff339] VdsAgent::VerifyVolumeNotInUse - mount point info before restore - path : \\?\Volume{17be14bf-55eb-450e-ad3a-3b146a104247}
2018-01-17 14:14:10.923 INFO [1648] [] [def] [b072adba-8da0-498e-a198-eceb285ff339] VdsAgent::VerifyVolumeNotInUse - DeviceIoControl(..,FSCTL_LOCK_VOLUME,...) failed. error :5
2018-01-17 14:14:10.923 INFO [1648] [] [def] [b072adba-8da0-498e-a198-eceb285ff339] VdsAgent::PerformRestoreUnmountOperation - volume E:\ is busy, aborting restore
Cause
Only one Database was being restored.
It was observed that 2 databases were using the same location for their respective data files (a directory in D drive) and same location for their respective log files (a directory called Log in E drive).
AppSync affected entities rules were not being adhered to here. Following is from the admin guide.
===============================================================================================================
If the affected entity was protected along with the database that is selected for restore, it will be restored by AppSync. Any other database that was not protected but is an affected entity will be overwritten.
AppSync calculates affected entities for the consistency groups or LUN groups of the database that is selected for restore. If the affected databases in turn partially reside on other consistency groups or LUNs groups, AppSync does not calculate affected entities on those consistency groups or LUN groups. Depending upon the type of affected entity, the affected databases are detached by AppSync or you must manually detach them from the SQL Server instance.
===============================================================================================================
It was observed that 2 databases were using the same location for their respective data files (a directory in D drive) and same location for their respective log files (a directory called Log in E drive).
AppSync affected entities rules were not being adhered to here. Following is from the admin guide.
===============================================================================================================
If the affected entity was protected along with the database that is selected for restore, it will be restored by AppSync. Any other database that was not protected but is an affected entity will be overwritten.
AppSync calculates affected entities for the consistency groups or LUN groups of the database that is selected for restore. If the affected databases in turn partially reside on other consistency groups or LUNs groups, AppSync does not calculate affected entities on those consistency groups or LUN groups. Depending upon the type of affected entity, the affected databases are detached by AppSync or you must manually detach them from the SQL Server instance.
===============================================================================================================
Resolution
From the management studio, both databases were made offline and restore was tried. It worked.
Affected Products
AppSyncProducts
AppSyncArticle Properties
Article Number: 000057419
Article Type: Solution
Last Modified: 18 Sept 2025
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.