|
|
10.5: Use multiple Time Machine disks for redundancy
You could answer this in part by doing this:
10.5: Use multiple Time Machine disks for redundancy
if you don't get a "Node requires traversal" message every time you swap drives then it may not be detecting the out-of-sync condition My point is: Time Machine gets the There is no "out-of-sync condition" (other than the (And yes, like I wrote: there is a huge number of megabytes copy every time I swap drives, easily noted in the logs with Time Machine Buddy, or by looking a the files that have been copied using TimeTracker.)
10.5: Use multiple Time Machine disks for redundancy
Perhaps I'm mistaken but my understanding of this is that in order to recover from a condition where the fsevents log has lost track of what need to be updated-- which will be the case here-- then a deep traversal is required to compare the current state of the main disk to the last backup on the old disk. That's in fact what the page you lined to says.
10.5: Use multiple Time Machine disks for redundancy
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 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". |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.10 seconds |
|