Shadow copy component backup failing with error code 13

[Vin1688]

Performed a multi-stream backup and it indicated shadow copy component failed with file read failed (error code 13). Rest of the drives able to backup.

Is it possible to delete the shadow copy component in the client itself or there is a solution to rectify this issue?

Thanks.

[Nicolai]

Shadow Copy Components is a essential part of Windows, you want that included. That's why ALL_LOCAL_DRIVES also include Shadow Copy Components.

tech note - does not know if it applies. Same error code :Shadow Copy Components / System State backup fails with status code 13: file read failed (veritas.co...

Please post a screenshot of the job details in the activity monitor.

/Nicolai

[Will_Hunting]

hi,

      Please post a screenshot of the backup selection in the backup policy and job details in the activity monitor. 

     Tech note:    How to verify Windows Open File Backup operation using VSSADMIN and BPFIS before contacting Veritas ...     

Below are some tests to verify Open File Backup operation with NetBackup on Windows Server platforms prior to contacting Veritas Technical Support and confirm Microsoft VSS is working as expected.

Test  — Create, list & delete a Shadow Copy using VSSADMIN

This test verifies that Windows and the Volume Shadow Service is operating correctly.

1. First, add the storage location for a volume using vssadmin command.
   
   C:\>
   vssadmin Add ShadowStorage /For=C: /On=D: /MaxSize=900MB
    
2. Create a shadow using vssadmin command.
   
   C:\>
   vssadmin create shadow /for=C:
   vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
   (C) Copyright 2001 Microsoft Corp.
   Successfully created shadow copy for 'C:\'
   Shadow Copy ID: {c4695448-3cab-4bd5-a7ae-2af61c509dfd}
   Shadow Copy Volume Name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
    
3. List the shadow using vssadmin command.
   
   C:\>
   vssadmin list shadows
   vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
   (C) Copyright 2001 Microsoft Corp.
   
   Contents of shadow copy set ID: {d0db889e-2e79-42f0-8716-605a5c18965f}
   Contained 1 shadow copies at creation time: 5/3/2006 11:36:20 AM
   Shadow Copy ID: {7f0bc357-1915-44d7-ab4c-c2988c9d1049}
   Original Volume: (C:)\\?\Volume{33c37ee9-d389-11da-a17d-806e6f6e6963}\
   Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
   Originating Machine: client01
   Service Machine: client01
   Provider: 'Microsoft Software Shadow Copy provider 1.0'
   Type: ClientAccessible
   Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
    
4. Delete the shadow using vssadmin command.
   
   C:\>
   vssadmin delete shadows /for=C:
   
   vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
   (C) Copyright 2001 Microsoft Corp.
   
   Do you really want to delete 1 shadow copies (Y/N): [N]? y
   Successfully deleted 1 shadow copies.

Will.

[Vin1688]

I run vssadmin list shadows and it returned no query to the output or something similar.

Is it possible to disable Microsoft VSS Open File Backup operation for the client having issue? What could be the impact when come to restoration of the VM?

[Will_Hunting]

hi,

1. Check the Volume Shadow Copy service to see if it started.

2. Please post a Windows Open File Backup tab of the Client Attributes dialog box screenshot like this:

will.

[Vin1688]

Yes, it is started. Tried to disable it and rerun the backup also failed with error code 13.

If backup individual drive letters, able to backup. However, if include 'shadow copy component' and 'system state', the backup failed showing error code 104 iand eventually error code 13.

Did a reboot of the server and rerun the backup also failed.