Benches macOS

7

How to limit space used by Time Machine

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Many folks in these lists have asked if they can stop Time Machine using all the space on a partition, so they can put other data there too. I grew a partition to make more space and found Time Machine would not use it. This is because it initially creates a Sparse Image with a size set to what is available at the time. Even though the Sparse Image does not occupy all that space until needed, it will not grow past that maximum. In theory it should be possible to fiddle with hdiutil [http://developer.apple.com/DOCUMENTATION/Darwin/Reference/ManPages/man1/hdiuti l.1.html], but that is risky since it is not clear how finiky Time Machine is over this. It does seem to 'fail safe' - that is if anything has been tampered with, it is inclined to refuse to proceed. So try the following:

1) Create a filler file on your volume to occupy the space you do not want Time Machine to use. A (non-Sparse) disk image will do nicely. Check that only the desired Time Machine space is showing as free.

2) Connect to the volume from the machine you wish to back up via a network connection and start making a back up. Time Machine will create its sparse image, hopefully with a maximum size of the space that was available.

3) For speed, if you can connect directly to the volume, stop the backup and connect directly via USB/Firewire and complete the initial backup faster that way. (You need to select the backup disk again.)

4) Delete the filler to release the space you want to use for other things.

I haven't followed this exactly myself, but I am pretty sure it will work.

7 replies

Sign in or join Beachball Help to reply.

  1. 0

    Kenichi Watanabe

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Interesting. For (3), if you connect it directly, doesn't Time Machine save the archive as individual files in folders instead of in an image?

  2. 0

    pvonk

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes, TM uses two different ways of backing up when comparing direct connection of the backup drive vs. having that drive attached to another Mac. So you can't stop a remote backup and continue the same one using a direct connect.

    I'm not sure what kind of backup the OP first used. He mentions a sparse image (does he really mean a sparse bundle file?) which tells me he was using a network connection. In this case (and I use network connections to a Mac mini from two other Macs) the sparse bundle size is dynamic, not fixed. It is not initially set to be the size of the partition/disk. I have two disks on the mini devoted as TM backup disks for two other macs. Each has the respective sparse bundle file and the rest of the disk is free for other uses. Over time, my sparse bundle files have expanded in size.

    Perhaps I didn't understand the details of that post.

    Message was edited by: pvonk

  3. 0

    erribus

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Sorry about my loose terminology - yes I did mean a sparse bundle. Yes if the backup is created on a local disk, it uses ordinary folders. If it is first created over a network, then it creates a sparse bundle. having created the sparse bundle, you can then connect the disk directly for speeding up the initial backup or a major restore, but also connect remotely for routine incremental backups or minor restores.

    It sounds like the type of sparse bundle created may depend on circumstances. In my case I am backing up from a laptop onto a partition on my desktop machine running Leopard 10.5.2 and when I grew the partition, although the Time Machine preference pane saw the extra space, when it came to a backup I got an error message saying there was not enough space and reporting the original size. Deleting and starting over again fixed this.

    It is possible that in other circumstances a disk attached to a Time Capsule or elsewhere might get a sparse bundle with different parameters.

    Incidentally, I tried copying my old backup sparse bundle onto another drive, deleting it and letting Time Machine create a new sparse bundle on my grown partition and copying the contents from the old one into the new one. Time Machine refused to work with it, so I lost my old backups.

    What we need is a Time Machine Utility to manipulate these files, copy them, move backups from direct folders to sparse bundles etc. Ideally Apple would produce this, but I would be willing to pay a shareware fee for that.

  4. 0

    emotpix

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I found the article below very helpful in overcoming the issues that occurred after a Leopard update. I have a Lacie Ethernet Big Disk I'm using with Time Machine to back up my MacBook. This uses step by step instructions using Terminal to create a sparse bundle on the NAS and also has the steps to limit the size of the bundle so your NAS doesn't get clogged with just one Mac's backups. We use it as the family storage for media, so I'm glad I could control the size.

    http://www.readynas.com/?p=253

  5. 0

    odysseus

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    +Yes, TM uses two different ways of backing up when comparing direct connection of the backup drive vs. having that drive attached to another Mac. So you can't stop a remote backup and continue the same one using a direct connect.+

    Actually, I believe that you can. If you read that ReadyNAS article reference below, you'll see that you can use Disk Utility to restore the hard drive backup to the NAS backup.

  6. 0

    odysseus

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    There's a whole discussion of how to limit space here:

    http://discussions.apple.com/message.jspa?messageID=7227083

    This seems to work fine for me.

  7. 0

    hborders

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I posted this on the other thread, too.

    This worked for me just fine.

    http://www.macosxhints.com/article.php?story=20071108020121567