Skip to main content

Failed Backup Warning Error Cyber Protect Home Office

Thread needs solution

Following completion of an unattended backup the Backup tab shows that the backup failed. (failed-backup-error.gif)

However, the Activity tab shows the backup completed successfully followed by the successful completion of the diverse validation. (failed-backup-activity-log-contradiction.gif)

I tried checking the backup logs - that's a completely new post!

This appears to be a bug...

0 Users found this helpful

Nigel, the backup log for this backup task is the starting point to try to understand what has happened?

For anyone reading this please see my second post about log files:

https://forum.acronis.com/forum/acronis-cyber-protect-home-office-forum…

Hi Steve,

Thanks for the link to the latest MVP tool on my other post linked above.

The log files appear to say that no changes were found on any of my drives:

"09/08/2022 02:03:36:365 AM +01:00 29728 I00000000: Pid: 20400 type=log; level=inf; message=Volume Tracker has failed to find changes on volume 'G:'.;"

However, I have mounted the backup for volume G: and the files I would expect to have changed are showing the latest file dates correctly?

Thanks,

Nigel

Nigel, I would need to see the whole log file rather than just one message related to the Volume Tracker activity.  The Backup Worker logs normally contain a whole lot of messages for a Disk backup. The associated Demon log for the same task essentially has a brief synopsis of the backup actions (similar to the report generated by Email notifications when enabled).

Nigel, thanks for the Backup Worker and Demon logs, both of which show no errors that I can see.

One suggestion here would be to decouple Validation from the Backup task to see whether that has any involvement in the confusing status being shown in the GUI?
Personally, I only perform validation when I have a cause to want to do so and then do it separately from any of my scheduled backup tasks.

Validation does not guarantee that a backup file will result in a successful, working recovery!

What validation does do is to confirm that the backup file that was created by the backup operation has not been changed after it was written to the storage drive / location.  It does this by reading the backup TIB / TIBX file and calculating checksum values for each block of the file then comparing those checksums with values embedded within the file.  It the checksums match, then the file has not been changed since written.

What validation cannot do is to change whether any malware, virus or corruption was present in the source data for the backup operation when it was performed.  This can also include file system issues present when a backup was created but not detected or known about.

The other aspect that could be in play here is setting the Backup task to Shutdown the PC after the backup has completed, and whether this happened too quickly to allow all the task activities to have completely finished?  I have never seen any indication of such an issue and the Backup Worker log finishes around 30 seconds before the message about Shutdown being actioned in the Demon log.