Cause of Time Backup failures identified

[mattr]

A quick FYI..

I have found the that Time Backup will work for a period of time and then consistently fail. The cause of the error is file system corruption on the destination volume. To resolve the problem you unmount the destination volume and use e2fsck fixes the problems (don't forget to mount the volume again before trying Time Backup!),

[Allard]

My Time backup task always fails with an "error occurred while copying files". I have reformated the destination disk (on sata2) an even checked it with e2fsck but while there are no problems it still fails.
Thinking the problem might be on my source (RAID volume) I copied all files manually to the same disk. I also used the regular (built-in) backup function on the same files. Both worked OK so I doubt if there's an problem on the source, or could there still be.

[mattr]

I recall someone raising a similar issue. I think it was something to do with file or folder names or had links. It could also be file system error on the source volume. I think the version of rsync they use for Time Backup is heavily modified and very susceptible to errors. In general, I find the whole Time Backup application to be very unreliable.

[bartgoossens]

@mattr unreliable timemachine, even in the 3.2 version with network backup? I'm doing my backups with Network Backup now, to a second Synology NAS 1511+, but am switching to Time Backup now...

[mattr]

Yeah, I've reverted to a weekly full. I recently had a problem restoring files. TimeBackup restored files into a CIFS folder from an NFS folder that isn't part of the backup set! Even if I get a successful backup I just don't trust it at this point. I'm upgrading to 1922 now. Maybe that will be better..