Time Machine over the network fails and reports incorrect available space

Question

Time Machine over the network fails and reports incorrect available space

I use Time Machine to backup my iMac to a MacBook Pro which is running OS X server. Both are running 10.11.1; the Server version is 5.0.15. Time Machine had been running fine using a 4TB USB drive on the server. Yesterday I added a 6TB drive and switched the iMac to use it (again, over the network).

Now Time Machine fails after about 90 seconds and reports "The backup disk needs 743.84 GB for the backup but only 509.94 GB are available..." The Time Machine System Preference panel then shows "510 GB of 510 GB available" (first image), which is strange because before the failure it correctly indicated "6 TB of 6 TB available" (second image).

I have doubled checked the formatting of the 6TB drive (HFS+ Journaled, GUID Partition Map) and confirmed that the server also shows 6TB available. I have also reset Time Machine backups (http://pondini.org/TM/A4.html), rebooted both computers, shutdown and restarted the Time Machine service, and basically started everything I know of from scratch twice.

Any solutions or hints will be quite welcome!

Posted on Dec 4, 2015 7:43 PM

Reply

Answer 1

Dec 5, 2015 7:34 AM in response to ScottAinsworth

After a bit of digging, I discovered that the sparse image created by Time Machine was limited to about 500GB (475Gi to be exact). Here is abbreviated output from 'df -h' with both the network share (TMBackups6) and sparse image (disk5s2) mounted:

    $ df -h

    //xxx@xxx._smb._tcp.local/TMBackups6 5.5Ti  1.7Gi  5.5Ti ...

    /dev/disk5s2                         475Gi  427Mi  475Gi ...

Seeing this, I double checked the "Limit each backup..." setting on the server; the check box was cleared, which should mean no limits. Still, the evidence pointed to enforcement of the default 500GB limit.

At this point I started thinking about creating the sparse image manually with the limit set to a sensible value. However, I don't do this often a did not relish spending time figuring it out. Instead, I set the limit to 9999GB and now Time Machine is backing up properly. To change the limit,

Open the Server app.
Click on the Time Machine service in the left column.
Double click the backup destination on which to set the limit.
Check the Backup Limit check box.
Change the limit in the text box to be larger than the backup drive.
Click the OK button.

Here is a screen shot (cropped) showing the results of steps 4 and 5 with the check box and text box highlighted in yellow (OK button not shown):

I do not yet know if setting the limit larger than the size of the physical drive will cause problems in the future. I believe from Maverick on, Time Machine is aware of both the physical drive size and maximum size of the sparse image. So don't expect problems.

I am satisfied with this work around for now. If anyone knows the root cause and a real permanent fix, I would appreciate the info.

Reply

Answer 2

Apr 6, 2016 6:08 PM in response to ScottAinsworth

Hi Scott,

Did you get reliable backups after this change? Independently, I determined I had the same issue and solved it using the same approach. But, I'm still having trouble with this report:

I can sometimes get a successful backup if I reboot everything. And I'm finding on this workstation (10.11.4) that neither the /Volumes/Time Machine Backups nor the /Volumes/WorkStations are unmounting after the failed TimeMachine backup attempt. I have two other clients on this network, both running Yosemite, that seem to work fine. The server is also 10.11.4.

Anyway, if you didn't experience any other troubles, I'll start a new thread.

Thanks.

Reply

Answer 3

May 8, 2016 1:38 PM in response to tim.rohrer

So, I stumbled upon what I think is the real answer--changing the name of the Time Machine share. I had originally named the share "TMBackups6". Right after creation, everything worked as expected. However, after turning the Time Machine service off and on a few times, it seemed to default to a 500GB maximum. Today, I removed "TMBackups6" from the Time Machine service, changed the name to "Time Machine 6" (for no particular reason), and added "Time Machine 6" to the Time Machine service. Now, all is well again.

Go figure.

R/Scott

Reply