3 ms·
Deleting the old backup is no longer the first step AFAIK. Yes, I have seen that behaviour in the past. Now, it gets renamed and then deleted once the next back
by ioquatix 11y ago
Deleting the old backup is no longer the first step AFAIK. Yes, I have seen that behaviour in the past. Now, it gets renamed and then deleted once the next backup is completed successfully.
- rcthompson 11y agoStill, it sucks that the solution involves losing your entire backup history.
- ioquatix 11y agoYes, it's completely rubbish, I agree. I'm pretty sure the people who are working on Time Machine are aware of this problem and I'm pretty sure it stems from the unreliability of mounting disk images over a network. Quite possibly due to hardware issues (e.g. flakey AirPort/Time Capsules) or problems with HFS+ filesystem. At a guess, I'd say they had to do their best to work around these issues. There is no excuse though, especially when it comes to backup.
- wiredfool 11y agoIt still is on Mavericks, which is where my laptop is for now. (I'll check Yosemite, as my wife's laptop got the same message.) I had flakey network stuff happen last night (which only seems to happen with one of my APs), and it flipped into needing to creating a new backup. The old backup is gone, the new one has gotten to about 7%, got interrupted, and now claims that it's in use.