4 ms·
Indeed, and this goes for home backups too. You never know something is there unless you test recovering it. For example: Apple's Time Machine seems like a sli
by gojomo 15y ago
Indeed, and this goes for home backups too. You never know something is there unless you test recovering it.
For example: Apple's Time Machine seems like a slick, safe way to backup your entire hard drive. And, you can use it to transfer the entire old drive to a new drive. But, if there is an I/O error reading any of the files on backup, it will simply skip that file, and the only indication of a problem is in the /var/log/system.log. It can skip the file for months... eventually reaching the point where any older backup where the file was successfully read is aged out. And even on recovery: the file was skipped, so there's no indication it's even missing. Only when an app needs it is there any indication that months of backups, and a supposed full-recovery, had silent failures.
- larrys 15y agoI had a problem with time machine that caused me to stop using it. When I switched (think it was under 10.5) from regular to filevault it stopped doing backups. I happened to pay attention to the time that it took and noticed it seemed extremely quick. I decided (as I mentioned in another reply here) to use Super Duper which makes a clone of your hard drive and is easy to verify (just boot from the cloned drive).
- chetan51 15y agoIs this the case even in the latest versions of the OS and Time Machine? I see an small app opportunity here.
- gojomo 15y agoThrough lion at least. There are a couple 3rd-party apps to address: one's called 'Time Machine Buddy' and another is 'Log Viewer for Time Machine'. Neither is super-slick (or seems to do anything more than grepping /var/log/system.log for backupd info), but they cover the basic need... once you know it's an issue, which may only happen after being bitten.