A rough account of what I did with Emacs recently.
- December 2
- In an attempt to remedy the backup situation, I'm switching the
backup drive to a slightly beefier machine (for handwaving reasons
it needs to be a network share, not directly connected). That
means it's basically spent the last 11 hours verifying the drive,
and there's no progress bar to hint at when it might be
- December 1
- I have established a pattern of backup failure that goes like
- TimeMachine launches a backup
- Optionally, it spends many hours verifying the existing
backup. This might happen if the previous backup crapped out
- TimeMachine takes a snapshot of the drive to be backed up,
and estimates how much space it'll need on the backup
- TimeMachine discovers there's not enough free space, so it
starts pruning things from the backup drive, like the
previous failed backup.
- Time passes...
- TimeMachine starts copying files across, and things of that
nature (I will allow that TimeMachine does clever stuff
- Oh no! A spurious network event has interrupted the
connection to the backup drive! (good luck finding out what,
if anything, actually happened.)
- TimeMachine abandons the backup, leaving a .inProgress
backup occupying all that space it had cleared.
- Go back to the top.
So, the thing about this is that each time around the loop, the
probability of failure increases because there's more data to back
up (unless the machine you're backing up is entirely unused, and
even then it's still generating some level of churn on the disk
from time to time). I appear to have hit a tipping point on this
where I can't rely on the backup drive to be reliably available
for long enough to complete the backup.
I am so glad I have Arq as an offsite backup while I'm trying to
figure this mess out.
previous month | current month
Woop, 12-18 is here.