Time Machine Mac Leopard

1. Mac Os Leopard Download
2. Snow Leopard Mac Os X
3. Time Machine Mac Francais

Time Capsule using Ethernet can also access the network to share files and connect to the Internet. With Mac OS X Leopard v10.5.2 or later you can set up Time Machine to back up all the computers on the network to your Time Capsule. See 'Using Time Machine with Your Time Capsule' on page 27 for more information. Apple says that only four percent of Mac users perform regular, automated backups. It aims to change this with Time Machine, a new backup feature in OS X 10.5. In the first of a multi-part series.

This same approach worked just fine with 10.5.0, except for the little caveat that it failed when time machine needed to prune (delete) old backups to fit in new ones. Have you tested it with this to make sure it doesn't decide to erase your whole backup as it did in the past?

I've been using something very similar for a couple months now (since the 10.5.2 release) and it works like a charm. Backing up, restoring files, thinning out old backups, ..

• there is no -library option for hdiutil (according to the man page)
• the default size in in blocks, but can be specified in gigabytes using 'g'
• the -fs option should be 'HFS+J', not 'Journaled HFS+'
• the -volname option was left out, but should be 'Backup of $MACHINENAME' (see the link in the second comment)

hdiutil create -size $SIZEg -fs HFS+J -type SPARSEBUNDLE -volname 'Backup of $MACHINENAME' $MACHINENAME_$MACADDRESS.sparsebundle

As from reading the man-page for hdiutil, I think, that -library SPUD, actually meant -layout SPUD (at least this option has a SPUD parameter).

Search engines for mac os x. So the full command will be:

hdiutil create -help

Along these lines, if you already have a networked time machine backup, you can find the disk image, open it with Disk Utility, and use 'Resize Image'. I just tried this after reading this hint and it works!
This really should be an option in Time Machine to make it easier for many computers to back up to a single Time Capsule or other drive without one person hogging all the space. In fact, I wonder how time machine handles if multiple users are backing up at the same time and the network drive runs out of space?

This is a great hint, but several points need to be made. 1.) You can skip all the bit about naming sparebundles. Just try creating one directly from Time Machine. Yes, it will fail, but it will be visible on your desktop for a couple of minutes, giving you plenty of time to make a note of the name it assigns to the sparsebundle. Let it disappear, then create one manually with the same name. 2.) You manually create a sparsebundle using Disk Utility. The Help file tells you how. As part of the creation process, you will be prompted to assign a size to the sparsebundle. It is vitally important that you select a size less than that of your NAS volume's physical capacity (and it is probably a good idea to leave an ample amount headroom so that Time Machine has space to do its thing). In the same way, if you are using your NAS as a central repository to back up multiple Macs, the total size of all the sparsebundles on your NAS should not exceed the capacity of your volume. 3.) I can't help wondering if these reports of Time Machine destroying data once it has to start removing files come from people who created sparsebundles larger than the capacities of their NAS volumes. Maybe so, maybe not. In any case, I'm not sweating this because my volume is big enough that it will be several years before I confront this problem, and I figure that by that time Time Machine will have undergone a lot of evolution, so that this problem will probably be ancient history. 4.) But just to be on the safe side, and because this hookup is not officially sanctioned by Apple, as an extra precaution I keep duplicates of my sparesebundles on a separate hard disk, I can bring them up as backups if I ever need to. Nevertheless, I've been using this setup for over a month and so far haven't had any trouble at all.

Does the Leopard install DVD recognize such a backup? In other words, is it possible to restore an entire disk from it?

• I just took Disk Utility in Leopard, create a sparsebundle disk image from here, naming it according to the name of my machine and en0 MAC address.
  The thing is, like time machine, Disk Utility can't create the .sparsebundle on the remote volume directly, so create it on your desktop, and copy it manually in the finder.
• In terminal : defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1
• If you get troubles in Console saying that this is not the correct time machine backup disk, try removing the file named .xxxxxxxxxxxx in the root of your share, and test again.
• Concerned about security ? You can even crypt your DMG !!! Yes, create your sparsebundle with 128bit AES encryption, it works perfectly. The trick is to save key in your keychain, when mounting the DMG manually, then go to Keychain, and copy/paste the entry from your user keychain to the system keychain.

From now, no need to mount your smb share or anything, everything is automatic, and people having access to the share cannot see your precious private files.

the backup always failed with all the informations found in this hint and commentes, with message :
'The backup disk image could not be mounted'
and if I mount it, proving there is nothing wrong with the image, it says the same error, only after 'preparing' for a long time.

>Does the Leopard install DVD recognize such a backup? In other words, is it possible to restore an entire disk from it?
Right, I notice none of the articles address restoring a full image to the original partition.
Can one boot from the OS X install DVD to locate a bootable complete OS X image located on a network drive and restore it to the local disks' original partition?

Ive tried all the listed tips, and after copying the sparsebundle to my AFP share, TimeMachine is still unable to see any volumes.
I've used
defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1
but still nothing appears in the TimeMachine select volumes box.
*sigh*

Everything seems to work when I set this up, but the backup never completes indicating it needs more room, I made the SPARSBUNDLE disc image 1G to start and in my test attempting to backup 150mb fails, sez the disc only has 89mb available. I was under the assumption the sparbundles were self-expanding as needed.
Am I doing something wrong?

After about three days of playing with the sparsebundle and time machine, I finally got it to work. The key for me was changing the computer name in the System Preferences - Sharing to a name that did not include spaces, symbols, etc. (just numbers and letters) and keeping the name of under 8 characters
Before this, I kept getting an 'The backup disk image could not be mounted'
error.
Also, I've read that you should remove the backup from Spotlight. It helps makes things go much faster. Not sure if this is the case or not, but I did it. Go to System Preferences - Spotlight, then under the 'privacy' tab, click on the Plus sign and add the backup under devices. It's not critical (at least not for me), but it may help.
I'm still in the process of backing up, so far 13GB out of 27GB are backed up. I'm keeping my fingers crossed until its done, but at least, I'm not geting the can't mount error any more.
Good luck.
My setup - MacBook backing up to a HP Media Smart Server over a wireless g network.

So, the computer ran for about three hours and then a black screen popped up that forced me to restart the computer.
Well, it sounds like a great idea, but I haven't gotten it to work. We ended up using an old USB hard drive to backup the computer.
I might try it again at some point, but I've been looking at some third party backup programs. They seem to offer backup to a networked drive, so I might try that. However, I would really prefer to use TM, but this is too frustrating. Maybe I'm doing something wrong. Hopefully, someone will figure it out.. if you do, please let us know.

My laptop drive failed a few weeks after I added the ability to use Time Machine over the network via this tip. While I was able to retrieve the data, I'm glad I was using it as a secondary backup when trying to figure out how to restore from a network backup.
As a result of my experience I do not recommend using Time Machine over the network unless you're positive you have the means and ability to restore your data.
Notes:
If you boot from the installer, open terminal, use the write defaults command, the TM volume will NOT show up. If there is in fact a way to have it show up while booted up off the DVD (and after having run the 'write defaults' command,) I'd love to see it!
For future reference here is the path I took to restore from a network TM backup, iirc:
- installed 10.5 on an external drive, booted off that and copied the sparsebundle over, since my server doesn't support sparsebundles (yeah I could have mounted it over the network but I wanted things to be local)
- mounted the sparsebundle and cloned that to a second external drive.
- While waiting for my internal drive to be replaced, I installed a spare 2.5' internal sata drive. I'm mentioning this because I booted off the install dvd, used the Time Machine data from the second external drive to restore all my data to the internal. Then when I got the replacement drive I just swapped the drives and did a straight clone.
YES the path I took could have been more efficient, such as making use of target disk mode and partitions. For my hardware situation it worked well. I am simply trying to make the point that until Apple officially supports this, don't rely on it as a single backup solution. Just pony up for a normal hard drive or use another method. my .02.

I've updated my guide to getting Time Machine working on non-Apple network drives (including over a wireless network).

I've also included a modified version of these instructions with a small correction to make the hdiutil call work on 10.5.5 and another that deals with Computer Names that have spaces and apostrophes.

Everything's working fine for me -- but watch out for putting your computer to sleep during a Time Machine backup!

Thanks for the article and the link!

Adam

Although this article was posted some time ago, and here it is July 2009, I have a question specifically about step 3:
> Copy the sparsebundle to the network share root. Easy enough.
> Mount your network share and copy it over. I used this Terminal
> command after the MyBackup share was mounted:
> cp -r mymachine_0017f2c8426b.sparsebundle /Volumes/MyBackup/.
Given that sparse bundle disc images are actually parent folders (containing files and subfolders) that reside on the file system, as far as I'm aware, the file system to hold a sparse bundle disc image must be HFS+ so does it matter therefore does not the 'network share root' also have to be HFS+ or is it possible for it to be another file system such as NTFS, FAT32 or ext3, etc.?

The host file system does not have to be HFS+. However, the sparse bundle will appear as a folder with a ._* file next to it, where * is the name of the sparse bundle. This is the mechanism used to store Mac metadata on non-native file systems. It would probably not be a good idea to delete or move the ._* file.
When mounted, the file system contained within the sparse bundle will be HFS+.

Now it's November and I know the thread is old, but has anyone gotten this to work well in 10.6? I have searched and tried the recommendations but can't seem to get it.

Mac Os Leopard Download

cp -r smides_[macaddr].sparsebundle /Volumes/[mount]

and then everything seemed to work. I'm doing my first full backup now. I'm curious if, since I'm using SMB, if the drive will mount correctly automatically the next time Time Machine wants to do a backup. We'll see...

Probably worth mentioning that the reason it fails to create the sparsebundle on NFS (or other network mounts)
hdiutil: create failed - Inappropriate ioctl for device
which it is taking as fatal. Can probably find out which ioctl it is trying to use with dtrace, but won't fix it.
It is also worth mentioning that if you create the sparsebundle on local disk, then use 'cp -r', you are copying sparse files as non-sparse. So suddenly you will actually take up the space. you can use 'rsync -arv --sparse sparsebundle /Volumes/NFSDrive/' to copy it sparsely.

I think that you're confused about what 'sparse' means. I suspect that you believe that the files which together compose the 'sparsebundle' disk image are in-themselves 'sparse files', which is not true. HFS+ does not implement sparse files. The _disk image_ is sparse in the sense that the file system _within_ the disk image is larger than the disk image itself, that is: the file system inside the disk image is stored within the disk image in a sparse way, such that parts of the file system which are not useful are not stored in the disk image on the _physical_ disk.
JP

I have a theoretical question about all this. I have a NAS setup, and I just installed a 2nd drive there specifically for backups. I have 2 macs, a MBP & an iMac. I followed instructions for creating a sparsebundle disk image on the NAS drive for each machine to get time machine to work over the network, and got it to work. Since the drive is 1TB, I made 2 images at 450GB each, even though the 2 machines only currently need about 90GB & 150GB.
Now, based on advice elsewhere, I set up Superduper to back up to the same drive. This uses a similar process of creating a sparse image on that drive. Note that I say sparse image, not sparsebundle - I tried using the existing sparsebundles already created, but superduper didn't seem to want to do that, and in fact although sparsebundle is a choice in their menu, only sparse image would work. So I went ahead and did this but only with my MBP. It indeed created a separate sparse image, and it takes up the full amount of space necessary to back up the entire drive (90GB).
What I'm wondering is if I'm running the risk of quickly running out of room on my NAS drive, since I think TM will fairly quickly eat up as much space as you give it (450GB X 2 = 900 GB), and the superduper backup is taking up the full amount of hard drive space needed (90GB) to make a full backup (based on what I had read, I thought that somehow using superduper onto the same drive as your TM backups would mean superduper would 'piggy back' on TM's backed up files and only add the components needed to create a startup disk, and therefore not take up much space.) I was still hoping to also back up the iMac (120GB) with Superduper onto the same drive.
Thanks for any insight you may have!

Can people help me here please. I am a bit techy but not THAT techy. I have a Thecus YES box NAS (N2100). I think I have the drives formatted as EXT3 or something. I have 2x 320GB drives in a raid array so they are mirrored. I have 4 users on the NAS that correspond to the 4 users on my Macbook which is running snow leopard. I have a folder on the NAS called backups which I think only my user account has access to but once I have this working I can add everyone else's account to.
My macbook has a 160GB HDD which has about 35GB free. On the NAS of the 320GB I have 120GB free. So for starters, will TM create a 125GB image that won't fit on the NAS or will it be compressed, I assume it will be compressed otherwise I may as well just copy everything to the NAS.
Anyway, I started by reading this thread and also the thread at http://forums.mactalk.com.au/14/70801-time-machine-backup-nas.html but although I managed to run the command that allows TM so see the NAS as a valid drive, I got an error running the hdutil command and have no idea where to go now. See below.
My mac computer name is 'Stephen's MacBook' and when I ran TM after step 1 on the aussie forum a file was created called 'Stephen's MacBook.tmp.sparsebundle'.
I used the mac address of my airport card as found from system preferences network info.
The hdutil commands I ran in terminal were
hdiutil create -library SPUD -size 120g -fs Journaled HFS+ -type SPARSEBUNDLE 'backup macbook' Stephen's MacBook_xxxxxxxxxxxx.sparsebundle (mac addr removed but I didn't put the : in)
hdiutil create -size 120g -type SPARSEBUNDLE -nospotlight -volname 'nasTMBak' -fs HFS+J -verbose ~/Desktop/Stephen's MacBook_xxxxxxxxxxxx.sparsebundle -imagekey sparse-band-size=131072
and the error I got was
hdiutil: create: Only one image can be created at a time.
hdiutil: create: returning 0
Usage: hdiutil create [options]
hdiutil create -help
I don't understand what the verbose bit is, I don't understand what volname I need to use and I don't understand what the 131072 bit is.
If someone can give me a succinct explanation of what I need to do to progress to get TM to backup my macbook wirelessly to my Thecus NAS then please post reply.
Thanks all.

I found that with Snow Leopard the System UUID was necessary (on an SMB NAS). See this
http://www.insanelymac.com/forum/index.php?showtopic=184462
After I had the System UUID properly set Time Machine worked properly.

How big does the sparse bundle image need to be?
My nas has 320gb drive but only 114 free and my mac has 160 gb drive but 130 used.
I am assuming time machine compresses the backup file?

Migration Assistant copies all of your files from your old Mac to your new Mac so that you don't have to copy them manually.

• If your files are currently on a PC, follow the PC migration steps instead.
• If you're moving content from a Time Machine backup, follow the steps to restore your Mac from a backup instead.

Get ready

1. Install all available software updates on both computers. If your old Mac isn't using OS X Lion or later, and your new Mac isn't using OS X Mavericks or later, follow the Mountain Lion migration steps instead.
2. If both computers are using macOS Sierra or later, place them near each other with Wi-Fi turned on. If either one is using OS X El Capitan or earlier, make sure that both are on the same network.
3. On your old Mac, choose Apple menu  > System Preferences, then click Sharing. Make sure that a name appears in the Computer Name field.

Use Migration Assistant

You're now ready to use Migration Assistant to move your files from the old Mac to the new one.

On your new Mac

Snow Leopard Mac Os X

1. Open Migration Assistant, which is in the Utilities folder of your Applications folder. Then click Continue.
2. When asked how you want to transfer your information, select the option to transfer from a Mac, Time Machine backup, or startup disk. Then click Continue.
   

On your old Mac

1. Open Migration Assistant, then click Continue.
2. When asked how you want to transfer your information, select the option to transfer to another Mac. Then click Continue.

On your new Mac

When asked to select a Mac, Time Machine backup, or other startup disk, select the other Mac. Then click Continue.

On your old Mac

If you see a security code, make sure that it's the same code shown on your new Mac. Then click Continue.

On your new Mac

Time Machine Mac Francais

1. Select the information to transfer.
   In this example, John Appleseed is a macOS user account. If it has the same name as an account already on your new Mac, you're prompted to either rename the old account or replace the one on your new Mac. If you rename, the old account will appear as a separate user on your new Mac, with a separate home folder and login. If you replace, the old account will delete and then replace the account on your new Mac, including everything in its home folder.
2. Click Continue to start the transfer. Large transfers might need several hours to complete.
3. After Migration Assistant is done, log in to the migrated account on your new Mac to see its files.

If you're not keeping your old Mac, learn what to do before you sell, give away, or trade in your old Mac.