I could almost forgive an off-by-one sort of error in Time Machine's index of target volumes. But write it did, and with vehemence.Īllow me to rattle off the list of opportunities to smell a rat that Time Machine's developers missed: The partition was on my internal hard drive (rather defeating the purpose), it was a fraction (37.7GB) of the size of the volume I intended to back up, it was not empty, and its type was other than HFS+. Why should it be? The Boot Camp partition was formatted for NTFS, a filesystem type that OS X can only read, not write. My Boot Camp volume wasn't even on the list of potential targets. Boot Camp's gone, its partition completely cleaned out, and that partition renamed "Time Machine Backups." I selected the Time Capsule volume, plainly named "Tom Yager's Time Capsule" (the default) before starting Time Machine. It saved me the trouble of keeping a Windows notebook handy. I booted to it less often than I used it with VMware Fusion. I had an activated copy of Windows Vista Ultimate there, painstakingly outfitted with all of the incrementally released Vista updates, plus Office and Visual Studio. I did not expect that satisfying this best practice would wipe out my MacBook Pro's Boot Camp partition. One should accept such trade-offs in the interest of data protection, and I oughtn't write about what I haven't used.
BOOT CAMP BACKUP TIME MACHINE FULL
I've been leery of using Time Machine automatic backup with Time Capsule (an Airport Extreme router with a 1TB internal drive) because I knew that full backups would take for-bloody-ever over 802.11n.
0 kommentar(er)
