You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

10.6.3 Resizing Sparsebundle Disk Images

Hi All,
I just updated to OSX 10.6.3 and am noticing a strange issue. First off I am using an unsupported NAS device for my Time Machine backups, however I have actually seen the box (Promise NS4600) sold at Apple Stores. Anyhow I have several Macs backing up to this NAS. Before 10.6.3 I had set a maximum size that the sparsebundle could grow to for each of the sparsebundle images. The problem is that when running time machine, it appears that if the sparsebundle is not the same size as the volume, the system automatically resizes the sparsebundle.

com.apple.backupd[1575]: Resizing backup disk image from 476.8 GB to 2743.0 GB

This is definitely not what I want. Does anyone know a workaround/fix? Is there a plist file I can edit where I can tell time machine not to resize my sparsebundle? Any ideas? Thanks.

Mac OS X (10.6.3)

Posted on Mar 31, 2010 8:42 AM

Reply
75 replies

Apr 16, 2010 9:45 PM in response to fracai

Looks like the lock trick may have worked for me...:
"Apr 17 16:38:29 antony-stubbss-macbook-pro-4 com.apple.backupd[2208]: Resizing backup disk image from 330.0 GB to 929.4 GB"

However, TimeMachine preferences does show 1TB free, but I think that it's just looking at the TimeCapsule drive, not the sparse bundle.... I'll report back to with more info...

Mounting the SparseBundle off the timecapsule, info shows ... strange:
Capacity: 354.33 GB
Available: 35.42 GB
Used: 318.91 GB on disk (318,913,728,512 bytes)

Hmm, according to the console, the max is set to 330, which I would expect to show 12 free. Perhaps it's a difference in measurement between 1024 vs 1000 for "Giga"...

I'll install the TimeMachine update which causes a new complete backup, that will show hopefully what is really happening...

Apr 19, 2010 12:19 AM in response to skerb1

Ok, it's still working today:
Apr 19 19:07:38 antony-stubbss-macbook-pro-4 com.apple.backupd[6192]: Resizing backup disk image from 100.0 GB to 929.4 GB
Monday, 19 April 2010 7:08:06 PM Pacific/Auckland
Apr 19 19:08:31 antony-stubbss-macbook-pro-4 com.apple.backupd[6192]: Could not resize backup disk image (DIHLResizeImage returned 35)
Apr 19 19:08:35 antony-stubbss-macbook-pro-4 com.apple.backupd[6192]: QUICKCHECK ONLY; FILESYSTEM CLEAN

Haven't hit the 100g limit yet...

Apr 29, 2010 12:29 PM in response to skerb1

Just reiterating that preventing backupd from updating the Info.plist file seems like the acceptable workaround. I'm running TM against a 2TB Windows share (NTFS volume shared through Vista), and since doing chmod -w didn't work from the Mac, I just changed the file permissions directly at the source, denying write permission to the user that is mounting the share.

Jun 21, 2010 9:30 AM in response to skerb1

Wow, what an insane battle this is. Would it kill Apple to add a max size parameter to the Time Machine interface? What is the big objection to limiting the size of the backup?

So, I'm backing up to an XServe running OS X Server 10.5.x, sharing off an 8TB RAID volume. If I could just limit the size of a given share on the server, this problem would go away. Anyone know of a way to accomplish this without reformatting the volume?

I've looked around and haven't found anything yet. Thanks.

Oct 19, 2010 3:49 PM in response to fracai

I've tested the whole process and am about to roll this out to several users. I created a how-to which captures everything needed to TM backup to an SMB/CIFS share hosted by Windows2K3. This works on 10.6.4 for me. Results may vary. Credit to previous responders in this list and elsewhere.
**********

How to set up Time Machine Backups to a network share:

*Set up the network share:*

Create a new share named for the user's login, giving only Domain Admins and the user access.
Log into the share from the workstation, saving password (Command+K, cifs://SHARE NAME/username)(if the Apple is bound to AD, credentials may be taken care of).

*Allow Time Machine over the network:*

sudo defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1

*Set up Destination:*

Create a disk image on an administrator's machine (steps below require Developer Tools be installed):

sudo hdiutil create -size SIZE InGIG(xG) -fs HFS+J -volname 'Time Machine Backups' -type SPARSEBUNDLE COMPUTERNAME.sparsebundle

Use a right-click and "show package contents" to browse within the sparsebundle package.

Get the UUID for the user's machine from Apple Menu > About this Mac > More Info > Hardware

Create a text file called "com.apple.TimeMachine.MachineID.plist" within the new sparsebundle package, with the following content:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>com.apple.backupd.HostUUID</key>
<string>YOURUUIDHERE</string>
</dict>
</plist>

Move the sparsebundle from where it is created (usually top level of creating user's home) to the mounted share. Do NOT create the sparsebundle on the share - this may cause permission issues.

Set the maximum size of the Time Machine sparse bundle. Give thought to the size. This will be the user's time machine quota. Make sure there is enough to get necessary info, but not so much to be an inefficient use of space. No more than 50GB is recommended (as in the example below)

hdiutil resize -size 50g COMPUTERNAME.sparsebundle

Prevent the OSX from resizing the sparsebundle to the maximum size of the target disk. MacOSX attempts to resize the disk image to the maximum available for some reason (at least in 10.6.4 and previous). To prevent this, you have to 'lock" the Info.plist and Info.bckup files. Make sure Developer Tools are installed (or at least the SetFile utility) :

SetFile -a L PATH TOSPARSEBUNDLE/Info.*

*Set up Time Machine:*
On the workstation, go to System Preference > Time Machine
Click "Select Disk"
Choose the share from the list (didn't appear? - redo "Allow Time Machine over the network" above)
Save password if asked
Click "Options"
It's suggested exclude everything except what absolutely needs to be backed up to the Exclude list. Select "Show invisible items" when selecting. See http://ryanblock.com/2008/05/good-folders-to-exclude-from-time-machine-backups/ for good rules.

Check "Show Time Machine status in the menu bar"

*Test and use:*
In the menubar, go to Time Machine > Back up now
If set up correctly, the disk image is automatically mounted and shows on the desktop when Time Machine needs it. The enclosing volume is NOT visibly mounted. In action the time machine volume mounts for the duration of the bakup and then dismounts.

Entering Time Machine does almost the same - the Time Machine volume mounts and the Time Machine UI works. However the volume does not dismount automatically. However, you (or the user) can then browse it just like any other Time Machine volume.

Oct 19, 2010 10:31 PM in response to skerb1

chflags can be used as an alternative for SetFile in case Developers Tools are not at hand

$ chflags uchg /path/to/sparsebundle/Info.*

to undo

$ chflags nouchg /path/to/sparsebundle/Info.*

I tested it with a 6GB partition and forced it until it reached its limit and TM behaves as expected: deleting old backups to make space for new files.

to verify if the file is locked or not:

$ ls -lO (uppercase 0)

"uchg" appears besides the Locked files ("-" for unlocked files)

Or if Xcode does not want to be installed, Pacifist can extract only the SetFile tool and then it can be linked to /usr/bin:

$ sudo ln -s /path/to/where setfile was extracted/SetFile /usr/bin/Setfile

$ rehash

Thanks to all the contributors, this thing was making me mad.

Message was edited by: Carmatana

Message was edited by: Carmatana

Nov 9, 2010 10:01 AM in response to Pondini

I can't seem to get this to work. I have followed the steps thoroughly as described by CBerryRMI (at least I believe I have:) but TM seems to want to create a new sparsebundle instead of using the one I created. If I create one called mymac.sparsebundle TM creates one called mymac1.sparsebundle during the initial full backup.

Message was edited by: hamah

10.6.3 Resizing Sparsebundle Disk Images

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.