Share via

Backup file are corrupted in Windows server

Anonymous
2024-12-16T06:45:29+00:00

I use a backup application that uses the Windows Volume Shadow Copy feature to create snapshots and read files from the snapshots, and found that there are a lot files were corrupted in many snapshots.

And I found that have been fixed in some version system, I wonder if the 2012 version has also been fixed?

https://support.microsoft.com/en-us/topic/backup-files-that-are-created-by-using-the-windows-volume-shadow-copy-feature-are-corrupted-in-windows-server-2003-windows-vista-windows-server-2008-windows-7-or-windows-server-2008-r2-c405b1e0-0183-0c45-3071-adfc7c199144#articleFooterSupportBridge=communityBridge

Windows Server High availability Virtualization and Hyper-V

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-12-17T01:52:36+00:00

    Hi,

    The update KB2748349 is available on Windows Server 2003 /2008 /2008 R2 and Windows Server 2012 is not affected by this issue.

    Check the status of the VSS writers by running the command vssadmin list writers in cmd or powershell. Look for any writers that show errors or are in a failed state. Restart the Volume Shadow Copy service and any related services. For example, if the SQL Server VSS writer is failing, restart the SQL Server service. Also check the Windows logs for the VSS related errors. Click on Filter Current Log on the right pane in Event Viewer and select VSS as the event source.

    0 comments
  2. Anonymous
    2024-12-17T02:46:43+00:00

    Thanks!

    I find some error about VSS as below:

    'VssAdmin: Unable to create a shadow copy: Either the specified volume was not found or it is not a local volume.   Command-line: 'C:\Windows\system32\vssadmin.exe Create Shadow /AutoRetry=15 /For=\?\Volume{99d963c5-e9d8-11eb-80b3-806e6f6e6963}'. '

    Is this error will cause the history file in snapshot error?

    I also find there are same question occur on Window Server 2016. And I view the VSS introuduce document, it seems it's not available on Window Server 2012 R2.

    https://answers.microsoft.com/en-us/windows/forum/windows8_1-files/shadow-copy-snapshot-file-contents-silently/06a5e25b-6607-45eb-81a1-71cfc2b0cce3?tm=1431093840771&page=1

    0 comments