2008/04/08

Time Machine backups on SMB share

Finally I managed to perform network Time Machine backups.

Despite the fact that network Time Machine backups were advertised by Apple before Leopard launch, this functionality has been disabled just before the release. I don't want to speculate about true reasons behind this move. There are some rumors that it was because of new apple's Time Capsule product and an attempt to bind network backups of Mac OS X to this device. Could be partially, however problem seems to be technical, not economical.

Network TM backups are disabled by default, however turning this feature on is quite simple, it is enough to run in Terminal:

defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1

In my case one more required step was to create sparse image bundle for the backup named in pattern

hostname_mac address without separators

, on the destination backup share.

(Update: you might be interested in precise command for creating sparse image bundle.)

This kind of backup use to be potentially unstable - there is an apple forum post regarding this issue. The problem seems to be fixed now with the latest TimeMachine and AirPort update. Probably this bug was an original rationale behind disabling network TM backups when the Leopard was released. Are there any more obstacles for network TM backups? If not - apple, please make network volumes appear in TM's drive chooser by default. Also the need of preparing sparse image bundle in order to make a backup seems to be too difficult for many Mac OS X users. Is it made for purpose? I believe there is still some technical issue behind. The only thing that worries me is backup instability. :(

2 comments:

  1. Anonymous8/4/08 06:57

    Well, in general, backup (time machine is not exactly backup, I know) on local disc makes little sense, so network backup is a must. It could be even made on FTP (with strong data encryption before uploading files). I wonder how it will be made in http://flyback-project.org/

    ReplyDelete
  2. "Non-local disk" does not imply "network storage". It could be USB or firewire drive connected to local machine - in fact it is apple's preferred way (except Time Capsule) of using Time Machine - mainly because of the amount of data to transfer. With wireless or even 100Mb/s ethernet network it is far slower then locally connected external disk.

    Flyback seems interesting. However personally I would rather concentrate on porting ZFS to linux. ZFS has TM features on filesystem level (in fact apple has already added ZFS support in Darwin - I hope it will be the default filesystem in next releases). As Sun hired Ian Murdock I hope that one day Debian will run also OpenSolaris kernel. I wonder which comes first - Debian running on top of Solaris kernel or ZFS support on Linux? :) Meanwhile we can enjoy Ubuntu based http://www.nexenta.org/ with ZFS enabled by default.

    ReplyDelete