TimeMachine stupidity

After my restore from TimeMachine, I am naturally

eager to start backup again. However this turns out to be not so easy. There is a problem with TimeMachine’s algorithm.

I the console log one sees: 

20-01-09 09:26:08 /System/Library/CoreServices/backupd[9542] Event store UUIDs don't match for volume: harddisk 
20-01-09 09:26:08 /System/Library/CoreServices/backupd[9542] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs| 
20-01-09 10:04:08 /System/Library/CoreServices/backupd[9542] Starting pre-backup thinning: 66.23 GB requested (including padding), 55.41 GB available

It tries to backup some 66.23 GB, where there is only 55.41 GB space. So it has to delete the oldest backup. So far so good. However when it has deleted the oldest backup and there still is no space, the whole process has to restart. And this takes a lot of time. I am now well into my second day of pruning and trying.

I guess there is room for improvement here. And why does this have to happen anyway? If things are well restored, the copy on my computer is the same as the last backup. So where do all the changes come from?


Categories: Computing
PermaLink

Page 1 of 1 pages