Image and clones are created and deleted using the PowerShell module in a nightly automation. Every now and then one of the images fails to delete “because it's being used by another process”. Restarting the clone agent service and trying to remove the image via the PoSh module doesn't work. There aren't any logs I could find to help give more detail on the issue to prevent it from happening in the future.
The image isn't associated with any clones according to the GUI and database backend (clone report as deleting fine in the GUI and backend db - but related clone dir and disk.vhd exists). I was unable to drop this either parent or clone image. From what I've gathered so far, this appears to be related to clone image corruption (only 1 clone of dozens affected and prohibiting db image from deleting).
Note:
- AV exclusions applied against all services, executables, dirs, extensions, and files related to SQL Clone. No other software or scanning is reading these files and confirmed via ProcMon.
- Tried to remove the clone vhd both ignoring and respecting the parent image. Both methods fails with the same error. GUI and PoSh module also fail.
Version: v5.6.21.8347 (would upgrade, but release notes don't mention anything specific and if this is resolved)
Any idea if this will be resolved soon and if not a workaround that could be built into the scripts we used to automate this to ensure the clone creation/deletion process is bulletproof? We've included a lot of error handling and retries where we can but there isn't a reliable way to handle these stuck images.
Image and clones are created and deleted using the PowerShell module in a nightly automation. Every now and then one of the images fails to delete “because it's being used by another process”. Restarting the clone agent service and trying to remove the image via the PoSh module doesn't work. There aren't any logs I could find to help give more detail on the issue to prevent it from happening in the future.
The image isn't associated with any clones according to the GUI and database backend (clone report as deleting fine in the GUI and backend db - but related clone dir and disk.vhd exists). I was unable to drop this either parent or clone image. From what I've gathered so far, this appears to be related to clone image corruption (only 1 clone of dozens affected and prohibiting db image from deleting).
Note:
- AV exclusions applied against all services, executables, dirs, extensions, and files related to SQL Clone. No other software or scanning is reading these files and confirmed via ProcMon.
- Tried to remove the clone vhd both ignoring and respecting the parent image. Both methods fails with the same error. GUI and PoSh module also fail.
Version: v5.6.21.8347 (would upgrade, but release notes don't mention anything specific and if this is resolved)
Any idea if this will be resolved soon and if not a workaround that could be built into the scripts we used to automate this to ensure the clone creation/deletion process is bulletproof? We've included a lot of error handling and retries where we can but there isn't a reliable way to handle these stuck images.