Time Machine SparseDisk Fails to Delete Old Files

I'm running Time Machine on the new 7.3.1 patch and have finally filled the drive. At first everything was going smoothly until I realized that Time Machine is not deleting old files to make room for new ones.
I found this out when I realized Time Machine stop backing up to it because the drive is full. Why is the sparsedisk not getting smaller or making room for newer backups?
Is it because this feature is unsupported?

ringoiphone wrote:
Thanks. Although the reset did nothing, by deleting enough old backups (a VERY slow process) I could get it to free enough space for another backup. It's not clear to me why it cannot do this automatically.
Time Machine will delete old backups, if it can. So something must be wrong. See #C4 in Time Machine - Troubleshooting.
If nothing there helps, a clue may be lurking in your logs. Use the widget in #A1 of Time Machine - Troubleshooting to display the backup messages from your logs. Locate the backup in question, then copy and post all the messages here.

Similar Messages

I had a repair done at the apple store where the replaced my hard drive and copied my other hard drive over to the new one. Everything is fine except the time machine wont reconnect to my old file and is trying create a new file but not enough space?

I had a repair done at the apple store where the replaced my hard drive and copied my other hard drive over to the new one. Everything is fine except the time machine wont reconnect to my old file and is trying create a new file but not there is not enough space for both files files? Do I need to do something to have it continue to update my old file instead of recreating a new one?

Depending on what version of OSX you're running, and how the data was transferred, you may be out of luck.
If you're running Lion, and your backups were made to a directly-connected external HD (ie, not a Time Capsule or other network location), you may be able to get Time Machine to "associate" the new disk with the old backups. See #B6 in Time Machine - Troubleshooting, especially the pink box there.
If you're running Snow Leopard, you might be able to do a full system restore of your backups to the new HD. See Time Machine - Frequently Asked Question #14 for detailed instructions. That should leave a "trail" that Time Machine can follow to "associate" the new drive with the old backups. Unfortunately, that doesn't always work, and there's no way to do it manually, as there is with Lion.

Time machine - possible to recover deleted backup files that have yet to be overwritten?

I recently had to wipe my hard drive and reinstall my OS after my MacBook Pro failed to start. I managed to restore all my files from a Time Machine backup on an external HD after installing OS Yosemite.
After my computer is up and running again, I switched on Time Machine again, which started deleting my older backup files to make room for a new backup. Before I know it, it has deleted all my backup files except for the latest one, the one which I used to restore my computer.
Then Time Machine discovered that it still would not have enough room for the new backup and stopped. So I don't think anything new has been written to my external HD yet. Given that Time Machine may not have overwritten the old backup images (fingers-crossed), is there any possibility that I could recover those? If so, how do I do it?
The old data backup is extremely important for me. Any help or advice will be greatly appreciated. Thank you very much.

I recently had to wipe my hard drive and reinstall my OS after my MacBook Pro failed to start. I managed to restore all my files from a Time Machine backup on an external HD after installing OS Yosemite.
After my computer is up and running again, I switched on Time Machine again, which started deleting my older backup files to make room for a new backup. Before I know it, it has deleted all my backup files except for the latest one, the one which I used to restore my computer.
Then Time Machine discovered that it still would not have enough room for the new backup and stopped. So I don't think anything new has been written to my external HD yet. Given that Time Machine may not have overwritten the old backup images (fingers-crossed), is there any possibility that I could recover those? If so, how do I do it?
The old data backup is extremely important for me. Any help or advice will be greatly appreciated. Thank you very much.

Time Machine - strange behavior while deleting old backups

Not sure if this is the right place, because this is actually not on Time Capsule, but on a Time Machine on an external USB drive.
In any case, I searched the web for "time machine delete old backups" and found many discussions of various aspects of this task. My objective is to clean up a partition on a the external drive that I no longer use for active TM backups, but to retain a small set of backups in case I need to go back to them. The partition now has other uses and I need the space. My main TM backup is now on a separate Time Capsule.
So again my objective is not to remove all backups, but just most of them.
It appears that the well-discussed procedure is the following:
Go into Time Machine.
Select the Macintosh HD.
Go back to one of the oldest backups.
Click on the Gear > click Delete Backup.
This procedure will remove one Backup at a time, and it seems to take 5 - 10 minutes for each backup.
Here is what I noticed that was "strange":
You could delete a selected backup using the above procedure.
For the first selected backup so deleted, there is a confirmation dialog with a warning message that it is not undoable.
After clicking OK on the warning message, the display backs up to the "Present" backup, and the administrative password is requested.
After the administrative password is entered, the backup starts but control is passed back to the user interface, and another backup can be selected to be deleted.
However, after the second backup is selected and deleted, there is no warning dialog, and no request for the administrative password. At this point the user interface is busy and nothing more can be done until the backup delete is completed. Except that the Time Machine can be exited by first pressing Escape, then Cancel on the lower left of the screen.
If the time machine is exited, there is a Delete Backups progress dialog with a progress bar for each backup so far requested. If the second backup was requested, as in the steps above, there would be two backups.
I discovered by playing around that either you had to wait within Time Machine for the deletion to complete, or alternatively exit Time Machine. While I was not sure what was going on, I kept starting one backup, then exiting Time Machine and re-entering Time Machine and requesting another delete operation. Each time after entering Time Machine, the warning/admin password sequence occurred and I was able to exit. And then immediately re-enter Time Machine and request another backup. Only by exiting and re-entering could another delete request be made.
When out of Time Machine, I thus saw the Delete Backups dialog with any number of concurrent "Delete One Backup" progress bars.
Because of the nature of the hard links used to indicate backups, I was wondering if these multiple delete operations could possibly be hung in a deadly embrace, so I decided to only do one at a time. Some further study to see if the multiple delete operations were all able to complete would be needed to know if this would be a good way to "queue up" multiple delete requests.
Bottom line: seems like kind of an odd implementation. Would be really nice if you could select many (say 30) individual backups and delete them all at once, rather than taking 5 - 10 minutes each. Again, this is because I am trying to reclaim disk space, but not delete all the backups from a Time Machine backup set that is not in active use.
Also, the method of "queuing up" backup delete requests is kind of odd, but seems to work, with the proviso that I have not yet confirmed that doing more than one at a time actually works.

Heinz-G?uenter Arnold wrote:
since the upgrade to SL it seem that Time Machine has problems to completely remove old backups completely. The "removed" backups do not show up in Time Machine anymore, but the backup folders and part of their contents can still be seen in Finder.
Hi, and welcome to the forums.
That happens occasionally, in both Leopard and Snow Leopard, sometimes after something was deleted from the Finder, but also after an abnormal shutdown or improper disconnection of the TM disk.
Run a +*Repair Disk+* on it via Disk Utility, in your Applications/Utilities folder. If it finds errors, but can't fix them all, run it again (and again) until it either fixes them all, or can't fix any more.

Time Machine help! Will my old files be deleted?

I've just purchased a drive to set up as a backup drive (and also for holding files that I don't have room for on my MacBook and I don't often access). I don't want to have to manually place all of my new files on it, but I'm afraid Time Machine will delete the files it holds that are no longer on my MacBook. Can someone please explain if it will or if not, what exactly will happen? Thanks!

RaimeL wrote:
I've just purchased a drive to set up as a backup drive (and also for holding files that I don't have room for on my MacBook and I don't often access).
Those are two completely different things.
Your best bet would be to get a larger internal HD, so you can keep all your originals on it, and use the external for backups only.
Second best would be a second external; use one for the "overflow" of stuff that won't fit on your Mac, and the other to back up the internal HD on your Mac and the "overflow" external.
Third best is to partition the external; backups in one partition, "overflow" in the other one. If you do that, when that drive fails (and they all do, sooner or later), you risk losing both copies. See #3 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum).
I don't want to have to manually place all of my new files on it
Depending on what you want to move, you may not have to do that manually:
[Moving your iTunes Music folder|http://support.apple.com/kb/HT1449]
[Moving your iPhoto library|http://support.apple.com/kb/HT1229]
[Moving iMovie footage to another drive|http://support.apple.com/kb/HT1026]
Note that you cannot use Time Machine's backed-up files normally. You can browse some types of files, but they must be restored somewhere to be used with an application.
I'm afraid Time Machine will delete the files it holds that are no longer on my MacBook.
Yes, sooner or later Time Machine will delete it's backup copies of things that are no longer on the drive(s) it's backing-up. So if you have it backing-up both the MacBook and the other data, it will only delete it's copies of things you deleted long ago.

Time Machine does not automatically delete old backups when drive is full

I back up to a 1TB external drive with TM. It will not delete old back-ups and instead tells me that the drive is full. I thought TM was supposed to manage all of this on its own.

It will, if it can. But it will never delete your last remaining backup.
See #C4 in Time Machine - Troubleshooting, probably the pink box there.
Basically, if Time Machine has to do a full or very large backup, and your Time Machine drive isn't well over twice the size of the data it's backing up, there won't be room for the last backup, plus the new one, plus some workspace.

How do I get Time Machine to delete old files?

On threads for earlier operating systems I've seen similar questions, and it seems Apple hasn't resolved the problem that although Time Machine says it will delete old files when the disc is full, it doesn't do it, even though my hard drive has only ~300 GB of files on it and my external hard drive has 1.5 T, it does nothing to delete old files automatically. This hasn't always been the case. The first few entries were deleted awhile back, freeing space, but that has stopped happening. Any suggestions? Do I have to start with a fresh external hard drive?

ringoiphone wrote:
Thanks. Although the reset did nothing, by deleting enough old backups (a VERY slow process) I could get it to free enough space for another backup. It's not clear to me why it cannot do this automatically.
Time Machine will delete old backups, if it can. So something must be wrong. See #C4 in Time Machine - Troubleshooting.
If nothing there helps, a clue may be lurking in your logs. Use the widget in #A1 of Time Machine - Troubleshooting to display the backup messages from your logs. Locate the backup in question, then copy and post all the messages here.

Does Time Machine replace changed files and delete old files?

I haven't upgraded to Leopard yet, but my son is a NEW CONVERT to the Mac; has uses Dells for years. He has a new Macbook Pro with Leopard. I use SuperDuper! with my Tiger Mini Mac.
I don't understand what Time Machine does. Does it continually update files on the target device, and if so how does it handle deleted and renamed files on the source device.
Thanks.

Time Machine takes a snapshot of the drive it is backing up every hour. If a file is new, renamed or modified since its last backup, Time Machine will make a physical copy of that file. To conserve drive space Time Machine will only make hard links back to its previously backed up files for files that exist on its source drive which remain unchanged. Hard links work in a somewhat similar fashion as aliases. If a file has been deleted Time Machine won't make a copy or hard link. You can read about how hard links work in Time Machine in this Ars Technica review.
http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/14
If a file is not on the hard drive for over an hour and is deleted before Time Machine makes its hourly backup that file will not be in any of Time Machine's backups.
Time Machine only retains the first hourly backup of the day as its daily backup. The other hourly backups get deleted in the course of the day. That means that to be retained in the daily backups a file must be on the hard drive for over a day or be physically present on the source drive for the first backup of the day.
After a month, Time Machine retains the daily backup made on the same day of the week as the initial backup as its weekly backup. If a file is on the source drive for less than a week and is not in the daily backup retained as the weekly it will end up being deleted when Time Machine thins its daily backups.
When the Time Machine volume fills up, Time Machine will start deleting its earliest backups to make room for new ones.

My 2 TB Time Capsule's memory is full because it will not automatically delete old files as it is supposed to, so it is giving me zero backup of my two computers now. How can this be fixed so my Time Capsule deletes the old data and saves the new?

My 2 TB Time Capsule’s memory is full because it will notautomatically delete old files as it is supposed to, so it is giving me zerobackup of my two computers now. How can this be fixed so my Time Capsule deletes the old data and savesthe new?
Neither my local computer consultant nor I have been ableto change any of the settings in Time Machine to correct this problem. Working with the choices in the TimeMachine, there does not appear that there is any way to change the frequency ofthe backups either, so, after a year has elapsed, the time capsule is full, andmy only choice appears to be to erase all the current data on the Time Capsuleand start over, something that I do not want to at all let alone repeat on anannual basis. My questions are:
What can be done to have my Time Capsule delete old filesas it is supposed to do, so it has memory available to allow my computers toback up?
Is this a software problem that can be fixed online or isdoes this require a mechanical fix of defective hardware?

How much data is being backed-up from each Mac? (see what's shown for Estimated size of full backup under the exclusions box in Time Machine Prefs > Options).
Is there any other data on your Time Capsule, besides the backups?
Most likely, there just isn't room. Time Machine may be trying to do a very large (or full) backup of one or both Macs, and can't. Since it won't ever delete the most recent backup, there has to be enough room for one full backup plus whatever it's trying to back up now, plus 20% (for workspace).
Also see #C4 in Time Machine - Troubleshooting for more details.

I just received my new Mac Mini and want to migrate files from my Time Machine. I assume the old OS is on Time machine and I don't want it to supersede the new Yosemite OS. Do I have to Do anything special?

I just received my new Mac Mini and want to migrate files from my Time Machine. I assume the old OS is on Time machine and I don't want it to supersede the new Yosemite OS. Do I have to Do anything special?

Using Migrations Assistant will only move the data and other things over, it will not bring over a previous version of the Os since the 2014 model can run anything earlier than Yosemite.

Time Machine backup failed - files can't be copied disk appears to be read

Error: <<<<<Time Machine could not complete the back - Files can't be copied onto backup disk because it appears to be read only.>>>>
I originally setup a Seagate GoFlex 1TB USB drive as my backup disk, wiped the drive and set it up as a MAC OS extended. Ran for a few days and then the error appeared - error above. Ran disk utility and verify disk - no issues found. The only way I found to resolve (temporarily) was to eject the drive, power off and reconnect. Eventually I decided the switch drives, swap the Seagate GoFlex 1TB with the WD Mybook 500GB (setup WD as MAC OS Extended), no issues till today, same error appeared..
Has anybody seen this problem, any ideas how to resolve the issue.

Hello,
http://pondini.org/TM/C6.html

Time Machine copy failed with error:28

Usually I just say OK when Time Machine can't complete a backup in either my computer or my wife's, and a couple of months later I get the irritating message again.
This time, it keeps returning.   I have no idea what to do:
Here's a log:
2/16/13 3:46:23.127 PM com.apple.backupd[1325]: Starting automatic backup
2/16/13 3:46:23.914 PM com.apple.backupd[1325]: Backing up to: /Volumes/FreeAgent GoFlex Drive/Backups.backupdb
2/16/13 3:46:29.390 PM AppleMobileSync[1329]: [0x10020c310] |ISyncManager|Warning| Could not retrieve ISyncClient with id com.apple.Keychain!
2/16/13 3:46:29.398 PM SyncServer[1315]: [0x7fd152c0bec0] |SyncManager|Error| sync alert tool for com.apple.Mail is invalid: can't find /System/Library/Frameworks/Message.framework/Resources/MailSync
2/16/13 3:46:29.416 PM com.apple.backupd[1325]: Using file event preflight for Macintosh HD
2/16/13 3:46:36.243 PM com.apple.backupd[1325]: Will copy (8.16 GB) from Macintosh HD
2/16/13 3:46:36.441 PM com.apple.backupd[1325]: Found 1464 files (8.16 GB) needing backup
2/16/13 3:46:36.478 PM com.apple.backupd[1325]: 11.28 GB required (including padding), 13.29 GB available
2/16/13 3:46:43.180 PM Mail[192]: open on /Users/HBrazee/Library/Mail/V2/Mailboxes/Deleted Messages.mbox/9032643A-C8BE-4195-B233-E5A6A64E535C/Data/4/9/Messages/94014.emlx : No such file or directory
2/16/13 3:47:09.883 PM mdworker[1337]: Unable to talk to lsboxd
2/16/13 3:47:09.887 PM mdworker[1335]: Unable to talk to lsboxd
2/16/13 3:47:09.892 PM mdworker[1336]: Unable to talk to lsboxd
2/16/13 3:47:09.896 PM mdworker[1334]: Unable to talk to lsboxd
2/16/13 3:47:10.000 PM kernel[0]: Sandbox: sandboxd(1343) deny mach-lookup com.apple.coresymbolicationd
2/16/13 3:47:10.414 PM sandboxd[1343]: ([1337]) mdworker(1337) deny mach-lookup com.apple.ls.boxd
2/16/13 3:47:10.460 PM sandboxd[1343]: ([1335]) mdworker(1335) deny mach-lookup com.apple.ls.boxd
2/16/13 3:47:10.525 PM sandboxd[1343]: ([1336]) mdworker(1336) deny mach-lookup com.apple.ls.boxd
2/16/13 3:47:10.625 PM sandboxd[1343]: ([1334]) mdworker(1334) deny mach-lookup com.apple.ls.boxd
2/16/13 3:49:19.630 PM mdworker[1359]: Unable to talk to lsboxd
2/16/13 3:49:19.635 PM mdworker[1360]: Unable to talk to lsboxd
2/16/13 3:49:19.711 PM sandboxd[1362]: ([1359]) mdworker(1359) deny mach-lookup com.apple.ls.boxd
2/16/13 3:49:19.716 PM sandboxd[1362]: ([1360]) mdworker(1360) deny mach-lookup com.apple.ls.boxd
2/16/13 3:49:20.000 PM kernel[0]: Sandbox: sandboxd(1362) deny mach-lookup com.apple.coresymbolicationd
2/16/13 3:49:36.358 PM com.apple.usbmuxd[27]: _SendAttachNotification (thread 0x7fff73d59180): Device 1c:ab:a7:98:32:58@fe80::1eab:a7ff:fe98:3258._apple-mobdev._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.
2/16/13 3:49:38.090 PM SyncServer[1365]: [0x7fc8f0c0bec0] |DataManager|Warning| Client com.apple.Mail sync alert tool path /System/Library/Frameworks/Message.framework/Resources/MailSync does not exist.
2/16/13 3:50:01.568 PM iTunes[203]: _NotificationSocketReadCallbackGCD (thread 0x7fff73d59180): Unexpected connection closure...
2/16/13 3:50:01.570 PM ath[254]: _NotificationSocketReadCallbackGCD (thread 0x7fff73d59180): Unexpected connection closure...
2/16/13 3:50:28.401 PM mdworker[1368]: Unable to talk to lsboxd
2/16/13 3:50:28.405 PM mdworker[1367]: Unable to talk to lsboxd
2/16/13 3:50:28.000 PM kernel[0]: Sandbox: sandboxd(1373) deny mach-lookup com.apple.coresymbolicationd
2/16/13 3:50:29.094 PM sandboxd[1373]: ([1368]) mdworker(1368) deny mach-lookup com.apple.ls.boxd
2/16/13 3:50:29.100 PM sandboxd[1373]: ([1367]) mdworker(1367) deny mach-lookup com.apple.ls.boxd
2/16/13 3:52:12.017 PM Mail[192]: open on /Users/HBrazee/Library/Mail/V2/POP-brazee.net/[email protected]/Sent Messages.mbox/9032643A-C8BE-4195-B233-E5A6A64E535C/Data/4/9/Messages/94034.emlx : No such file or directory
2/16/13 3:52:34.652 PM mdworker[1383]: Unable to talk to lsboxd
2/16/13 3:52:34.884 PM mdworker[1384]: Unable to talk to lsboxd
2/16/13 3:52:34.939 PM mdworker[1382]: Unable to talk to lsboxd
2/16/13 3:52:34.950 PM mdworker[1385]: Unable to talk to lsboxd
2/16/13 3:52:34.997 PM sandboxd[1390]: ([1383]) mdworker(1383) deny mach-lookup com.apple.ls.boxd
2/16/13 3:52:35.003 PM sandboxd[1390]: ([1384]) mdworker(1384) deny mach-lookup com.apple.ls.boxd
2/16/13 3:52:35.008 PM sandboxd[1390]: ([1382]) mdworker(1382) deny mach-lookup com.apple.ls.boxd
2/16/13 3:52:35.013 PM sandboxd[1390]: ([1385]) mdworker(1385) deny mach-lookup com.apple.ls.boxd
2/16/13 3:52:35.000 PM kernel[0]: Sandbox: sandboxd(1390) deny mach-lookup com.apple.coresymbolicationd
2/16/13 3:54:21.305 PM Dock[138]: no information back from LS about running process
2/16/13 3:54:21.309 PM lsboxd[233]: @AE relay 61657674:6f646f63
2/16/13 3:54:21.000 PM kernel[0]: Sandbox: sandboxd(1401) deny mach-lookup com.apple.coresymbolicationd
2/16/13 3:54:24.631 PM com.apple.XType.FontHelper[1406]: FontHelper: message received. (<dictionary: 0x7ffc64800c60> { count = 2, contents =
    "query" => <string: 0x7ffc64800dc0> { length = 105, contents = "com_apple_ats_name_postscript == "Arial,Bold" && kMDItemContentTypeTree != com.adobe.postscript-lwfn-font" }
    "restricted" => <bool: 0x7fff74932320>: true
2/16/13 3:54:24.632 PM com.apple.XType.FontHelper[1406]: AutoActivation: scopes (
    "/Library/Application Support/Apple/Fonts"
2/16/13 3:54:24.808 PM com.apple.XType.FontHelper[1406]: FontHelper: message received. (<dictionary: 0x7ffc64800810> { count = 2, contents =
    "query" => <string: 0x7ffc64800970> { length = 111, contents = "com_apple_ats_name_postscript == "Arial,BoldItalic" && kMDItemContentTypeTree != com.adobe.postscript-lwfn-font" }
    "restricted" => <bool: 0x7fff74932320>: true
2/16/13 3:54:24.809 PM com.apple.XType.FontHelper[1406]: AutoActivation: scopes (
    "/Library/Application Support/Apple/Fonts"
2/16/13 3:54:25.052 PM WindowServer[102]: CGXDisableUpdate: UI updates were forcibly disabled by application "Preview" for over 1.00 seconds. Server has re-enabled them.
2/16/13 3:54:25.584 PM WindowServer[102]: reenable_update_for_connection: UI updates were finally reenabled by application "Preview" after 1.53 seconds (server forcibly re-enabled them after 1.00 seconds)
2/16/13 3:54:30.628 PM sandboxd[1401]: ([192]) Mail(192) deny file-read-data /Users/HBrazee/Library/Preferences/com.apple.DownloadAssessment.plist
2/16/13 3:54:49.692 PM mdworker[1411]: Unable to talk to lsboxd
2/16/13 3:54:49.696 PM mdworker[1410]: Unable to talk to lsboxd
2/16/13 3:54:49.818 PM sandboxd[1416]: ([1411]) mdworker(1411) deny mach-lookup com.apple.ls.boxd
2/16/13 3:54:49.823 PM sandboxd[1416]: ([1410]) mdworker(1410) deny mach-lookup com.apple.ls.boxd
2/16/13 3:54:50.000 PM kernel[0]: Sandbox: sandboxd(1416) deny mach-lookup com.apple.coresymbolicationd
2/16/13 3:55:11.964 PM WindowServer[102]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
2/16/13 3:55:11.986 PM Mail[192]: open on /Users/HBrazee/Library/Mail/V2/POP-brazee.net/[email protected]/Deleted Messages.mbox/9032643A-C8BE-4195-B233-E5A6A64E535C/Data/4/9/Messages/94057.emlx : No such file or directory
2/16/13 3:57:17.000 PM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=1438[GoogleSoftwareUp] clearing CS_VALID
2/16/13 3:57:19.177 PM GoogleSoftwareUpdateDaemon[1440]: -[KeystoneDaemon logServiceState] GoogleSoftwareUpdate daemon (1.1.0.3659) vending:
    com.google.Keystone.Daemon.UpdateEngine: 2 connection(s)
    com.google.Keystone.Daemon.Administration: 0 connection(s)
2/16/13 3:57:19.332 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateEngine updateProductID:] KSUpdateEngine updating product ID: "com.google.Keystone"
2/16/13 3:57:19.445 PM GoogleSoftwareUpdateDaemon[1440]: -[KSCheckAction performAction] KSCheckAction checking 1 ticket(s).
2/16/13 3:57:19.554 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction starting update check for ticket(s): {(
    <KSTicket:0x585250
        productID=com.google.Keystone
        version=1.1.0.3659
        xc=<KSPathExistenceChecker:0x582eb0 path=/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/>
        serverType=Omaha
        url=https://tools.google.com/service/update2
        creationDate=2010-06-26 00:04:18
    >
Using server: <KSOmahaServer:0x292b10
    engine=<KSDaemonUpdateEngine:0x287110>
    params={
        EngineVersion = "1.1.0.3659";
        ActivesInfo = {
            "com.Google.GoogleEarthPlus.intel" = {
                LastRollCallPingDate = 2013-02-16 08:00:38 +0000;
            "com.google.Chrome" = {
                LastRollCallPingDate = 2013-02-16 08:00:38 +0000;
                LastActiveDate = 2012-11-25 19:27:11 +0000;
                LastActivePingDate = 2012-11-26 08:00:15 +0000;
            "com.google.Keystone" = {
                LastRollCallPingDate = 2013-02-16 08:00:39 +0000;
                LastActivePingDate = 2013-02-16 08:00:39 +0000;
                LastActiveDate = 2013-02-16 22:57:18 +0000;
            "com.google.musicmanager" = {
                LastActivePingDate = 2012-07-29 06:59:48 +0000;
                LastActiveDate = 2012-07-28 19:04:42 +0000;
                LastRollCallPingDate = 2013-02-16 08:00:38 +0000;
        UserInitiated = 0;
        IsSystem = 1;
        OmahaOSVersion = "10.8.2_i486";
        Identity = KeystoneDaemon;
        AllowedSubdomains = (
            ".omaha.sandbox.google.com",
            ".tools.google.com",
            ".www.google.com",
            ".corp.google.com"
>
2/16/13 3:57:19.867 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction running KSServerUpdateRequest: <KSOmahaServerUpdateRequest:0x2973e0
    server=<KSOmahaServer:0x292b10>
    url="https://tools.google.com/service/update2"
    runningFetchers=0
    tickets=1
    activeTickets=0
    rollCallTickets=0
    body=
        <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
        <o:gupdate xmlns:o="http://www.google.com/update2/request" protocol="2.0" version="KeystoneDaemon-1.1.0.3659" ismachine="1">
            <o:os platform="mac" version="MacOSX" sp="10.8.2_i486"></o:os>
            <o:app appid="com.google.Keystone" version="1.1.0.3659" lang="en-us" installage="966" brand="GGLG">
                <o:updatecheck></o:updatecheck>
            </o:app>
        </o:gupdate>
>
2/16/13 3:57:29.555 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateCheckAction(KSServerUpdateRequestDelegate) serverRequest:fetchedWithResponse:] KSUpdateCheckAction received KSServerUpdateResponse: <KSOmahaServerUpdateResponse:0x298e70
    server=<KSOmahaServer:0x292b10>
    url="https://tools.google.com/service/update2"
    status=200
    tickets=1
    activeTickets=0
    rollCallTickets=0
    data=
        <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
        <gupdate xmlns="http://www.google.com/update2/response" protocol="2.0" server="prod">
            <daystart elapsed_seconds="53810"></daystart>
            <app appid="com.google.Keystone" status="ok">
                <updatecheck status="noupdate"></updatecheck>
            </app>
        </gupdate>
>
2/16/13 3:57:29.864 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateCheckAction(PrivateMethods) finishAction] KSUpdateCheckAction found updates: {( )}
2/16/13 3:57:29.934 PM GoogleSoftwareUpdateDaemon[1440]: -[KSPrefetchAction performAction] KSPrefetchAction no updates to prefetch.
2/16/13 3:57:29.937 PM GoogleSoftwareUpdateDaemon[1440]: -[KSMultiUpdateAction performAction] KSSilentUpdateAction had no updates to apply.
2/16/13 3:57:29.938 PM GoogleSoftwareUpdateDaemon[1440]: -[KSMultiUpdateAction performAction] KSPromptAction had no updates to apply.
2/16/13 3:57:29.942 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateEngine(PrivateMethods) updateFinish] KSUpdateEngine update processing complete.
2/16/13 3:57:30.431 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateEngine updateAllProducts] KSUpdateEngine updating all installed products.
2/16/13 3:57:30.434 PM GoogleSoftwareUpdateDaemon[1440]: -[KSCheckAction performAction] KSCheckAction checking 2 ticket(s).
2/16/13 3:57:30.476 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction starting update check for ticket(s): {(
    <KSTicket:0x28ec80
        productID=com.google.Chrome
        version=24.0.1312.57
        xc=<KSPathExistenceChecker:0x29adc0 path=/Applications/Google Chrome.app>
        serverType=Omaha
        url=https://tools.google.com/service/update2
        creationDate=2010-06-18 13:11:31
        tagPath=/Applications/Google Chrome.app/Contents/Info.plist
        tagKey=KSChannelID
        brandPath=/Library/Google/Google Chrome Brand.plist
        brandKey=KSBrandID
        versionPath=/Applications/Google Chrome.app/Contents/Info.plist
        versionKey=KSVersion
    >,
    <KSTicket:0x29fe80
        productID=com.google.Keystone
        version=1.1.0.3659
        xc=<KSPathExistenceChecker:0x2977f0 path=/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/>
        serverType=Omaha
        url=https://tools.google.com/service/update2
        creationDate=2010-06-26 00:04:18
    >
Using server: <KSOmahaServer:0x595c80
    engine=<KSDaemonUpdateEngine:0x287110>
    params={
        EngineVersion = "1.1.0.3659";
        ActivesInfo = {
            "com.Google.GoogleEarthPlus.intel" = {
                LastRollCallPingDate = 2013-02-16 08:00:38 +0000;
            "com.google.Chrome" = {
                LastRollCallPingDate = 2013-02-16 08:00:38 +0000;
                LastActiveDate = 2012-11-25 19:27:11 +0000;
                LastActivePingDate = 2012-11-26 08:00:15 +0000;
            "com.google.Keystone" = {
                LastRollCallPingDate = 2013-02-16 08:00:39 +0000;
                LastActivePingDate = 2013-02-16 08:00:39 +0000;
                LastActiveDate = 2013-02-16 22:57:18 +0000;
            "com.google.musicmanager" = {
                LastActivePingDate = 2012-07-29 06:59:48 +0000;
                LastActiveDate = 2012-07-28 19:04:42 +0000;
                LastRollCallPingDate = 2013-02-16 08:00:38 +0000;
        UserInitiated = 0;
        IsSystem = 1;
        OmahaOSVersion = "10.8.2_i486";
        Identity = KeystoneDaemon;
        AllowedSubdomains = (
            ".omaha.sandbox.google.com",
            ".tools.google.com",
            ".www.google.com",
            ".corp.google.com"
>
2/16/13 3:57:30.577 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction running KSServerUpdateRequest: <KSOmahaServerUpdateRequest:0x290140
    server=<KSOmahaServer:0x595c80>
    url="https://tools.google.com/service/update2"
    runningFetchers=0
    tickets=2
    activeTickets=0
    rollCallTickets=0
    body=
        <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
        <o:gupdate xmlns:o="http://www.google.com/update2/request" protocol="2.0" version="KeystoneDaemon-1.1.0.3659" ismachine="1">
            <o:os platform="mac" version="MacOSX" sp="10.8.2_i486"></o:os>
            <o:app appid="com.google.Chrome" version="24.0.1312.57" lang="en-us" installage="974" brand="GGRM">
                <o:updatecheck></o:updatecheck>
            </o:app>
            <o:app appid="com.google.Keystone" version="1.1.0.3659" lang="en-us" installage="966" brand="GGLG">
                <o:updatecheck></o:updatecheck>
            </o:app>
        </o:gupdate>
>
2/16/13 3:57:31.427 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateCheckAction(KSServerUpdateRequestDelegate) serverRequest:fetchedWithResponse:] KSUpdateCheckAction received KSServerUpdateResponse: <KSOmahaServerUpdateResponse:0x29a970
    server=<KSOmahaServer:0x595c80>
    url="https://tools.google.com/service/update2"
    status=200
    tickets=2
    activeTickets=0
    rollCallTickets=0
    data=
        <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
        <gupdate xmlns="http://www.google.com/update2/response" protocol="2.0" server="prod">
            <daystart elapsed_seconds="53812"></daystart>
            <app appid="com.google.Chrome" status="ok">
                <updatecheck status="noupdate"></updatecheck>
            </app>
            <app appid="com.google.Keystone" status="ok">
                <updatecheck status="noupdate"></updatecheck>
            </app>
        </gupdate>
>
2/16/13 3:57:31.430 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateCheckAction(PrivateMethods) finishAction] KSUpdateCheckAction found updates: {( )}
2/16/13 3:57:31.479 PM GoogleSoftwareUpdateDaemon[1440]: -[KSPrefetchAction performAction] KSPrefetchAction no updates to prefetch.
2/16/13 3:57:31.480 PM GoogleSoftwareUpdateDaemon[1440]: -[KSMultiUpdateAction performAction] KSSilentUpdateAction had no updates to apply.
2/16/13 3:57:31.482 PM GoogleSoftwareUpdateDaemon[1440]: -[KSMultiUpdateAction performAction] KSPromptAction had no updates to apply.
2/16/13 3:57:31.487 PM GoogleSoftwareUpdateDaemon[1440]: -[KSUpdateEngine(PrivateMethods) updateFinish] KSUpdateEngine update processing complete.
2/16/13 3:57:33.732 PM GoogleSoftwareUpdateDaemon[1440]: -[KeystoneDaemon logServiceState] GoogleSoftwareUpdate daemon (1.1.0.3659) vending:
    com.google.Keystone.Daemon.UpdateEngine: 1 connection(s)
    com.google.Keystone.Daemon.Administration: 0 connection(s)
2/16/13 3:57:49.201 PM GoogleSoftwareUpdateDaemon[1440]: -[KeystoneDaemon main] GoogleSoftwareUpdateDaemon inactive, shutdown.
2/16/13 3:58:22.082 PM mdworker[1575]: Unable to talk to lsboxd
2/16/13 3:58:22.088 PM mdworker[1576]: Unable to talk to lsboxd
2/16/13 3:58:24.000 PM kernel[0]: Sandbox: sandboxd(1580) deny mach-lookup com.apple.coresymbolicationd
2/16/13 3:58:25.365 PM sandboxd[1580]: ([1575]) mdworker(1575) deny mach-lookup com.apple.ls.boxd
2/16/13 3:58:25.469 PM sandboxd[1580]: ([1576]) mdworker(1576) deny mach-lookup com.apple.ls.boxd
2/16/13 3:59:36.358 PM mdworker[1587]: Unable to talk to lsboxd
2/16/13 3:59:36.362 PM mdworker[1586]: Unable to talk to lsboxd
2/16/13 3:59:36.503 PM sandboxd[1588]: ([1587]) mdworker(1587) deny mach-lookup com.apple.ls.boxd
2/16/13 3:59:36.508 PM sandboxd[1588]: ([1586]) mdworker(1586) deny mach-lookup com.apple.ls.boxd
2/16/13 3:59:36.000 PM kernel[0]: Sandbox: sandboxd(1588) deny mach-lookup com.apple.coresymbolicationd
2/16/13 4:00:08.980 PM firefox[1592]: invalid drawable
2/16/13 4:00:10.701 PM WindowServer[102]: CGXDisableUpdate: UI updates were forcibly disabled by application "Firefox" for over 1.00 seconds. Server has re-enabled them.
2/16/13 4:00:10.813 PM WindowServer[102]: reenable_update_for_connection: UI updates were finally reenabled by application "Firefox" after 1.11 seconds (server forcibly re-enabled them after 1.00 seconds)
2/16/13 4:00:24.543 PM com.apple.usbmuxd[27]: _SendAttachNotification (thread 0x7fff73d59180): Device 1c:ab:a7:98:32:58@fe80::1eab:a7ff:fe98:3258._apple-mobdev._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.
2/16/13 4:00:26.787 PM SyncServer[1604]: [0x7f9f7ac0bec0] |DataManager|Warning| Client com.apple.Mail sync alert tool path /System/Library/Frameworks/Message.framework/Resources/MailSync does not exist.
2/16/13 4:00:30.376 PM mdworker[1594]: Unable to talk to lsboxd
2/16/13 4:00:30.379 PM mdworker[1595]: Unable to talk to lsboxd
2/16/13 4:00:30.468 PM sandboxd[1606]: ([1594]) mdworker(1594) deny mach-lookup com.apple.ls.boxd
2/16/13 4:00:30.481 PM sandboxd[1606]: ([1595]) mdworker(1595) deny mach-lookup com.apple.ls.boxd
2/16/13 4:00:30.000 PM kernel[0]: Sandbox: sandboxd(1606) deny mach-lookup com.apple.coresymbolicationd
2/16/13 4:00:43.702 PM iTunes[203]: _NotificationSocketReadCallbackGCD (thread 0x7fff73d59180): Unexpected connection closure...
2/16/13 4:00:43.705 PM ath[254]: _NotificationSocketReadCallbackGCD (thread 0x7fff73d59180): Unexpected connection closure...
2/16/13 4:01:42.495 PM mdworker[1611]: Unable to talk to lsboxd
2/16/13 4:01:42.499 PM mdworker[1612]: Unable to talk to lsboxd
2/16/13 4:01:42.599 PM sandboxd[1613]: ([1611]) mdworker(1611) deny mach-lookup com.apple.ls.boxd
2/16/13 4:01:42.608 PM sandboxd[1613]: ([1612]) mdworker(1612) deny mach-lookup com.apple.ls.boxd
2/16/13 4:01:42.000 PM kernel[0]: Sandbox: sandboxd(1613) deny mach-lookup com.apple.coresymbolicationd
2/16/13 4:02:01.167 PM WindowServer[102]: CGXSetWindowProperty: Invalid window 0x131
2/16/13 4:02:01.167 PM WindowServer[102]: kCGErrorIllegalArgument: _CGXAddWindowToWindowOrderingGroup: error setting window property
2/16/13 4:02:29.971 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_LOWDISK (4)
2/16/13 4:02:29.972 PM KernelEventAgent[45]: tid 00000000 type 'hfs', mounted on '/Volumes/FreeAgent GoFlex Drive', from '/dev/disk1s3', low disk
2/16/13 4:02:29.000 PM kernel[0]: HFS: Low Disk: Vol: FreeAgent GoFlex Drive freeblks: 38399, warninglimit: 38400
2/16/13 4:02:55.923 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_LOWDISK, VQ_VERYLOWDISK (516)
2/16/13 4:02:55.000 PM kernel[0]: HFS: Vol: FreeAgent GoFlex Drive Very Low Disk: freeblks: 25599, dangerlimit: 25600
2/16/13 4:02:55.926 PM KernelEventAgent[45]: tid 00000000 type 'hfs', mounted on '/Volumes/FreeAgent GoFlex Drive', from '/dev/disk1s3', low disk, very low disk
2/16/13 4:02:55.929 PM mds[39]: (Warning) Volume: Indexing reset and suspended on backup volume "/Volumes/FreeAgent GoFlex Drive" because it is low on disk space.
2/16/13 4:03:40.000 PM kernel[0]: memorystatus_thread: idle exiting pid 1474 [cfprefsd]
2/16/13 4:03:43.211 PM com.apple.launchd[1]: (com.apple.XType.FontHelper[1406]) Exited: Killed: 9
2/16/13 4:03:43.000 PM kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
2/16/13 4:03:43.000 PM kernel[0]: macx_swapon SUCCESS
2/16/13 4:03:43.000 PM kernel[0]: memorystatus_thread: idle exiting pid 1406 [XType.FontHelper]
2/16/13 4:03:52.000 PM kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
2/16/13 4:03:52.000 PM kernel[0]: macx_swapon SUCCESS
2/16/13 4:03:52.849 PM com.apple.launchd[1]: (com.apple.iCloudHelper[1218]) Exited: Killed: 9
2/16/13 4:03:52.000 PM kernel[0]: memorystatus_thread: idle exiting pid 1218 [com.apple.iCloud]
2/16/13 4:03:53.571 PM mdworker[1619]: Unable to talk to lsboxd
2/16/13 4:03:53.000 PM kernel[0]: Sandbox: sandboxd(1627) deny mach-lookup com.apple.coresymbolicationd
2/16/13 4:03:53.585 PM mdworker[1622]: Unable to talk to lsboxd
2/16/13 4:03:53.672 PM sandboxd[1627]: ([1619]) mdworker(1619) deny mach-lookup com.apple.ls.boxd
2/16/13 4:03:53.677 PM sandboxd[1627]: ([1622]) mdworker(1622) deny mach-lookup com.apple.ls.boxd
2/16/13 4:03:53.690 PM mdworker[1621]: Unable to talk to lsboxd
2/16/13 4:03:53.692 PM mdworker[1620]: Unable to talk to lsboxd
2/16/13 4:03:53.711 PM sandboxd[1627]: ([1621]) mdworker(1621) deny mach-lookup com.apple.ls.boxd
2/16/13 4:03:53.786 PM sandboxd[1627]: ([1620]) mdworker(1620) deny mach-lookup com.apple.ls.boxd
2/16/13 4:04:05.629 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_LOWDISK (4)
2/16/13 4:04:05.629 PM KernelEventAgent[45]: tid 00000000 type 'hfs', mounted on '/Volumes/FreeAgent GoFlex Drive', from '/dev/disk1s3', low disk
2/16/13 4:04:21.928 PM com.apple.backupd[1325]: Stopping backup.
2/16/13 4:04:21.954 PM com.apple.backupd[1325]: Error: (-34) SrcErr:NO Copying /Users/HBrazee/Documents/Virtual Machines.localized/Microsoft Windows XP.vmwarevm/winxp-s003.vmdk to /Volumes/FreeAgent GoFlex Drive/Backups.backupdb/Howard Brazee’s Computer/2013-02-15-184254.inProgress/07592BCC-A3D7-4879-B08D-C01FDDF1895A/Maci ntosh HD/Users/HBrazee/Documents/Virtual Machines.localized/Microsoft Windows XP.vmwarevm
2/16/13 4:05:16.286 PM com.apple.backupd[1325]: Copied 14628 files (14.03 GB) from volume Macintosh HD.
2/16/13 4:05:16.286 PM com.apple.backupd[1325]: Copy stage failed with error:28

>>> Enter Time Machine and manually delete unnecessary backups to make
>>> sufficient room for new ones.
>>
>>
>> I haven't figured out how to do this.   Where is this setting?
>
> I have not figured this out either. But there is a command line
> program tmutil (time machine utility) that can delete backups, and
> also do much more. I am not an expert in this area, so I can only
> suggest that you open a Terminal.app and type
>     man tmutil
>
> Be careful Howard. If Time Machine is not able to delete old backup
> jobs, something is wrong with your backup disk.
If I recall correctly you do this by going on to TM and using one of the
pull down menus in the top apple menu strip ....
I myself am having problems with TM. I erased the external target disk and
started TM again. However it stops wverytime and refuses to backup ..
Telling me there isn't enough room even though the ext space is much
bigger. It also quotes the size of my HD content about 20% bigger than
finder says weird.
Howard (another one...)
============
1. Enter the time Machine
2. Scroll back it time for a few generations
3. Select the folder(s) to delete
4. Under the "Action" item (or gear icon), select the delete option you
want.
=================
> The last couple of days my Time Machine has run out of space during
> backups (error 28).
Just to be certain, is that really "28" or is it "-28"? (I assume it is
a positive error number, as error -28 is
> In the past, when I've seen this, I just say OK, and the problem goes away
> by itself, as it clears up space.
>
> My FreeAgent GoFlex Drive is 1 TB, while my Mac drive is 500.11 GB.
>
> I tried using Disk Utility to fix permissions, but those buttons were
> greyed out.   Disk Utility did not find any problem with the disk.
Repair Permissions is not relevant for Time Machine backups. It only
repairs permissions on files installed by the OS X Installer application
(or the OS installation or preinstalled OS, or Software Update). TM
backups don't qualify.
In any case, Time Machine deletes old backups using root privileges so
it doesn't care about permissions on the backup drive.
> Time Machie preferences show 13.3 GB of 1 TB available.
>
> I haven't been adding stuff to my computer lately more than getting
> mail.
>
> Oldest backup: December 29, 2012
> Latest backup: February 15, 2013
>
> Excluded from backups is the backup drive, my downloads folder, and my
> Mobile Documents folder.
>
> Estimated size of full backup 397.5 GB
Something odd is happening here. Given your described usage, you should
not be chewing through 1 TB of backups in less than three months. I've
gone more than a year on a drive with a similar ratio and not filled it
(and I am backing up my downloads, sometimes two or three times as I
move them to other folders).
Has anything major been done to the computer within that timeframe, e.g.
installing a new hard drive, or erasing the main drive and restoring
from backup? If so, that drive is treated as a new one and would require
another full backup, leaving the old one there.
A similar possibility is if Time Machine thought the computer had been
replaced, which would result in a new backup being started, and would
also leave the old backup unable to be deleted automatically.
In this case, you wouldn't be able to directly access the backups prior
to the change using "Enter Time Machine", but could get to them by
holding down the Option key and choosing "Browse Other Backup Disks"
from the Time Machine menu.
> What suggestions do you have for me to resolve this issue.
Which OS X version are you running?
Have a look in system.log (using Console) to see if Time Machine logged
any relevant information when the backup failed. Look for references to
"backupd" (which is the background software which does Time Machine
backups).
=============

Time machine sometimes fails with no space left

Hi,
I'm beginning to notice that sometimes Time Machine is failing to backup saying there is no space left on the Time Machine backup disk. I'm using OS X 10.9.4 .
My understanding is that when there is not enough space left, Time Machine will automatically delete older backups to make space? Sometimes this happens, sometimes not.
For example:
Aug 10 18:39:49 Barney.local com.apple.backupd[9571]: Starting automatic backup
Aug 10 18:39:50 Barney.local com.apple.backupd[9571]: Backing up to /dev/disk6s2: /Volumes/TimeMachine/Backups.backupdb
Aug 10 18:40:04 Barney.local com.apple.backupd[9571]: Will copy (1 MB) from Macintosh HD
Aug 10 18:40:04 Barney.local com.apple.backupd[9571]: Will copy (Zero KB) from HD5
Aug 10 18:40:04 Barney.local com.apple.backupd[9571]: Will copy (Zero KB) from HD2
Aug 10 18:40:04 Barney.local com.apple.backupd[9571]: Found 64 files (1 MB) needing backup
Aug 10 18:40:04 Barney.local com.apple.backupd[9571]: 1.74 GB required (including padding), 7.41 GB available
Aug 10 18:40:26 Barney.local com.apple.backupd[9571]: Copied 70 items (1 MB) from volume Macintosh HD. Linked 709.
Aug 10 18:40:33 Barney.local com.apple.backupd[9571]: Copied 1 items (Zero KB) from volume HD5. Linked 2.
Aug 10 18:57:34 Barney.local backupd[9571]: Metadata.framework [Error]: server port invalidated for uid 0
Aug 10 19:01:02 Barney.local com.apple.backupd[9571]: Stopping backup.
Aug 10 19:01:02 Barney.local com.apple.backupd[9571]: Error: (-34) SrcErr:NO Copying /Volumes/HD2/Users/gj/Documents/2013.partial.mbox/mbox to /Volumes/TimeMachine/Backups.backupdb/Barney/2014-08-10-184001.inProgress/38868 CAA-6167-40B8-8F15-BF798FADF283/HD2/Users/gj/Documents/2013.partial.mbox
Aug 10 19:01:03 Barney.local com.apple.backupd[9571]: Copied 9 items (16.82 GB) from volume HD2. Linked 21.
Aug 10 19:01:03 Barney.local backupd[9571]: Metadata.framework [Error]: MDBackupCancel failed:-1 (4) (os/kern) invalid argument
Aug 10 19:01:03 Barney.local com.apple.backupd[9571]: Copy stage failed with error:28
Aug 10 19:01:04 Barney.local com.apple.backupd[9571]: Backup failed with error 28: 28
What I'm interpreting here is that initially TM says there isn't anything to copy from HD2, but then spends about 3.5 minutes copying a very large file from HD2 and then files due to being out of space.
Why did TM not realise this file existed in the first place?
Thanks for any help.
Steve

About TM "Backup Drive is Full"
Alert TM only deletes older files if they have been deleted from the source and when TM needs space on the backup drive for a new incremental backup. Time Machine "thins" it's backups; hourly backups over 24 hours old, except the first of the day; those "daily" backups over 30 days old, except the first of the week. The weeklies are kept as long as there's room.
So, how long a backup file remains depends on how long it was on your Mac before being deleted, assuming you do at least one backup per day. If it was there for at least 24 hours, it will be kept for at least a month. If it was there for at least a week, it will be kept as long as there's room.
Note, that on a Time Capsule the sparsebundle grows in size as needed, but doesn't shrink. Thus, from the user's view of the TC it appears that no space has been freed, although there may be space in the sparsebundle.
Once TM has found it cannot free up enough space for a new backup it reports the disk is full. You can either erase the backup drive and start your backups anew or replace the drive with a larger drive.

HT3275 Time Capsule can no longer delete oldest files

My Time Machine/Capsule always used to delete the oldest files to make room when the Capsule needed more space. Recently it has stopped doing this and only gives me the options to 'change to a larger drive' or 'delete some file to make room'.
Could the problem be because I've recently upgraded my OS from 10.5.8 to 10.6.8?
Please advise me what I can do.

Yes, when you update the OS it cannot auto delete old files.. Good to see you are updating from 4th to 3rd last OS version.. I think some people consider the latest greatest OS to be essential. whereas on older computer the older OS may be better.
You can do exactly what is suggested.. buy a new external drive and use that.. External drive plugged into the iMac is no problem and much faster and better than TC.
Or you can plug the USB into the TC and archive the old backups if you want to keep them.. erase the drive of the TC then start again. A clean new backup is a good idea anyway.

Copying Mac App Store Apps may cause Time Machine to fail

Hey folks,
My Time Machine backups started failing the other day with the "error occurred while copying files" error (asking me to run Disk Utility). I ran DU and the drive checked out fine. I eventually checked the backupd logs (Console> filter "backupd") and found that TM was stopping with Error: (-41) SrcErr:No Copying /Path/to/a/file/inside/aMacAppStoreApp. Then saying the backup stopped with error:11.
So I deleted the App and ran the backup again. This time it gave me the same error on another MacAppStore App that I had installed. So I deleted that one too and then TM backup run successfully.
Background:
- There were only two MAS Apps installed (the two referenced above: Quick Note, ARD).
- Both were installed after being downloaded to a different computer, copied to this one, and then a copy made into the Applications folder. They were working fine.
- When I "installed" the Apps, I did not do a drag/drop copy, I did a copy/paste.
- There were two copies of the each App on the filesystem. 1 copy in my "software installers" folder and 1 copy in the Applications folder. Only the copy in the Applications folder failed to backup. The unused copy in the installers folder backed up fine.
Once the backups were working. I then moved the Apps from the "software installers" folder to the Applications folder. I opened the applications and they worked fine. I then ran the backup and it worked fine as well.
So I'm not sure if Time Machine was failing because of my unusual way of copying them into the Applications folder or what? Thoughts? Either way, it seems like a strange thing to cause TM to completely fail.

It's not copy protection issue since after I recopied the App (using drag/drop) the backup worked fine.
You are allowed to copy MAS Apps from one computer to another and run them as long as the target computer is either authorized for the same MAS account or you login to the account that purchased the App.

Time Machine SparseDisk Fails to Delete Old Files

Similar Messages

Maybe you are looking for