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

Click here to return to the 'Fine advice, but unnecessary' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Fine advice, but unnecessary
Authored by: GaelicWizard on Nov 20, '08 01:55:33PM

The advice in this hint won't hurt anything, but it is also unneeded. I notice that several of the commenters above me have seen this issue, as have I. These issues did plague the brand-new Time Machine and Time Capsule when first released, but have been resolved.

Since around 10.5.4, and moreso with 10.5.5, Time Machine does correctly notice network changes and will unmount the volume. Also, the method by which the disk image is stored on the Time Capsule (sparse bundle), is largely immune to corruption (although nothing is perfect).

Also, several updates to the Time Capsule firmware have been released. I believe that we are on 7.3.2 now. Some of these updates did specifically list Time Machine improvements. As I mentioned above, I did have corruption issues once. I updated all my software, updated my TC firmware, and created a new sparsebundle and haven't had any trouble since.

Time Machine should, can, and does correctly disconnect from a Time Capsule when the network drops.

Of course, following this hint doesn't hurt anything either, so if you would feel safer with this method, then do it!


P.S. Judging from the NDA-violating postings of release notes from 10.5.6, the last remnants of the <del>old republic</del> Time Machine / Time Capsule bugs should be eliminated.


[ Reply to This | # ]