Aller au contenu principal

Back Failed ... but it worked if I ran it again ... failed again today.

Thread solved

I have a few backups running ... this one writes to a SSD (1GB) that is mirrored to my MS OneDrive.

Hmm ... code and spoiler don't work :( ... makes for a very long and generally boring post.

Attached is the results from VVS Doctor.

[code]

10/11/2020 3:00:00 PM: -04:00 21548 I00000000: -----
10/11/2020 3:00:00 PM: -04:00 21548 I00000000: ATI Demon started. Version: 24.6.1.25700.
10/11/2020 3:00:00 PM: -04:00 21548 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
10/11/2020 3:00:00 PM: -04:00 21548 I00640002: Operation Samsung SSD 970 PRO 512GB 1B2QEXP7 started by schedule.
10/11/2020 3:00:00 PM: -04:00 21548 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
10/11/2020 3:00:00 PM: -04:00 21548 I013C0000: Operation: Backup
10/11/2020 3:00:12 PM: -04:00 21548 E02160015: Error 0x2160015: A backup error.
| trace level: error
| line: 0xa340ffd3416335cf
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp:353
| function: da_backup::Commit
| line: 0xa340ffd3416335cf, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp:353, da_backup::Commit
| $module: disk_backup_vs_650
|
| error 0x70021: Failed to create volume snapshot.
| line: 0x8ba4fa0bac28bf6d
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\backup_partition.cpp:538
| function: `anonymous-namespace'::PartitionBackuper::Init
| line: 0x8ba4fa0bac28bf6d, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\backup_partition.cpp:538, `anonymous-namespace'::PartitionBackuper::Init
| $module: disk_backup_vs_650
|
| error 0x10c443: Failed to unlock the volume snapshot.
| line: 0x3fec04e376b8a1a2
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp:1196
| function: win_snapshot_core::SnapStart
| line: 0x3fec04e376b8a1a2, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp:1196, win_snapshot_core::SnapStart
| $module: disk_backup_vs_650
|
| error 0x10c46b: VSS writer 'SqlServerWriter' with class ID 'A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A' has failed to process the snapshot.
| line: 0x3fec04e376b89da6
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp:176
| function: `anonymous-namespace'::ObtainVSSFailReasonSuberror
| line: 0x3fec04e376b89da6, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp:176, `anonymous-namespace'::ObtainVSSFailReasonSuberror
| $module: disk_backup_vs_650
|
| error 0xfff0
| line: 0xbd28fdbd64edb8fb
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\common\error.cpp:317
| function: Common::Error::AddHResult
| line: 0xbd28fdbd64edb8fb, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\common\error.cpp:317, Common::Error::AddHResult
| code: 0x800423f4
| $module: disk_backup_vs_650
10/11/2020 3:00:13 PM: -04:00 21548 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bced8
| file: c:\bs_hudson\workspace\123\products\imager\demon\main.cpp:738
| function: main
| line: 0x9f2c53c72e8bced8, c:\bs_hudson\workspace\123\products\imager\demon\main.cpp:738, main
| $module: ti_demon_vs_25700

Start: 10/11/2020 3:00:00 PM
Stop: 10/11/2020 3:00:13 PM
Total Time: 00:00:13 [/code]

 

Fichier attaché Taille
AcronisVSSDoctorReport_2020-10-11-17-14-08.txt 10.33 Ko
0 Users found this helpful

Ran it again (from the Acronis console) and it appears to be working with no issue.  The scheduled start stopped after 13 seconds.

The VSS Doctor report did show 2 error events within the same time period of your failed backup task log.

Timestamp: 10/11/2020 3:00:11 PM
Type: Error
Source: VSS
Message: Volume Shadow Copy Service error: Unexpected error calling routine GetVolumePathName is fail on the path T:\Recorded TV, winerror 0x00000002..  hr = 0x80070002, The system cannot find the file specified. .   Operation:    OnPostSnapshot event    PostSnapshot Event  Context:    Execution Context: Shadow Copy Optimization Writer    Execution Context: Writer    Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}    Writer Name: Shadow Copy Optimization Writer    Writer Instance ID: {fdb7272c-ccdc-4c49-8229-60b758911a3e}
InstanceId: 8193
SearchLink: https://www.google.com/#newwindow=1&q=VSS+event+id+8193

Timestamp: 10/11/2020 3:00:08 PM
Type: Warning
Source: VSS
Message: A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error.  If the backup process is retried, the error is likely to reoccur. . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.   Operation:    PrepareForSnapshot Event  Context:    Execution Context: Writer    Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}    Writer Name: SqlServerWriter    Writer Instance Name: Microsoft SQL Server 2016:SQLWriter    Writer Instance ID: {dac2d6e6-8509-45be-ba0a-c9b0f94f79d6}    Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"    Process ID: 6584
InstanceId: 8229
SearchLink: https://www.google.com/#newwindow=1&q=VSS+event+id+8229

Thanks. I will follow up on those links.

Same happened again today ... scheduled task failed, manually started task completed.

I found that the Volume Shadow Copy service was NOT started. Have set it to automatic and started it. Will wait until the next scheduled backup (Tomorrow at 3pm) and see how we go.

Update: Today's 3pm scheduled backup went off without any issues.

 

Thanks to Steve for the solution :)