I'm not sure what you're doing wrong, but the Time Machine UI works fine when using unsupported network drives.
I've been running this method for about a week now without any hitches. In fact, when you backup to a non-supported drive, because of the way Time Machine relies of hard-linked directories, it will create a Mac OS sparse disk image (which supports this feature inside of it). Sure, with a sparse disk image, you'll always run the risk of if the image gets corrupt, there goes your data - but then again, there's always a risk that it'll snow at the equator too!
I've even used this method to RESTORE from a Time Machine disk on a NAS via the Leopard DVD.
All-in-all, sure, it may not be for the faint of heart, but in the week I've been running it, all my backups have completed, it has auto-mounted the network share if (at the time of the hourly backup) the share wasn't mounted (and even unmounted the share once complete).
Reader Comments (Page 1 of 1)
JR @ Nov 10th 2007 8:14AM
I'm not sure what you're doing wrong, but the Time Machine UI works fine when using unsupported network drives.
I've been running this method for about a week now without any hitches. In fact, when you backup to a non-supported drive, because of the way Time Machine relies of hard-linked directories, it will create a Mac OS sparse disk image (which supports this feature inside of it). Sure, with a sparse disk image, you'll always run the risk of if the image gets corrupt, there goes your data - but then again, there's always a risk that it'll snow at the equator too!
I've even used this method to RESTORE from a Time Machine disk on a NAS via the Leopard DVD.
All-in-all, sure, it may not be for the faint of heart, but in the week I've been running it, all my backups have completed, it has auto-mounted the network share if (at the time of the hourly backup) the share wasn't mounted (and even unmounted the share once complete).
Thumbs Up here, works fine.