Error: The flush and hold writes operation on volume timed out while waiting for a release writes command.
-
Getting this error in the Windows Event Viewer on Windows Server 2012 R2. Seems like we are getting a stall on the storage while waiting for Volume Shadow Copy to do its thing. Not finding a lot of information about this out there, the box is fully patched and up to date (for 2012 R2) and so isn't affected by the lack of patching as so many others seem to have been. So looking for the source of the issue.
We appear to get this error when Crashplan attempts to take a backup.
-
Also getting... Event 1283 stcvsm
"Flush-and-hold state was released while snapping due to timeout on \Device\HarddiskVolume1, cancelling snapping"
-
Wondering if the issue is that CrashPlan can't handle SQL Server and is causing delays because it is trying to back up the open files and not expecting VSS to take so long?
-
Does it use its own VSS service or Microsoft's?
-
@obsolesce said in Error: The flush and hold writes operation on volume timed out while waiting for a release writes command.:
Does it use its own VSS service or Microsoft's?
MS'
-
@scottalanmiller said in Error: The flush and hold writes operation on volume timed out while waiting for a release writes command.:
@obsolesce said in Error: The flush and hold writes operation on volume timed out while waiting for a release writes command.:
Does it use its own VSS service or Microsoft's?
MS'
Okay, in that case, can you verifying it works using Windows Server Backup as a quick test for some test data to backup something on that volume?
If VSS is working outside of Crashplan, my guess is Crashplan is the issue.
-
This might be Crashplan not supporting SQL Open files as you can see here:
https://support.code42.com/CrashPlan/4/Backup/Back_up_open_files_and_databases -
@dbeato said in Error: The flush and hold writes operation on volume timed out while waiting for a release writes command.:
This might be Crashplan not supporting SQL Open files as you can see here:
https://support.code42.com/CrashPlan/4/Backup/Back_up_open_files_and_databasesYes, we looked around to find some that weren't where they were supposed to be and might have been open. Hoping that that might end up being all that the issue was.
