… Time Machine verifies backups (is that what you call deep traversal), …
No, those two things are unrelated to each other.
The traversal is of a file system on the Mac, for data that may be not yet backed up. The traversal occurs:
- without a check of consistency of the HFS Plus file system; and
- without verification of integrity of the files.
The Apple-provided routine for verification of a Time Machine backup with network attached storage is, essentially, a sequence of two things:
- a temporary copy of a fraction of the backup – of some metadata – from the NAS, to the Mac
- at the Mac, using that copy, a limited check of file sytem consistency
–
limited because
with the fraction alone, no repair can be made.
Further reading (technical)
CopyHFSMeta in open source for OS X 10.11.2.
The
OS X manual page for fsck_hfs(8).
In Ask Different:
– a comparison of NetBSD (in the Apple products) with FreeNAS (based on FreeBSD) may observe that
good use of FreeNAS can be better than what's possible with Apple's products. For example, where FreeNAS is used with ZFS and scrubbing:
- all data in a pool is examined to verify that it checksums correctly.
Perceptions
… as
@grahamperrin pointed out, Time Machine over AFP is flaky regardless of the host platform.
Those were not my words. Some other people describe AFP as flaky.
Consider this possibility:
… a drop in network connectivity …
For fun: imagine a network cable, in a dusty corner of the room where my FreeNAS stuff is kept. That cable, severed – during a backup – by an escaped rabbit with anti-Apple tendencies. I assume that the
AFP replay cache is not designed to make everything perfect after ungraceful interruptions at critical times.
There: AFP for Time Machine is neither perfect, nor flaky :)