Article ID: 8005
Product Version: CloudBacko Go 8.5 or above
Operating System: Windows
Cannot backup exclusively opened file (on Windows platforms) on a local hard disk.
There are many underlying components in the operating system that may come into play during the backup process to cause the VSS error. This article offers a guideline on how to troubleshoot for errors related to Volume Shadow Copy.
The following are some steps to follow for troubleshooting errors related to Volume Shadow Copy (these steps may vary depending on the operating system):
Prerequisites of Volume Shadow Copy
Which version of Windows are you using?
Ensure that the CloudBacko Go client application is installed on a supported Windows platform. Refer to the following article for the software requirement list:
Software Requirement List
Reboot the affected machine
Have you restarted the affected computer recently?
Try rebooting the affected machine. In some instances, servers that have not been rebooted in a while may cause VSS malfunction. Reboot your server regularly as a preventive and cleanup measure for your system.
Volume Shadow Copy Service (VSS)
Ensure that the VSS service is started or can be started properly. Restart the VSS service with the following procedure:
Re-register VSS files
Perform the following procedures to ensure that all VSS related components are correctly registered:
In an administrative command prompt, execute the 'RegisterVSS.bat' script file available in the CloudBacko Go installation home, reboot the machine afterward.
You can safely ignore the error message(s) displayed during the process, some of the DLL files are platform specific.
Latest Windows updates from Microsoft
Have you installed the latest Windows Updates on the affected computer?
Check if you have installed the latest Windows Updates. There may be known issues identified by Microsoft that can be resolved in a hotfix / update:
Damaged COM+ catalog (for older Windows platforms such as Windows Server 2003)
Are the COM+ catalog on the affected computer damaged?
Refer to the instructions provided in the following document to clean up the COM+ catalog:
In some cases, Visio, which is part of Microsoft Office 2003 can cause Volume Shadow Copy to fail. Leverage the event logs found under Event Viewer.
For machine with Visio installed, check if the following event is found:
Event Type: Error
Event ID: 5013
Volume Shadow Copy Service error: Shadow Copy writer ContentIndexingService called routine VsServiceChangeState which failed with status 0x8007041d (converted to 0x800423f4).
To resolve the issue, delete the following registry key with regedit.exe, reboot the computer afterward:
Volume Shadow Copy (VSS) related issue
Troubleshoot for VSS related issue. Refer to the following instruction:
Ensure that status of all VSS writers and providers are stable:
|>vssadmin list writers|
All writer should have status of  Stable.
|>vssadmin list providers|
If no provider is listed, there may be issue with the installation of operating system itself. Resolution should be pursued with Microsoft support staff.
Ensure that left-over snapshots are cleaned up:
|>vssadmin delete shadows /all|
This will clean up all VSS snapshots.
Defective operating system may often accumulate hundreds of VSS snapshots that persist in the system and cause Windows to become un-responsive.
In some case, you may not be able to delete the VSS snapshots with the above command. Perform the following instead:
|>vssadmin resize ShadowStorage /For=C: /On=C: /MaxSize=300MB|
If there is no VSS writer error displayed, but the system is not creating a new VSS snapshot, increase the max shadow storage size on the system instead.
|>vssadmin resize ShadowStorage /For=C: /On=C: /MaxSize=10GB|
Problem persist after going though all steps outlined above?
Issue related to the Volume Shadow Copy (VSS) Windows services, or the Windows operating system itself should be further pursued with Microsoft support staff.
VSS, volume, shadow, copies, VSC, VS