When operating under Windows Server 2008 or later, problems related to Windows Server 2008 or later disk management may make it impossible to lock volumes that are not being used by applications or services.
Details of this problem and a patch module are available at the following URL (Microsoft online support KB952790):
http://support.microsoft.com/kb/952790/en
Since volumes may be locked when AdvancedCopy Manager is executing the following commands, execution of these commands may be affected by this problem.
swsrpvssbackup_exchange (Exchange VSS backup execution command)
swsrpvssrestore_exchange (Exchange VSS restore execution command)
The following message will be displayed if the above problem affects execution of a command:
[swst3607 or swsrp3607] Locking the volume failed. Please confirm that the volume is being used by other processes. Error=[ERROR], Volume Name=[VOLUME] |
If the above message is output frequently, it is recommended to apply the patch module from the above URL (Microsoft online support KB952790).
Alternatively, the problem may be resolved by remounting the volume indicated at [VOLUME NAME] in the error message. By way of a temporary counter-measure, the volume dismount methods are described below. Note that the mounting of the dismounted volume is performed automatically by the OS when the volume is accessed.
Use the following procedure to dismount a volume:
Check that the volume for which the problem occurred is not being used by an application or service.
When a volume is dismounted, all handles that are open for that volume are disabled.
Use the handle-exe tool, available from the following URL, to identify the processes that are using the volume:
http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx |
For example, to identify the processes that are using the E: drive, execute " handle.exe E:" from command prompt.
Execute the following command to dismount the volume:
If, for example, the name of the volume for which this problem occurred is "g1d1p1", execute "swstdismount g1d1p1" from command prompt.
If this problem affects operations frequently, "LockForceMode=on" can be set in the volume lock operation specification file. This resolves the problem by performing an automatic volume dismount operation before copy is executed.
In this case, ensure that applications and services are not using the volume when copy is executed.
When a volume is dismounted, all handles that are open for that volume are disabled.
Refer to the following sections for the settings in the volume lock operation specification files:
If the above problem occurs for the restore source backup volume, use the method described above under "Dismount method using commands" to dismount the volume.
