I'd like a way to verify a time machine backup.

What I envision:
1. A tool to list "which files on the backup do not need to be backed up" -- in 
other words, the list of files that time machine think are worth backing up but 
can be skipped. These can then be sent to a diff-tool to verify that what is on 
the backup matches.

2. A way to let time machine know that "Hey, this file does not actually match, 
and needs to be backed up". "Delete all backups of file X" is one such, but it 
is overkill. On the other hand, if the file on the backup is in error, maybe it 
should be removed. It is also not quite sufficient, if files should be backed 
up but are missing.

#1 -- list all files that should be backed up and not need to be re-backed up 
-- is needed to avoid worrying about files that do not get backed up. The idea 
of "only scan files that are on the backup" will miss files that should have 
been but have not because of a bug in time machine itself. In theory, such a 
tool can be written today, but I have no idea how. As far as I can tell, 
backupd is the only program that has the knowledge to make such a list, but 
does not.

#2 -- force a backup of specific files -- seems to be impossible at the moment.

In the past (10.9.5), I had directories where the list of "what was backed up" 
did not match the list of "what should have been backed up". So the concern of 
"files missing" is not crazy. And the concern of "undetected IO error in the 
write" is very real.

Has anyone looked into this issue? Are there any tools, or any sort of "work in 
progress", or anything, to deal with any of this so far?

---
Entertaining minecraft videos
http://YouTube.com/keybounce

_______________________________________________
MacOSX-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-talk

Reply via email to