|
|
Be careful with Time Machine and non-Apple NAS storage...
Be careful with this setup. The disk image used for the backup may become corrupted if it is not unmounted cleanly on a third-party fileserver. (E.g., anytime the network is interrupted or the machine is put to sleep during a backup you can end up with journal data not being flushed to the disk image, which may corrupt it. I've heard that this is why Apple does not support backups to third party disks that don't support the changes to file sharing in 10.5.)
Be careful with Time Machine and non-Apple NAS storage...
This is all true, but it doesn't have anything to do with this hint. The hint merely disables the automatic initiation of Time Machine backups. The remote sparsebundle is mounted and dismounted by the OS just as it otherwise would be.
I've been using this method for a couple of months now without a problem. In fact my frequency of corruption of the sparsebundle image on the server has decreased, because I can begin backups when I know there is less chance of server interruption. And also simply because the number of backups is lower. (Do I really need 24 backups each day? Others, maybe. Me, no.)
Be careful with Time Machine and non-Apple NAS storage...
You're right that this doesn't have anything to do with the above hint (except to say that the setup described is dangerous), but you're probably not right that it works just the same. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|