Stilgherrian (@stilgherrian)

Wentworth Falls NSW AU

The below is an off-site archive of all tweets posted by @stilgherrian ever

August 3rd, 2012

Mobile: Semi-loose in the Sydney CBD until 1400, when I can resume running of the data backups etc… for the next three days. Sigh.

via Janetter for Mac

As expected, generating a new Time Machine backup is estimating completion as “about a day”. Must lock in continuous accommodation first.

via Janetter for Mac

@SulphurCocky I’m dealing with 25x that amount of data, for which there’s currently no known-good backup thanks to multiple failures.

via Janetter for Mac in reply to SulphurCocky

@SulphurCocky Think it through. Look at USB transfer speeds, add overhead, double it ‘cos of verify-after-write, add Spotlight indexing.

via Janetter for Mac in reply to SulphurCocky

@SulphurCocky I have done precisely that. The times you are seeing are those for duplicating the amount of data involved.

via Janetter for Mac in reply to SulphurCocky

The question then becomes, can a fresh Time Machine backup be generated before I must unplug and move the computer. Probably not.

via Janetter for Mac

For example, after 12.5 hours we discover that duplicating the Time Machine backup drive won’t happen because there’s too many I/O errors.

via Janetter for Mac

The challenge is scheduling my accommodation and work around data-copying tasks that sometimes run for 17 to 20 hours or more.

via Janetter for Mac

Fri plan: Slabs of backup and hard drive cloning working around errors, interleaved with accommodation changes, planning and disgruntlement.

via Janetter for Mac

This is Friday, a somebody is going to pay.

via Plume for Android