Kommentare zu: Time Machine backups on network shares in Leopard

Von: New to Mac

New to Mac — Tue, 29 Dec 2009 07:03:22 +0000

Worked for me on snow leopard. I had to manually create the filename string. When time machine was trying and failing, it just kepy using “tmp” for the MAC portion. I also had to recreate the image once. The first time I did not choose sparse bundle form the drop down while creating it.

Von: Will

Will — Tue, 22 Dec 2009 16:55:07 +0000

Regarding last comment please visit the website for more information because this site did not post my text correctly.
Will

Von: Will

Will — Tue, 22 Dec 2009 16:53:07 +0000

Please make it clear that these directions do not work for Snow Leopard and refer people to the above noted website, http://www.insanelymac.com/forum/index.php?showtopic=184462&st=0

However to save anyone else some time the Snow-leopard solution is simple;
with the file name TimeMachine attempts to create, use the above directions to create the sparsebundle
THEN create a file entitled “com.apple.TimeMachine.MachineID.plist” with the following text with the exception of this line
139A6879-CDA9-5721-A1BE-18EF49xxxxxxx which should reflect the UUID of your computer as per System Profiler:

com.apple.backupd.HostUUID
139A6879-CDA9-5721-A1BE-18EF49xxxxxxx

That’s It. OSX 10.6 fixed again.
Good luck,
Will

Von: Ryan

Ryan — Sun, 06 Dec 2009 09:18:47 +0000

Thanks, this has worked a treat for me.

If anyone cares to know, this is using a Thecus N2200 NAS.

Von: Chris Harvan

Chris Harvan — Sat, 31 Oct 2009 16:09:06 +0000

This seems to be working on a DNS-323 with a iMacG5. THANK YOU SO MUCH!!!

Von: Michal

Michal — Sun, 04 Oct 2009 21:21:42 +0000

I’ve followed the procedure described here http://www.readynas.com/?p=253 and it works on my SL machines. Of course, I just have a network share drive, actually mounted through the Fonera 2n router. So now, my time machines run through 79Eur router on 90Eur USB disk. What a save compared to 500Eur time capsule

Von: brian

brian — Mon, 14 Sep 2009 15:29:01 +0000

Has anyone got the Snow Leopard instructions to work?
No idea where i’m going worng

Von: craig

craig — Sat, 12 Sep 2009 01:53:08 +0000

Just found this set of Snow Leopard=specific instructions - have not yet tried them, but thought you might be interested… good luck! http://www.insanelymac.com/forum/index.php?showtopic=184462

Von: craig

craig — Fri, 11 Sep 2009 23:14:42 +0000

I have the same problem in 10.6 Snow Leopard - I used the workaround in 10.5, but now get error 45 after some time creating machinename.tmp.sparsebundle. Also tried manually creating a sparsebundle without the .tmp, as I had noticed that 10.5 also initially created a .tmp then renamed, but this did not help.

Von: Dids

Dids — Tue, 08 Sep 2009 15:31:06 +0000

Also looking for a way to get this to work on Snow Leopard.

Meh, guess I’ll have to just copy the files I need then. >.<

Von: grph

grph — Mon, 07 Sep 2009 12:58:24 +0000

I have not gotten this to work in SL either. When I try to backup to a network share it creates an image named [computer name].tmp.sparsebundle instead of [computer name]_[MAC address].sparsebundle. I tried creating a disk image named [computer name].tmp.sparsebundle, but time machine simply overwrote it and gave me the good ol’ error 45.
When I tried to backup to the share containing [computer name].tmp.sparsebundle Time Machine told me it was “making backup disk available” (or something, I’m not using the English OSX). While it was doing that the [computer name].tmp.sparsebundle folder grew from 0 MB to about 600 MB, before Time Machine gave me error 45 and deleted the disk image from the share.
Meanwhile, the [computer name]_[MAC address].sparsebundle folder was left untouched.

If anyone has any hints or tips to get this to work I’d be very happy to hear them!

Von: curt

curt — Sat, 05 Sep 2009 22:49:56 +0000

Rew.AU:

I hadn’t had the time to try this with my new MBP before I upgraded, but no matter how closely I follow the steps it doesn’t work with Snow Leopard for me either. DAMN IT!

Von: Rew.AU

Rew.AU — Mon, 31 Aug 2009 09:21:10 +0000

Has anyone had their Time Machine backups to an network attached disk stop working after installing Snow Leopard ?

It appears that Snow Leopard treats sparse bundle permissions differently to Leopard and we’re in trouble again !

Von: oo

oo — Mon, 17 Aug 2009 19:51:28 +0000

After hours of trial and error I discovered that I had to unmount the SMB share and the sparse volume in finder, then suddenly time machine started to backup properly.

Gosh, Apple isn’t making life simpler, why the heck did I switch??!

Von: Seb

Seb — Sun, 16 Aug 2009 22:44:45 +0000

Thanks man !

Von: mac fan

mac fan — Fri, 01 May 2009 13:21:42 +0000

Thank you very much for posting this. It helped me to use the network drive for the purpose I bought it.

Thanks again for this brilliant post.

Von: mmsguru

mmsguru — Tue, 31 Mar 2009 03:26:20 +0000

Yeeeehaaaaw - it works!

I read through that confusing thread on the apple-forums. People were suggesting to interrupt the initial “preparing” process, copying or moving the created sparsebundle out of place etc… I tried all of those suggestions, didnt work for me (guess I made a mistake).

However, using the described method from this blog works like a charme. Thanks for sharing!

Von: Gi

Gi — Mon, 16 Mar 2009 18:39:51 +0000

A Million thanks to you! You saved me!

Von: David

David — Tue, 10 Feb 2009 21:51:02 +0000

Thank you for the hint. It help me very much!

Von: Rew.AU

Rew.AU — Thu, 20 Nov 2008 04:20:59 +0000

This thread certainly helped me get Time Machine working properly on my SMB connected external disk (connected to a XP machine), but thought I’d point out another trap that I resolved after some late night experimentation;

** This may be obvious to some smart people, but it caught me out !

Creating the initial .sparsebundle needs to take place on a file system which understands user and group ID’s properly.

I spent a bunch of time trying to figure out why Disk Utility kept failing when I was attempting to create the empty sparse bundle image across the network on my remotely connected drive.

The answer turned out to be that the NTFS formatted remote disk (attached to the Win XP machine I was talking to via SMB) was not returning the ‘right’ answers when Disk Utility was setting permissions within the bundle.

I finally figured out that I needed to create the initial sparsebundle file on my desktop, *then* move it across the network to the desired location. All made sense after thinking about it for a while, and works well.

In summary;

1/. Use Disk Manager to create a Sparse Bundle image of the desired size *on your desktop* (which, given it’s empty to start with, will be only a few dozen megabytes)

2/. Copy the resulting .sparsebundle file to the desired location on the network

3/. Enable Network Volumes in Time Machine from Terminal by running the “defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1″ command

4/. Switch on Time Machine and target the backups to the network location you copied the Sparse Bundle to in step 2

5/. Go play ball / drink coffee / get some sleep (not necessarily in that order)

Thanks again for creating this thread and all the helpful assistance. Share & enjoy!

Von: Mikael

Mikael — Wed, 19 Nov 2008 18:01:55 +0000

Remember to select right image format in Disk Utility when creating empty image for Time Machine. If you create “reade/write disk image” it will take all that volume size from your network HD - and creating it will be damn slow.

Instead select “sparse bundle disk image”. It’s 0byte file (or if not 0, it’s very small anyway) and fills up with time.

And btw, it doesn’t matter how much you have space to create an empty disk image - you can change a capacity of the disk image by this way:

From the terminal : hdiutil resize -size xx{m or g} /PATH/TO/DISKIMAGE.dmg
xx= the size you want the image to be.
Use either M for MG or G for GB

i.e. hdiutil resize -size 25g ~/Desktop/mystuff.dmg

(It’s copy’n'paste from somewhere internet…)

In terminal you get your current folder position by typing “pwd”.

There is also small handy tool to make netshares time machine accessible with just one button click: http://www.xiotios.com/itimemachine.html

Von: G

Thu, 13 Nov 2008 16:59:47 +0000

Thank you for sharing this! I wasn’t using the correct MAC address at first (as you indicated, make sure it’s the ‘en0′ MAC address), but after correcting this, it seems to be backing up to my DroboShare now.

Von: Richard

Richard — Fri, 07 Nov 2008 03:09:26 +0000

Thanks so much for sharing this solution. It appears to be working beautifully so far. (38MB of 87GB copied).

Macbook Pro -> Windows XP Desktop computer with NTFS drive over wireless.

The only problem I had is that it took me all evening to finally stumble upon this post.

Von: lucidsystems

lucidsystems — Sat, 13 Sep 2008 10:23:34 +0000

You may want to consider using LBackup.

Von: djandyh

djandyh — Fri, 12 Sep 2008 18:17:29 +0000

Lets make this easier for the not so technical as i followed the instruction with no joy, and after hours had to work it out myself.

I am connecting to an airport for the USB

1. Format the drive as fat32
2. Connect the hard drive to the airport, this creates a share folder
3. Now connect the hard drive to the laptop via the usb cable
4. Create a spars bundle in the shared folder with following settings

Save As Name: Someone’s MacBook Pro_************ where ************* is the mac address of the laptop
Volume Name: Someone’s MacBook Pro_************
Volume Size: 500Gb
Volume Format: Mac OS Extended Journaled
Encryption: None
Partitions: No Partition Map
Image Format: Spars Bundle Disk Image

5. Connect the hard drive back to the airport
6. Connect to the drive with with finder
7. Change Time Machines to point to the drive and backup and like magic this worked with no command line fudges