Resolving VSS_WS_FAILED_AT_FREEZE Backup Errors
The backup error VSS_WS_FAILED_AT_FREEZE may occur with several types of writers, such as the Hyper-V VSS Writer or Registry Writer.
We have a tool to diagnose all kinds of VSS errors, called VssDiag available at //backupchain.com/VssDiag.html
The important thing is to enter the backup error time as accurately as possible, within a 5 minute window and the tool will find all relevant error details stored in Windows logs.
Most often, this error is caused indirectly by a different application or service, and chances are that service will also log its error in the Event Viewer. Because VSS is a framework where services, such as Exchange, SQL, and Windows itself, hook into, failures such as VSS_WS_FAILED_AT_FREEZE may be caused by a configuration or resource issue solely related to external service applications.
The freeze has to do with how long application “writers” have to hold their write access to disk. Usually that’s 60 seconds or less. Because some writers use a shorter timeout than 60 secs, the system may give freeze errors more often with disk I/O is high. Our VssDiag tool should be helpful in determining which service causes the problem. Most of the time it’s Microsoft Exchange, SQL Server, or the system registry service.
After examining the errors found by VssDiag, restart the services: COM+ System Application Service, Distributed Transaction Coordinator Service, and Volume Shadow Copy Service
You may also want to check our VSS Troubleshooting Guide at //backupchain.com/hyper-v-backup/Troubleshooting.html
Backup Software Overview
Server Backup SoftwareDownload BackupChain
Cloud Backup
Backup VMware Workstation
Backup FTP
Backup VirtualBox
Backup File Server
Hyper-V Backup
Backup Hyper-VPopular
- Hyper-V Links, Guides, Tutorials & Comparisons
- Veeam Alternative
- How to Back up Cluster Shared Volumes
- DriveMaker: Map FTP, SFTP, S3 Site to a Drive Letter (Freeware)
Resources
- Free Hyper-V Server
- Remote Desktop Services Blog
- SCDPM Blog
- SCOM Blog
- V4 Articles
- Knowledge Base
- FAQ
- Archive 2024
- Archive 2022
- Archive 2021
- Archive 2020
- Archive 2018
- Archive 2017
- Archive 2016
- Archive 2015
- Archive 2014
- Archive 2013
- Hyper-V Scripts in PowerShell
- FastNeuron
- BackupChain (Greek)
- BackupChain (Deutsch)
- BackupChain (Spanish)
- BackupChain (French)
- BackupChain (Dutch)
- BackupChain (Italian)
Backup Software List
BackupChain
Veeam
Unitrends
Symantec Backup Exec
BackupAssist
Acronis
Zetta
Altaro
Windows Server Backup
Microsoft DPM
Ahsay
CommVault
IBM
Other Backup How-To Guides
- Hyper-V Server 2008 R2: Important Hotfixes and Updates
- New: Backup Software Comparison and List
- Hyper-V Stop 0x0000000A BSOD Error Causes and Fixes KB2776366
- 8 Tape Backup Disadvantages and Issues You Need To Know
- Granular Backup Software for Hyper-V
- Windows 11 Final Release Free ISO Download Links
- How to Update Windows Offline Without an Internet Connection
- How to Backup VMware Workstation, VMs, VMDK Files
- What are Hyper-V Checkpoints, Snapshots, and VSS?
- VMware Workstation Speed-Up, How to Fix Slow Performance
- Hyper-V Server 2016 Download Locations + 2012 R2, 2008
- How to fix: 0x800423f4, The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur
- How to Fix VSS Timeout Error VSS_E_FLUSH_WRITES_TIMEOUT
- Hyper-V, VMware, VirtualBox Feature Comparison
- Copy a File From the Host to a VM Using a Powershell Script
- What is Deduplication?
- Hyper-V Cluster 2012 R2 Setup Instructions, Simple and Quick
- Hyper-V Best Practices You Must Know
- Hyper-V Backup Quick Start Guide
- How to Fix VolSnap Error ..a critical control file could not be opened