Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.5: Use multiple Time Machine disks for redundancy' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Use multiple Time Machine disks for redundancy
Authored by: palahala on Jun 05, '09 09:56:44AM
a condition where the fsevents log has lost track of what need to be updated-- which will be the case here--

No, that is not the case here... Time Machine knows very well what data is on each backup disk. It then asks fseventd or some related API what has changed since.

When you manually repoint the time machine to a new disk it knows for sure it has to recatalog the disk.

If you're saying that you see the "Node requires deep traversal" message each time you manually assign another disk, then something is wrong on your Mac.

You are speculating that it can do this by looking at the lastudate events UUID and seeing if this is still in the fsevents log somewhere. It's possible this is true, I don't think either of us knows.

That's not speculating, that's exactly what is described in each article I mentioned earlier (though it's not the log's UUID but the FSEventsID counter). Time Machine is not keeping track of any changes. It doesn't have to, as long as it knows the last ID it used when writing to some backup.

So, I don't see anything confirming your "actually slowly corrupt your backups".



[ Reply to This | # ]