I just had a CRC error on a large file, an external hash check confirms the source and the destination file are not the same. If I run the job again however, fbackup just flags the entire job as 'OK' - which of course it isn't, as there is a bad file on the destination dir.
It might be a good idea to let fbackup flag these files in the fkc index file, and keep trying on subsequent jobs until they are backed up successfully... Otherwise people might get some nasty surprises when restoring!
CRC error, but next backup "OK"
-
Adrian (Softland)
- Posts: 1932
- Joined: Thu May 23, 2013 7:57 am
Hi,
We added your request to our Wishlist.
We added your request to our Wishlist.
Do you know you can monitor your backups remotely with Backup4all Monitor? You can read more here: https://www.backup4all.com/backup4all-monitor.html