Forum Discussion
cpegel
15 years agoLevel 4
Yes, I'm using AOFO set to Microsoft Volume Shadow Copy Service with Snapshot Provider "System".
I had a deeper look in the related logs and found this exception:
V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes. AOFO: Started for resource: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). The following volumes are dependent on resource: "C:" . The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
So it's a problem with the shadow copies?
Edit: It came into my mind that this also might be related to a running antivirus software. I'm running Kaspersky antivirus on the server.
Edit: I added the Backup Exec binaries (beserver.exe, beagent.exe, etc.) to the exclusion list of Kaspersky, so it wont prevent files to be opened, still no success. After I did the changes I ran a full backup, successfully. Then I waited for the next full backup in the regular schedule,. and it failed.
I had a deeper look in the related logs and found this exception:
V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes. AOFO: Started for resource: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). The following volumes are dependent on resource: "C:" . The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
So it's a problem with the shadow copies?
Edit: It came into my mind that this also might be related to a running antivirus software. I'm running Kaspersky antivirus on the server.
Edit: I added the Backup Exec binaries (beserver.exe, beagent.exe, etc.) to the exclusion list of Kaspersky, so it wont prevent files to be opened, still no success. After I did the changes I ran a full backup, successfully. Then I waited for the next full backup in the regular schedule,. and it failed.
Related Content
- 12 years ago
- 10 months ago