It sounds like the type of sparse bundle created may depend on circumstances. 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. If it is first created over a network, then it creates a sparse bundle. Yes if the backup is created on a local disk, it uses ordinary folders. Sorry about my loose terminology - yes I did mean a sparse bundle. I haven't followed this exactly myself, but I am pretty sure it will work. (You need to select the backup disk again.)Ĥ) Delete the filler to release the space you want to use for other things. Time Machine will create its sparse image, hopefully with a maximum size of the space that was available.ģ) 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. Check that only the desired Time Machine space is showing as free.Ģ) Connect to the volume from the machine you wish to back up via a network connection and start making a back up. A (non-Sparse) disk image will do nicely. So try the following:ġ) Create a filler file on your volume to occupy the space you do not want Time Machine to use. It does seem to 'fail safe' - that is if anything has been tampered with, it is inclined to refuse to proceed. In theory it should be possible to fiddle with hdiutil, but that is risky since it is not clear how finiky Time Machine is over this. Even though the Sparse Image does not occupy all that space until needed, it will not grow past that maximum. This is because it initially creates a Sparse Image with a size set to what is available at the time.
I grew a partition to make more space and found Time Machine would not use it. 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.
0 kommentar(er)
