Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.5: Use multiple Time Machine disks for redundancy' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Use multiple Time Machine disks for redundancy
Authored by: lovemymacs on Jun 04, '09 12:51:46PM

I would like to add that time machine backups are incredibly prone to corruption and when they become corrupted they can become completely unusable extremely quickly. Like in moments. If the computer gets overloaded or crashes in the middle of a wireless backup just one time that can render months of backups worthless. I do use multiple time machine backups now as just a part of my backup system. When my previous backups have become damaged the geniuses have cheerfully told me to reformat and start again. I've had two separate time capsules completely replaced. And on Apple's website the list of people who describe my exact problems is very, very long. Time capsule would be wonderful if it would only work consistently. That said - it has saved me on more than one occasion and those occasions have been well worth all of the trouble. But every night I run a superduper backup and I keep six days of those backups going in rotation. I also use emailbackup pro as well as creating copies of any particularly important data like my schedule and keeping them on multiple volumes and backup disks. I lost about $10,000 of information two years ago when my palm somehow switched to "purge" and I find any amount of trouble in backing up to be a small price. Superduper is a staggeringly useful program. Time machine seriously scares me as any kind of dependable solution. When it is there and ready, though, when it has worked, it is wonderful.



[ Reply to This | # ]
10.5: Use multiple Time Machine disks for redundancy
Authored by: hamarkus on Jun 05, '09 06:25:22AM

I too had one TC replaced by the geniuses. But as long as the TC still mounts, trying a fsck from the command line can fix a lot of errors (but it might easily take more than 24 hours to do this).



[ Reply to This | # ]