Strange behaviour of Time Machine.

I am getting the enclosed notice from Time Machine:
Even so the backing is to 2 TB disk and the backup is about 250GB.
The Hard Drive Was empty before the backup started.
What is going wrong?
Thanks,
Amnon

Open the Time Machine pane in System Preferences. Click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove the problem disk, then add it back. Quit System Preferences. Test.

Similar Messages

Anyone ever successfully solved this strange problem in Time Machine?

Hi Folks,
I have a intel imac running snow leopard (10.6.8) and have a problem I can't seem to solve, and Applecare is having trouble also.
I am trying to do a time machine backup from scratch. I had a previous well-functioning TM backup, but it was trying to do what I thought was an inappropriately large backup and I decided to start afresh. So I went to my external firewire drive and trashed the backup folder. I then re-selected the drive as the backup disc for TM and started over. The backup always stops at 16.13g of a 350+ g backup. There are no error messages...it just sticks there and says "backing up".
To solve this I have tried reformatting the drive in several different paradigms (GUID, Journaled, Nonjournaled, case-sensitive, etc). I even bought a new external drive thinking that might have the problem....it still sticks at the same place. I have also trashed the TM preference files....no difference. Repaired permissions....no change. I even did a archive and reinstall of the OS with preserved user settings.....still gets stuck at the same place.
Does anyone know anything else I could try short of doing a complete re-install of the OS with erasure of all my settings?.... I would really like to avoid that if at all possible.
Many thanks for any ideas.

This is a tough one.
Since you get the same results with 2 different backup drives, it sure sounds like something amiss on the internal's directory structure, but Disk Utility should have found that.
About all I can think of is to try to exclude whatever's causing the problem from being backed-up. If we can manage to do that, then you can try to fix or replace the culprit.
Backups are done alphabetically, starting with your Applications folder, then Library, private (hidden), System, and Users (there are a few other, very small, hidden system folders, too).
So . . . we need to figure out where 16.1 GB's falls in that sequence. See how large each of those folders is, via the Finder or Get Info. Do this as an Admin user, but even so, there are some files and folders you're not authorized to, so the numbers won't be exact.
To see the private folder, you'll need to have the Finder show invisible items; there's a Terminal command for that, but it's probably just as easy to use the TinkerTool app, per #A3 of Time Machine - Troubleshooting.
Then open a Finder window to your internal HD. You'll see all the hidden and visible folders, in the order Time Machine backs them up. (Several of the hidden ones are excluded, so you needn't worry about them.)
Once you have a guesstimate of where the backup gets to 16 GBs, exclude the appropriate folder from backups, via Time Machine Preferences > Options. Then try another backup.
If you can get a good backup that way, then you can narrow it down by removing the large folder exclusion and excluding sub-folders, etc.

"An unexpected error occurred (error code -43)" when launching Time Machine

Hi! When attempting to launch Time Machine, I get the following error:
The operation could not be completed
An unexpected error occurred (error code -43)
My machine is a 2.8 GHz Quad-Core Intel Xeon running 10.5.8
What's strange is that Time Machine DID work just the other day. It would launch automatically when I plugged in my external HD (Maxtor One Touch) though I didn't set it up to back up yet. After I reformatted the drive to Mac OS Extended (Journaled), Time Machine started giving me this error and won't launch. Any ideas here? Thanks!

When you reformatted, it got a new UUID (Universally Unique IDentifier), which may be confusing Time Machine. Try just reselecting it, per +Time Machine Preferences.+
If that doesn't help, try a "full reset" of Time Machine, per #A4 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

Time Machine backups slowing down after 25 days

I am experiencing a peculiar kind of behaviour from Time Machine under
Mountain Lion (10.8.2). In the multiple threads on Time Machine issues,
I could not find this exact problem described so I am wondering if
anyone else has seen the same thing or even has a solution.
Like for many others, the basic symptom is that Time Machine becomes
extremely slow. In my case this always happens about 25 days after the
last reboot. I am using a Mid 2010 27-inch IMAC and a Mid 2010 Mac Pro,
both connected to a Time Capsule via ethernet. Both are showing the
same behaviour.
Originally I was letting Time Machine do its regular hourly backups,
this has now been changed to twice a day using TimeMachineEditor. The
change has made no difference, backups are still getting slow after
25 days. This is accompanied by kernel_task gradually ramping up
its CPU usage, from below a percent to several percent.
Here are the backupd entries from a "normal" backup:
This takes 3-4 min, which I find tolerable - although I
am always surprised by the rather large number of files that
are backed up even if the machine has remained idle:
May 18 18:00:00 myhost.nl com.apple.backupd[75338]: Starting manual backup
May 18 18:00:00 myhost.nl com.apple.backupd[75338]: Attempting to mount network destination URL: afp://Soeren;[email protected]/Backup
May 18 18:00:01 myhost.nl com.apple.backupd[75338]: Mounted network destination at mount point: /Volumes/Backup using URL: afp://Soeren;[email protected]/Backup
May 18 18:00:23 myhost.nl com.apple.backupd[75338]: Disk image /Volumes/Backup/Soeren's IMAC.sparsebundle mounted at: /Volumes/Time Machine Backups
May 18 18:00:23 myhost.nl com.apple.backupd[75338]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
May 18 18:00:56 myhost.nl com.apple.backupd[75338]: Using file event preflight for Macintosh HD
May 18 18:01:07 myhost.nl com.apple.backupd[75338]: Will copy (9.2 MB) from Macintosh HD
May 18 18:01:07 myhost.nl com.apple.backupd[75338]: Found 1150 files (9.2 MB) needing backup
May 18 18:01:07 myhost.nl com.apple.backupd[75338]: 14.53 GB required (including padding), 1.74 TB available
May 18 18:02:50 myhost.nl com.apple.backupd[75338]: Copied 3082 files (48.4 MB) from volume Macintosh HD.
May 18 18:02:50 myhost.nl com.apple.backupd[75338]: Using file event preflight for Macintosh HD
May 18 18:02:50 myhost.nl com.apple.backupd[75338]: Will copy (5.7 MB) from Macintosh HD
May 18 18:02:50 myhost.nl com.apple.backupd[75338]: Found 18 files (5.7 MB) needing backup
May 18 18:02:50 myhost.nl com.apple.backupd[75338]: 14.53 GB required (including padding), 1.74 TB available
May 18 18:03:07 myhost.nl com.apple.backupd[75338]: Copied 1415 files (5.7 MB) from volume Macintosh HD.
May 18 18:03:08 myhost.nl com.apple.backupd[75338]: Created new backup: 2013-05-18-180307
May 18 18:03:12 myhost.nl com.apple.backupd[75338]: Starting post-backup thinning
May 18 18:03:12 myhost.nl com.apple.backupd[75338]: No post-back up thinning needed: no expired backups exist
May 18 18:03:13 myhost.nl com.apple.backupd[75338]: Backup completed successfully.
May 18 18:03:18 myhost.nl com.apple.backupd[75338]: Ejected Time Machine disk image: /Volumes/Backup/Soeren's IMAC.sparsebundle
May 18 18:03:18 myhost.nl com.apple.backupd[75338]: Ejected Time Machine network volume.
And here are the corresponding entries one day later, after the
25-day "limit" had been reached. Note that it takes about an
hour to backup a few MB! Larger backups, when I have actually
been using the computer, can take hours.
May 19 18:00:00 myhost.nl com.apple.backupd[82625]: Starting manual backup
May 19 18:00:01 myhost.nl com.apple.backupd[82625]: Attempting to mount network destination URL: afp://Soeren;[email protected]/Backup
May 19 18:00:01 myhost.nl com.apple.backupd[82625]: Mounted network destination at mount point: /Volumes/Backup using URL: afp://Soeren;[email protected]/Backup
May 19 18:17:13 myhost.nl com.apple.backupd[82625]: Disk image /Volumes/Backup/Soeren's IMAC.sparsebundle mounted at: /Volumes/Time Machine Backups
May 19 18:17:15 myhost.nl com.apple.backupd[82625]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
May 19 18:19:10 myhost.nl com.apple.backupd[82625]: Using file event preflight for Macintosh HD
May 19 18:20:45 myhost.nl com.apple.backupd[82625]: Will copy (5 MB) from Macintosh HD
May 19 18:20:45 myhost.nl com.apple.backupd[82625]: Found 1092 files (5 MB) needing backup
May 19 18:20:46 myhost.nl com.apple.backupd[82625]: 14.54 GB required (including padding), 1.74 TB available
May 19 18:48:03 myhost.nl com.apple.backupd[82625]: Copied 3178 files (47.2 MB) from volume Macintosh HD.
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Using file event preflight for Macintosh HD
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Will copy (6 MB) from Macintosh HD
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Found 170 files (6 MB) needing backup
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: 14.54 GB required (including padding), 1.74 TB available
May 19 18:56:50 myhost.nl com.apple.backupd[82625]: Copied 1831 files (6 MB) from volume Macintosh HD.
May 19 18:56:56 myhost.nl com.apple.backupd[82625]: Created new backup: 2013-05-19-185651
May 19 18:57:39 myhost.nl com.apple.backupd[82625]: Starting post-backup thinning
May 19 19:00:52 myhost.nl com.apple.backupd[82625]: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Soeren's IMAC/2013-05-18-180307 (48.4 MB)
May 19 19:00:52 myhost.nl com.apple.backupd[82625]: Post-back up thinning complete: 1 expired backups removed
May 19 19:00:57 myhost.nl com.apple.backupd[82625]: Backup completed successfully.
May 19 19:01:38 myhost.nl com.apple.backupd[82625]: Ejected Time Machine disk image: /Volumes/Backup/Soeren's IMAC.sparsebundle
May 19 19:01:38 myhost.nl com.apple.backupd[82625]: Ejected Time Machine network volume.
I have now rebooted the machine, and things are back to normal.
In about 25 days, I fully expect that things will start to grind to
a halt again. On the MacPro, which has now been running for 16
days, things should be fine for another 9-10 days.

These are the messages from the first slow backup. This one was only marginally slower than a normal backup, but a sure sign that things were going awry nonetheless:
May 19 06:00:00 myhost.nl com.apple.backupd[79247]: Starting manual backup
May 19 06:00:00 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 06:00:00 myhost.nl com.apple.backupd[79247]: Attempting to mount network destination URL: afp://Soeren;[email protected]/Backup
May 19 06:00:00 myhost.nl com.apple.backupd[79247]: Mounted network destination at mount point: /Volumes/Backup using URL: afp://Soeren;[email protected]/Backup
May 19 06:00:00 myhost kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
May 19 06:00:00 myhost kernel[0]: AFP_VFS afpfs_mount: /Volumes/Backup, pid 79248
May 19 06:00:00 myhost kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80ee82d008 /Volumes/Backup (error = 0, retval = 0)
May 19 06:00:23 myhost.nl com.apple.backupd[79247]: Disk image /Volumes/Backup/Soeren's IMAC.sparsebundle mounted at: /Volumes/Time Machine Backups
May 19 06:00:23 myhost.nl com.apple.backupd[79247]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
May 19 06:01:14 myhost.nl com.apple.backupd[79247]: Using file event preflight for Macintosh HD
May 19 06:01:28 myhost.nl com.apple.backupd[79247]: Will copy (36.7 MB) from Macintosh HD
May 19 06:01:28 myhost.nl com.apple.backupd[79247]: Found 411 files (36.7 MB) needing backup
May 19 06:01:28 myhost.nl com.apple.backupd[79247]: 14.57 GB required (including padding), 1.74 TB available
May 19 06:02:34 myhost.nl mdworker[79274]: Unable to talk to lsboxd
May 19 06:02:34 myhost.nl mdworker[79275]: Unable to talk to lsboxd
May 19 06:02:34 myhost.nl sandboxd[79276] ([79274]): mdworker(79274) deny mach-lookup com.apple.ls.boxd
May 19 06:02:34 myhost.nl sandboxd[79276] ([79275]): mdworker(79275) deny mach-lookup com.apple.ls.boxd
May 19 06:02:34 myhost kernel[0]: Sandbox: sandboxd(79276) deny mach-lookup com.apple.coresymbolicationd
May 19 06:04:02 myhost.nl netbiosd[76]: name servers down?
May 19 06:04:31 myhost.nl com.apple.backupd[79247]: Copied 2912 files (77.9 MB) from volume Macintosh HD.
May 19 06:04:31 myhost.nl com.apple.backupd[79247]: Using file event preflight for Macintosh HD
May 19 06:04:31 myhost.nl com.apple.backupd[79247]: Will copy (5.6 MB) from Macintosh HD
May 19 06:04:31 myhost.nl com.apple.backupd[79247]: Found 22 files (5.6 MB) needing backup
May 19 06:04:31 myhost.nl com.apple.backupd[79247]: 14.54 GB required (including padding), 1.74 TB available
May 19 06:04:36 myhost.nl mdworker[79290]: Unable to talk to lsboxd
May 19 06:04:36 myhost.nl mdworker[79291]: Unable to talk to lsboxd
May 19 06:04:36 myhost.nl sandboxd[79292] ([79290]): mdworker(79290) deny mach-lookup com.apple.ls.boxd
May 19 06:04:36 myhost.nl sandboxd[79292] ([79291]): mdworker(79291) deny mach-lookup com.apple.ls.boxd
May 19 06:04:36 myhost kernel[0]: Sandbox: sandboxd(79292) deny mach-lookup com.apple.coresymbolicationd
May 19 06:04:49 myhost.nl com.apple.backupd[79247]: Copied 1424 files (5.6 MB) from volume Macintosh HD.
May 19 06:04:50 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 06:04:50 myhost.nl com.apple.backupd[79247]: Created new backup: 2013-05-19-060449
May 19 06:04:53 myhost.nl com.apple.backupd[79247]: Starting post-backup thinning
May 19 06:05:40 myhost.nl com.apple.backupd[79247]: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Soeren's IMAC/2013-04-19-001551 (83 MB)
May 19 06:05:48 myhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=79313[GoogleSoftwareUp] clearing CS_VALID
May 19 06:06:04 myhost.nl com.apple.backupd[79247]: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Soeren's IMAC/2013-05-17-180350 (48.9 MB)
May 19 06:06:04 myhost.nl com.apple.backupd[79247]: Post-back up thinning complete: 2 expired backups removed
May 19 06:06:04 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 06:06:04 myhost.nl com.apple.backupd[79247]: Backup completed successfully.
May 19 06:06:11 myhost.nl com.apple.backupd[79247]: Ejected Time Machine disk image: /Volumes/Backup/Soeren's IMAC.sparsebundle
May 19 06:06:11 myhost.nl com.apple.backupd[79247]: Ejected Time Machine network volume.
May 19 06:06:11 myhost kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Backup, flags 0, pid 79318
May 19 06:06:11 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/Backup 0xffffff80ee82d008
May 19 06:06:11 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/Backup 0xffffff80ee82d008
May 19 06:06:11 myhost kernel[0]: AFP_VFS afpfs_unmount : afpfs_DoReconnect sent signal for unmount to proceed
Here is then the full log for the next backup, 12 hrs later (this is the one I posted earlier):
The message at 19:01:11 about mds not responding seems to be related to this. I have seen that a few times during these slow backups, but not otherwise.
May 19 18:00:00 myhost.nl com.apple.backupd[82625]: Starting manual backup
May 19 18:00:00 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 18:00:01 myhost.nl com.apple.backupd[82625]: Attempting to mount network destination URL: afp://Soeren;[email protected]/Backup
May 19 18:00:01 myhost.nl com.apple.backupd[82625]: Mounted network destination at mount point: /Volumes/Backup using URL: afp://Soeren;[email protected]/Backup
May 19 18:00:02 myhost kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
May 19 18:00:02 myhost kernel[0]: AFP_VFS afpfs_mount: /Volumes/Backup, pid 82627
May 19 18:00:02 myhost kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80ee853008 /Volumes/Backup (error = 0, retval = 0)
May 19 18:00:43 myhost.nl apsd[59]: <APSConnectionNotificationQueue: 0x7f7f51021020>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
May 19 18:01:13 --- last message repeated 2 times ---
May 19 18:02:35 myhost.nl mdworker[82632]: Unable to talk to lsboxd
May 19 18:02:35 myhost.nl sandboxd[82633] ([82632]): mdworker(82632) deny mach-lookup com.apple.ls.boxd
May 19 18:02:35 myhost kernel[0]: Sandbox: sandboxd(82633) deny mach-lookup com.apple.coresymbolicationd
May 19 18:02:56 myhost.nl netbiosd[76]: name servers down?
May 19 18:05:27 myhost.nl apsd[59]: <APSConnectionNotificationQueue: 0x7f7f51021020>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
May 19 18:05:57 --- last message repeated 2 times ---
May 19 18:11:33 myhost.nl mdworker[82687]: Unable to talk to lsboxd
May 19 18:11:33 myhost.nl sandboxd[82688] ([82687]): mdworker(82687) deny mach-lookup com.apple.ls.boxd
May 19 18:11:33 myhost kernel[0]: Sandbox: sandboxd(82688) deny mach-lookup com.apple.coresymbolicationd
May 19 18:15:33 myhost.nl netbiosd[76]: name servers down?
May 19 18:17:13 myhost.nl com.apple.backupd[82625]: Disk image /Volumes/Backup/Soeren's IMAC.sparsebundle mounted at: /Volumes/Time Machine Backups
May 19 18:17:15 myhost.nl com.apple.backupd[82625]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
May 19 18:19:10 myhost.nl com.apple.backupd[82625]: Using file event preflight for Macintosh HD
May 19 18:20:33 myhost.nl mdworker[82745]: Unable to talk to lsboxd
May 19 18:20:34 myhost kernel[0]: Sandbox: sandboxd(82747) deny mach-lookup com.apple.coresymbolicationd
May 19 18:20:34 myhost.nl sandboxd[82747] ([82745]): mdworker(82745) deny mach-lookup com.apple.ls.boxd
May 19 18:20:45 myhost.nl com.apple.backupd[82625]: Will copy (5 MB) from Macintosh HD
May 19 18:20:45 myhost.nl com.apple.backupd[82625]: Found 1092 files (5 MB) needing backup
May 19 18:20:46 myhost.nl com.apple.backupd[82625]: 14.54 GB required (including padding), 1.74 TB available
May 19 18:29:35 myhost.nl netbiosd[76]: name servers down?
May 19 18:31:11 myhost.nl mdworker[82800]: Unable to talk to lsboxd
May 19 18:31:11 myhost.nl sandboxd[82801] ([82800]): mdworker(82800) deny mach-lookup com.apple.ls.boxd
May 19 18:31:11 myhost kernel[0]: Sandbox: sandboxd(82801) deny mach-lookup com.apple.coresymbolicationd
May 19 18:41:03 myhost.nl netbiosd[76]: name servers down?
May 19 18:41:15 myhost.nl mdworker[82847]: Unable to talk to lsboxd
May 19 18:41:15 myhost kernel[0]: Sandbox: sandboxd(82848) deny mach-lookup com.apple.coresymbolicationd
May 19 18:41:15 myhost.nl sandboxd[82848] ([82847]): mdworker(82847) deny mach-lookup com.apple.ls.boxd
May 19 18:48:03 myhost.nl com.apple.backupd[82625]: Copied 3178 files (47.2 MB) from volume Macintosh HD.
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Using file event preflight for Macintosh HD
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Will copy (6 MB) from Macintosh HD
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: Found 170 files (6 MB) needing backup
May 19 18:48:05 myhost.nl com.apple.backupd[82625]: 14.54 GB required (including padding), 1.74 TB available
May 19 18:49:02 myhost.nl netbiosd[76]: name servers down?
May 19 18:49:08 myhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=82886[GoogleSoftwareUp] clearing CS_VALID
May 19 18:51:55 myhost.nl mdworker[82911]: Unable to talk to lsboxd
May 19 18:51:56 myhost.nl sandboxd[82912] ([82911]): mdworker(82911) deny mach-lookup com.apple.ls.boxd
May 19 18:51:56 myhost kernel[0]: Sandbox: sandboxd(82912) deny mach-lookup com.apple.coresymbolicationd
May 19 18:56:50 myhost.nl com.apple.backupd[82625]: Copied 1831 files (6 MB) from volume Macintosh HD.
May 19 18:56:55 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 18:56:56 myhost.nl com.apple.backupd[82625]: Created new backup: 2013-05-19-185651
May 19 18:57:39 myhost.nl com.apple.backupd[82625]: Starting post-backup thinning
May 19 19:00:52 myhost.nl com.apple.backupd[82625]: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Soeren's IMAC/2013-05-18-180307 (48.4 MB)
May 19 19:00:52 myhost.nl com.apple.backupd[82625]: Post-back up thinning complete: 1 expired backups removed
May 19 19:00:54 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 19 19:00:57 myhost.nl com.apple.backupd[82625]: Backup completed successfully.
May 19 19:01:11 myhost.nl diskarbitrationd[16]: mds [38]:16919 not responding.
May 19 19:01:38 myhost.nl com.apple.backupd[82625]: Ejected Time Machine disk image: /Volumes/Backup/Soeren's IMAC.sparsebundle
May 19 19:01:38 myhost.nl com.apple.backupd[82625]: Ejected Time Machine network volume.
May 19 19:01:38 myhost kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Backup, flags 0, pid 82962
May 19 19:01:38 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/Backup 0xffffff80ee853008
May 19 19:01:38 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/Backup 0xffffff80ee853008
May 19 19:01:38 myhost kernel[0]: AFP_VFS afpfs_unmount : afpfs_DoReconnect sent signal for unmount to proceed
In case you want to see yet another one, here is the next backup. This took even longer..
May 20 06:00:00 myhost.nl com.apple.backupd[85963]: Starting manual backup
May 20 06:00:00 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 20 06:00:01 myhost.nl com.apple.backupd[85963]: Attempting to mount network destination URL: afp://Soeren;[email protected]/Backup
May 20 06:00:02 myhost.nl com.apple.backupd[85963]: Mounted network destination at mount point: /Volumes/Backup using URL: afp://Soeren;[email protected]/Backup
May 20 06:00:02 myhost kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
May 20 06:00:02 myhost kernel[0]: AFP_VFS afpfs_mount: /Volumes/Backup, pid 85965
May 20 06:00:02 myhost kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80ee828008 /Volumes/Backup (error = 0, retval = 0)
May 20 06:00:49 myhost.nl mdworker[85968]: Unable to talk to lsboxd
May 20 06:00:49 myhost.nl sandboxd[85969] ([85968]): mdworker(85968) deny mach-lookup com.apple.ls.boxd
May 20 06:00:50 myhost kernel[0]: Sandbox: sandboxd(85969) deny mach-lookup com.apple.coresymbolicationd
May 20 06:08:47 myhost.nl mdworker[85995]: Unable to talk to lsboxd
May 20 06:08:48 myhost.nl sandboxd[85996] ([85995]): mdworker(85995) deny mach-lookup com.apple.ls.boxd
May 20 06:08:48 myhost kernel[0]: Sandbox: sandboxd(85996) deny mach-lookup com.apple.coresymbolicationd
May 20 06:08:59 myhost.nl netbiosd[76]: name servers down?
May 20 06:13:40 myhost.nl netbiosd[76]: name servers down?
May 20 06:16:58 myhost.nl mdworker[86043]: Unable to talk to lsboxd
May 20 06:16:59 myhost.nl sandboxd[86044] ([86043]): mdworker(86043) deny mach-lookup com.apple.ls.boxd
May 20 06:16:59 myhost kernel[0]: Sandbox: sandboxd(86044) deny mach-lookup com.apple.coresymbolicationd
May 20 06:17:12 myhost.nl com.apple.backupd[85963]: Disk image /Volumes/Backup/Soeren's IMAC.sparsebundle mounted at: /Volumes/Time Machine Backups
May 20 06:17:14 myhost.nl com.apple.backupd[85963]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
May 20 06:20:49 myhost.nl fseventsd[48]: event logs in /Volumes/Time Machine Backups/.fseventsd out of sync with volume. destroying old logs. (13 220 40785)
May 20 06:25:39 myhost.nl mdworker[86090]: Unable to talk to lsboxd
May 20 06:25:40 myhost kernel[0]: Sandbox: sandboxd(86091) deny mach-lookup com.apple.coresymbolicationd
May 20 06:25:40 myhost.nl sandboxd[86091] ([86090]): mdworker(86090) deny mach-lookup com.apple.ls.boxd
May 20 06:31:31 myhost.nl netbiosd[76]: name servers down?
May 20 06:33:44 myhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=86114[GoogleSoftwareUp] clearing CS_VALID
May 20 06:34:54 myhost.nl mdworker[86117]: Unable to talk to lsboxd
May 20 06:34:55 myhost kernel[0]: Sandbox: sandboxd(86132) deny mach-lookup com.apple.coresymbolicationd
May 20 06:34:55 myhost.nl sandboxd[86132] ([86117]): mdworker(86117) deny mach-lookup com.apple.ls.boxd
May 20 06:43:57 myhost.nl mdworker[86154]: Unable to talk to lsboxd
May 20 06:43:57 myhost kernel[0]: Sandbox: sandboxd(86155) deny mach-lookup com.apple.coresymbolicationd
May 20 06:43:57 myhost.nl sandboxd[86155] ([86154]): mdworker(86154) deny mach-lookup com.apple.ls.boxd
May 20 06:45:12 myhost.nl netbiosd[76]: name servers down?
May 20 06:53:01 myhost.nl mdworker[86192]: Unable to talk to lsboxd
May 20 06:53:01 myhost.nl sandboxd[86193] ([86192]): mdworker(86192) deny mach-lookup com.apple.ls.boxd
May 20 06:53:01 myhost kernel[0]: Sandbox: sandboxd(86193) deny mach-lookup com.apple.coresymbolicationd
May 20 06:57:15 myhost.nl netbiosd[76]: name servers down?
May 20 07:01:40 myhost.nl mdworker[86231]: Unable to talk to lsboxd
May 20 07:01:40 myhost.nl sandboxd[86232] ([86231]): mdworker(86231) deny mach-lookup com.apple.ls.boxd
May 20 07:01:41 myhost kernel[0]: Sandbox: sandboxd(86232) deny mach-lookup com.apple.coresymbolicationd
May 20 07:09:06 myhost.nl fseventsd[48]: log dir: /Volumes/Time Machine Backups/.fseventsd getting new uuid: 581D7EBC-9D7D-40A2-861C-486D09F787AA
May 20 07:09:15 myhost.nl netbiosd[76]: name servers down?
May 20 07:09:48 myhost.nl mdworker[86257]: Unable to talk to lsboxd
May 20 07:09:49 myhost.nl sandboxd[86272] ([86257]): mdworker(86257) deny mach-lookup com.apple.ls.boxd
May 20 07:09:49 myhost kernel[0]: Sandbox: sandboxd(86272) deny mach-lookup com.apple.coresymbolicationd
May 20 07:10:18 myhost.nl com.apple.backupd[85963]: Using file event preflight for Macintosh HD
May 20 07:11:14 myhost.nl com.apple.backupd[85963]: Will copy (4.4 MB) from Macintosh HD
May 20 07:11:14 myhost.nl com.apple.backupd[85963]: Found 306 files (4.4 MB) needing backup
May 20 07:11:14 myhost.nl com.apple.backupd[85963]: 14.54 GB required (including padding), 1.74 TB available
May 20 07:13:47 myhost.nl netbiosd[76]: name servers down?
May 20 07:19:31 myhost.nl mdworker[86304]: Unable to talk to lsboxd
May 20 07:19:31 myhost kernel[0]: Sandbox: sandboxd(86305) deny mach-lookup com.apple.coresymbolicationd
May 20 07:19:31 myhost.nl sandboxd[86305] ([86304]): mdworker(86304) deny mach-lookup com.apple.ls.boxd
May 20 07:29:54 myhost.nl mdworker[86351]: Unable to talk to lsboxd
May 20 07:29:54 myhost kernel[0]: Sandbox: sandboxd(86366) deny mach-lookup com.apple.coresymbolicationd
May 20 07:29:54 myhost.nl sandboxd[86366] ([86351]): mdworker(86351) deny mach-lookup com.apple.ls.boxd
May 20 07:32:27 myhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=86372[GoogleSoftwareUp] clearing CS_VALID
May 20 07:33:26 myhost.nl com.apple.backupd[85963]: Copied 1917 files (11.7 MB) from volume Macintosh HD.
May 20 07:33:27 myhost.nl com.apple.backupd[85963]: Using file event preflight for Macintosh HD
May 20 07:33:27 myhost.nl com.apple.backupd[85963]: Will copy (5.9 MB) from Macintosh HD
May 20 07:33:27 myhost.nl com.apple.backupd[85963]: Found 156 files (5.9 MB) needing backup
May 20 07:33:27 myhost.nl com.apple.backupd[85963]: 14.54 GB required (including padding), 1.74 TB available
May 20 07:33:58 myhost.nl netbiosd[76]: name servers down?
May 20 07:44:14 myhost.nl mdworker[86412]: Unable to talk to lsboxd
May 20 07:44:15 myhost.nl sandboxd[86413] ([86412]): mdworker(86412) deny mach-lookup com.apple.ls.boxd
May 20 07:44:15 myhost kernel[0]: Sandbox: sandboxd(86413) deny mach-lookup com.apple.coresymbolicationd
May 20 07:45:27 myhost.nl netbiosd[76]: name servers down?
May 20 07:55:37 myhost.nl netbiosd[76]: name servers down?
May 20 07:58:57 myhost.nl mdworker[86459]: Unable to talk to lsboxd
May 20 07:58:57 myhost kernel[0]: Sandbox: sandboxd(86460) deny mach-lookup com.apple.coresymbolicationd
May 20 07:58:57 myhost.nl sandboxd[86460] ([86459]): mdworker(86459) deny mach-lookup com.apple.ls.boxd
May 20 08:09:31 myhost.nl netbiosd[76]: name servers down?
May 20 08:13:14 myhost.nl mdworker[86516]: Unable to talk to lsboxd
May 20 08:13:14 myhost kernel[0]: Sandbox: sandboxd(86517) deny mach-lookup com.apple.coresymbolicationd
May 20 08:13:20 myhost.nl sandboxd[86517] ([86516]): mdworker(86516) deny mach-lookup com.apple.ls.boxd
May 20 08:14:16 myhost.nl netbiosd[76]: name servers down?
May 20 08:27:46 myhost.nl mdworker[86567]: Unable to talk to lsboxd
May 20 08:27:47 myhost kernel[0]: Sandbox: sandboxd(86568) deny mach-lookup com.apple.coresymbolicationd
May 20 08:27:47 myhost.nl sandboxd[86568] ([86567]): mdworker(86567) deny mach-lookup com.apple.ls.boxd
May 20 08:29:21 myhost.nl com.apple.backupd[85963]: Copied 1608 files (907.6 MB) from volume Macintosh HD.
May 20 08:29:25 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 20 08:29:27 myhost.nl com.apple.backupd[85963]: Created new backup: 2013-05-20-082922
May 20 08:30:00 myhost.nl com.apple.backupd[85963]: Starting post-backup thinning
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[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)
May 20 08:31:10 myhost kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=86593[GoogleSoftwareUp] clearing CS_VALID
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateEngine updateProductID:] KSUpdateEngine updating product ID: "com.google.Keystone"
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSCheckAction performAction] KSCheckAction checking 1 ticket(s).
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction starting update check for ticket(s): {(
                    <KSTicket:0x546640
                              productID=com.google.Keystone
                              version=1.1.0.3659
                              xc=<KSPathExistenceChecker:0x546580 path=/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/>
                              serverType=Omaha
                              url=https://tools.google.com/service/update2
                              creationDate=2010-06-26 09:28:46
                    >
          Using server: <KSOmahaServer:0x256da0
                    engine=<KSDaemonUpdateEngine:0x1856510>
                    params={
                              EngineVersion = "1.1.0.3659";
                              ActivesInfo = {
                                        "com.google.macphotouploader" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:57 +0000;
                                        "com.google.Chrome" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActiveDate = 2011-01-07 15:41:05 +0000;
                                                  LastActivePingDate = 2011-01-08 08:00:00 +0000;
                                        "com.google.GoogleDrive" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActivePingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActiveDate = 2013-05-20 05:38:35 +0000;
                                        "com.google.Keystone" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:57 +0000;
                                                  LastActivePingDate = 2013-05-19 06:59:57 +0000;
                                                  LastActiveDate = 2013-05-20 06:31:10 +0000;
                                        "com.Google.GoogleEarthPlugin.intel" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                        "com.Google.GoogleEarthPlus" = {
                                                  LastRollCallPingDate = 2011-05-31 07:00:00 +0000;
                                        "com.Google.GoogleEarthPlus.intel" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +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"
          >
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction running KSServerUpdateRequest: <KSOmahaServerUpdateRequest:0x25ad60
                    server=<KSOmahaServer:0x256da0>
                    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="1058" brand="GGLG">
                                      <o:updatecheck></o:updatecheck>
                                  </o:app>
                              </o:gupdate>
          >
May 20 08:31:10 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction(KSServerUpdateRequestDelegate) serverRequest:fetchedWithResponse:] KSUpdateCheckAction received KSServerUpdateResponse: <KSOmahaServerUpdateResponse:0x1c44170
                    server=<KSOmahaServer:0x256da0>
                    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="84674"></daystart>
                                  <app appid="com.google.Keystone" status="ok">
                                      <updatecheck status="noupdate"></updatecheck>
                                  </app>
                              </gupdate>
          >
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction(PrivateMethods) finishAction] KSUpdateCheckAction found updates: {( )}
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSPrefetchAction performAction] KSPrefetchAction no updates to prefetch.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSMultiUpdateAction performAction] KSSilentUpdateAction had no updates to apply.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSMultiUpdateAction performAction] KSPromptAction had no updates to apply.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateEngine(PrivateMethods) updateFinish] KSUpdateEngine update processing complete.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateEngine updateAllProducts] KSUpdateEngine updating all installed products.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSCheckAction performAction] KSCheckAction checking 2 ticket(s).
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction starting update check for ticket(s): {(
                    <KSTicket:0x546640
                              productID=com.google.Keystone
                              version=1.1.0.3659
                              xc=<KSPathExistenceChecker:0x545c20 path=/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/>
                              serverType=Omaha
                              url=https://tools.google.com/service/update2
                              creationDate=2010-06-26 09:28:46
                    >,
                    <KSTicket:0x546ec0
                              productID=com.google.macphotouploader
                              version=1.5.0.1425
                              xc=<KSLaunchServicesExistenceChecker:0x547260 bundle=com.google.macphotouploader>
                              url=https://tools.google.com/service/update2
                              creationDate=2008-12-06 18:11:10
                    >
          Using server: <KSOmahaServer:0x1a4a600
                    engine=<KSDaemonUpdateEngine:0x1856510>
                    params={
                              EngineVersion = "1.1.0.3659";
                              ActivesInfo = {
                                        "com.google.macphotouploader" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:57 +0000;
                                        "com.google.Chrome" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActiveDate = 2011-01-07 15:41:05 +0000;
                                                  LastActivePingDate = 2011-01-08 08:00:00 +0000;
                                        "com.google.GoogleDrive" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActivePingDate = 2013-05-19 06:59:56 +0000;
                                                  LastActiveDate = 2013-05-20 05:38:35 +0000;
                                        "com.google.Keystone" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:57 +0000;
                                                  LastActivePingDate = 2013-05-19 06:59:57 +0000;
                                                  LastActiveDate = 2013-05-20 06:31:10 +0000;
                                        "com.Google.GoogleEarthPlugin.intel" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +0000;
                                        "com.Google.GoogleEarthPlus" = {
                                                  LastRollCallPingDate = 2011-05-31 07:00:00 +0000;
                                        "com.Google.GoogleEarthPlus.intel" = {
                                                  LastRollCallPingDate = 2013-05-19 06:59:56 +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"
          >
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction performAction] KSUpdateCheckAction running KSServerUpdateRequest: <KSOmahaServerUpdateRequest:0x1a4dc20
                    server=<KSOmahaServer:0x1a4a600>
                    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.Keystone" version="1.1.0.3659" lang="en-us" installage="1058" brand="GGLG">
                                      <o:updatecheck></o:updatecheck>
                                  </o:app>
                                  <o:app appid="com.google.macphotouploader" version="1.5.0.1425" lang="en-us" installage="1625" brand="GGLG">
                                      <o:updatecheck></o:updatecheck>
                                  </o:app>
                              </o:gupdate>
          >
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction(KSServerUpdateRequestDelegate) serverRequest:fetchedWithResponse:] KSUpdateCheckAction received KSServerUpdateResponse: <KSOmahaServerUpdateResponse:0x1867890
                    server=<KSOmahaServer:0x1a4a600>
                    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="84675"></daystart>
                                  <app appid="com.google.Keystone" status="ok">
                                      <updatecheck status="noupdate"></updatecheck>
                                  </app>
                                  <app appid="com.google.macphotouploader" status="ok">
                                      <updatecheck status="noupdate"></updatecheck>
                                  </app>
                              </gupdate>
          >
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateCheckAction(PrivateMethods) finishAction] KSUpdateCheckAction found updates: {( )}
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSPrefetchAction performAction] KSPrefetchAction no updates to prefetch.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSMultiUpdateAction performAction] KSSilentUpdateAction had no updates to apply.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSMultiUpdateAction performAction] KSPromptAction had no updates to apply.
May 20 08:31:11 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KSUpdateEngine(PrivateMethods) updateFinish] KSUpdateEngine update processing complete.
May 20 08:31:13 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[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)
May 20 08:31:40 myhost.nl GoogleSoftwareUpdateDaemon[86594]: -[KeystoneDaemon main] GoogleSoftwareUpdateDaemon inactive, shutdown.
May 20 08:32:43 myhost.nl netbiosd[76]: name servers down?
May 20 08:37:45 myhost.nl com.apple.backupd[85963]: Deleted /Volumes/Time Machine Backups/Backups.backupdb/Soeren's IMAC/2013-04-20-001649 (118.6 MB)
May 20 08:37:45 myhost.nl com.apple.backupd[85963]: Post-back up thinning complete: 1 expired backups removed
May 20 08:37:47 myhost.nl com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
May 20 08:37:52 myhost.nl com.apple.backupd[85963]: Backup completed successfully.
May 20 08:38:06 myhost.nl diskarbitrationd[16]: mds [38]:16919 not responding.
May 20 08:38:06 myhost.nl diskarbitrationd[16]: fseventsd [48]:16643 not responding.
May 20 08:38:30 myhost.nl mdworker[86623]: Unable to talk to lsboxd
May 20 08:38:30 myhost kernel[0]: Sandbox: sandboxd(86624) deny mach-lookup com.apple.coresymbolicationd
May 20 08:38:31 myhost.nl sandboxd[86624] ([86623]): mdworker(86623) deny mach-lookup com.apple.ls.boxd
May 20 08:38:32 myhost.nl fseventsd[48]: disk logger: failed to open output file /Volumes/Time Machine Backups/.fseventsd/6365734200d27745 (No such file or directory). mount point /Volumes/Time Machine Backups/.fseventsd
May 20 08:38:36 myhost.nl com.apple.backupd[85963]: Ejected Time Machine disk image: /Volumes/Backup/Soeren's IMAC.sparsebundle
May 20 08:38:36 myhost.nl com.apple.backupd[85963]: Ejected Time Machine network volume.
May 20 08:38:36 myhost kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Backup, flags 0, pid 86627
May 20 08:38:36 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/Backup 0xffffff80ee828008
May 20 08:38:36 myhost kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/Backup 0xffffff80ee828008
May 20 08:38:36 myhost kernel[0]: AFP_VFS afpfs_unmount : afpfs_DoReconnect sent signal for unmount to proceed
I let this go on for another couple of days, then rebooted. Things are now back to normal.

Problem using Time machine in Yosemite

I have recently reformatted my Macintosh HD in my iMAC 21,5 from 2010, downloaded latest version of Yosemite and after that reloaded
all my backup data using Time Machine. I then ran a fresh initial backup again by Time machine to the same external hard disk. That
took of course a few hours (5) for 16 GB. Next day, after having made some updates in my documents etc, I took a new backup. This time
in 1.5 hours for 160 GB. Again one day later, after having done only very minor work in my computer, I took a backup again expecting it
to be run in just 5 minutes or so. It took however 45 minutes and 67 GB were backuped. All this does not make sense to me at all.
Since at least a year back I have regurlary run my backups once a week, and it has typically been completed in approx. 5 minutes for on average
of 3 to 5 GB.
Can anybody give me some hints how to handle this? What could possibly be the reason for this strange behavior of Time machine?
Do I have to buy a new external hard disk, or what shall I do?
Kindly regards
Dennis 2008

When the "absurd 139-GB-backup" was completed, I ran a disk control again, and the result looked OK. So I decided to give it one more chance.
I made a few changes to an excel-document, in order to get some minor updates, and then I started a backup run again.
And this time it behaved exactly the way I expected! Only 253 MB in 2 minutes!!
It really looks very promising now. I will wait until tomorrow though, before I try again. And if it works fine then, I will mark your answer as 'This solved my question'.
If I still get the absurd GB-backups, I guess I shall follow your suggestion and buy a new EHD, as you recommend. Even if the one I have is not even one year old!
But it looks very promising now. I think you have solved my problem.
Regards
Dennis

Time Machine and Time Capsule not working well.

Greetings,
I am having strange issues with Time Machine and the Time Capsule. I am using a MacBook Pro and have the 1TB Time Capsule. I am also using the Time Capsule as the wireless base station for my network.
The issue is, Time Machine has only once created a full back-up. Since then, it could not either connect to the disk or mount the image. I have tried several things like renaming my computer and renaming the Time Capsule. I have also tried copying via LAN and wireless. I even went as far as erasing the disk.
Now that the disk is erased, Time Machine cannot create an imgage on the drive. This is my latest issue.
Is this kind of trouble wide spread or very rare? Any way to fix it?
As a work-around, I am using Smart Backup instead of Time Machine to do my back-ups.

Standard Lion and ML issue..
Just reboot the TC.. sometimes with ML you may need to reboot the whole network.
In Lion you can use 5.6utilty and disconnect all users.. but apple has not made 5.6 utility available for ML or not yet. Perhaps they don't know about the bug. or if you put your head deep enough in the sand you can pretend there is no such problem.. it does expose some other parts!!
Pondini has info on a work around to load 5.6 utility into ML.
Read C12 and C17
http://pondini.org/TM/Troubleshooting.html

Time machine will not work after upgrade

Since I upgraded to Mavericks on Oct. 22, Time Machine will not run properly, or at all for that matter. It tells me that it is 'Preparing Backup', but it was said that for over 4 days now. Suggestions?

I had a strange issue with Time Machine and Mavericks. Time machine wouldn't recognise the external USB drive I was using for backups. There was nothing in the logs, no errors, the time for the backup would come along and then it would skip to the next hour with no backup being done. What I was doing was removing the drive from Time Machine Preferences and re-adding it, TM would then start a manual backup and from that point it would run fine.
I ended up doing a Disc Verify on the drive (all ok, no issues) and shut the machine down. Today I booted up and staright away the TM Icon for the drive is correct and the TM is running as it used to.
I have three macs, all with external USB drives, the other two macs have no issues with TM, only my main one. Having a look at other issues, my external drive is a Western Digital unit so maybe that has something to do with it, though it can see the drive fine from Finder.
Anyway, if you are having similar issues, just run the Disc Verify Utility (and repair if there are errors) and hopefully it'll fix up that particular issue.

Time Machine won't backup... because there's too much free space??

Hi all,
I'm getting a strange error from Time Machine:
"*Time Machine Error*
This backup is too large for the backup volume. The backup requires 147.8 MB but only 506.8 MB are available.
To select a larger volume, or make the backup smaller by excluding files, open System Preferences and choose Time Machine."
I should probably also note that, according to Finder, my Time Machine volume has only 27.5 MB available out of 182.89 GB.
I'm confused!
Thanks in advance,
Mike

Hi all,
Update: The same Time Machine Error message has just popped up again, only this time it says, "The backup requires 173.2 MB but only 823.1 MB are available."
Now I'm even more confused!
Thanks in advance (again),
Mike

Software issues after restoring from Time Machine backup.

Hi all,
I recently had to do a full restore from my time machine back ups. Everything worked flawlessly and when the restore was done, I appeared to have my OS, apps and data all the way they were prior to the failure.
Now I'm experiencing strange behavior from some of my applications.
First, when I use Safari’s "Top Sites" feature it shuts down the application with no associated error message.
Second, when I attempted to launch MS Word, I received an error stating that there was a problem with the Office database and it instructed me to use the included db repair utility (I'm sorry, I'm at work and I don't have access to the actual error messages at the moment). I did this, and after some time it reported the same error.
I shrugged my shoulders and used the included uninstall to remove Office from my machine and then re-installed. After the install was complete I launched Word and got the same error.
Is there any history of applications behaving strangely after a Time Machine restore? How can I totally remove MS Office such that whatever db the error references is gone as well?

The hard drive was bad. The OS locked up after trying to load iTunes. I rebooted and after the reboot everything ran very, very slowly. After several reboot attempts, the machine would not boot past the grey apple screen. I attempted to use /sbin/fsck -fy to repair and after running that several times (with varying outputs but all stating that the disk could not be repaired) I eventually was getting the same output over and over with a statement that no repair could be made.
I then bought Disk Warrior and ran it against my iMac using my wife's MacBook Pro. Disk Warrior returned a similar error stating that the disk couldn't be repaired.
Finally, I decided to re-install the OS and restore from back up but after several attempts to re-install the install would invariably fail after the consistency check of the DVD had completed and the install was to begin. It said something short like "There was an error with this install. Please try installing again." At this point, I surmised that the disk was a lost cause. I had the hard drive replaced and then restored from my Time Machine back up.
After the change in hard drive, the OS install ran just fine and the restore ran fine as well.
Thanks!

Strange Behaviour in Pentium IV machine

Hi all. I put this post in Java HotSpot forum, but that forum seems not to be as popular as this, so I've decided to post it here too.
I've been reading posts in this forum (and another in this site) for more than a week trying to find any idea that could help me with my "strange" problem, but with no success.
I've developed an application that manages some info stored in Mysql. My developing machine is a Pentium II (400MHz) with Red Hat 7.3 Valhalla installed. I use Mysql 3.23.49 and J/Connector (version 2.0.14) downloaded from Mysql site and JRE version 1.4.1.-b21.
The production machine is a Pentium IV (1.60 GHz) , with the same Red Hat version, the same JRE version and Mysql 3.23.51.
Well, in developing machine I am able to run up to 4 instances of the application witout crashing, only decreasing timing performance. But in production machine, I get and "strange" behaviour. Sometimes (1 of each 10 times) the application crashes (even the machine crashes sometimes), and I get Hot Spot log files (hs_err_pid####.log) like these
Type 1 ------------------------------------->
Unexpected Signal : 11 occurred at PC=0x403291D8
Function=skip_method_invoke_and_aux_frames__12vframeStream+0x58
Library=/usr/java/j2sdk1.4.1/jre/lib/i386/client/libjvm.so
Current Java thread:
at java.security.AccessController.doPrivileged(Native Method)
at sun.io.Converters.getDefaultEncodingName(Converters.java:66)
at java.lang.StringCoding.decode(StringCoding.java:226)
at java.lang.String.<init>(String.java:383)
at com.mysql.jdbc.Buffer.readLenString(Unknown Source)
at com.mysql.jdbc.MysqlIO.getResultSet(Unknown Source)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(Unknown Source)
at com.mysql.jdbc.MysqlIO.sqlQuery(Unknown Source)
at com.mysql.jdbc.Connection.execSQL(Unknown Source)
- locked <0x448f92d0> (a com.mysql.jdbc.jdbc2.IO)
at com.mysql.jdbc.Connection.execSQL(Unknown Source)
at com.mysql.jdbc.Statement.executeQuery(Unknown Source)
- locked <0x448f92d0> (a com.mysql.jdbc.jdbc2.IO)
at com.mysql.jdbc.jdbc2.Statement.executeQuery(Unknown Source)
at GeneraTablaDiasCerrados.<init>(GeneraTablaDiasCerrados.java:99)
at GeneraTablaDiasCerrados.main(GeneraTablaDiasCerrados.java:425)
Type 2------------------------------------------------>
Unexpected Signal : 11 occurred at PC=0x424AC980
Function=sqlQueryDirect (//or nextRow//) (compiled Java code) (or nextRow)
Library=(N/A)
Current Java thread: (//No output in this case//)
Type 3------------------------------------------------------>
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x4212E3B0
Function=(null)+0x4212E3B0
Library=java
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
- locked <0x44901b38> (a java.io.BufferedInputStream)
at com.mysql.jdbc.MysqlIO.readPacket(Unknown Source)
at com.mysql.jdbc.MysqlIO.sendCommand(Unknown Source)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(Unknown Source)
at com.mysql.jdbc.MysqlIO.sqlQuery(Unknown Source)
at com.mysql.jdbc.Connection.execSQL(Unknown Source)
- locked <0x448f92e8> (a com.mysql.jdbc.jdbc2.IO)
at com.mysql.jdbc.Connection.execSQL(Unknown Source)
at com.mysql.jdbc.Statement.executeQuery(Unknown Source)
- locked <0x448f92e8> (a com.mysql.jdbc.jdbc2.IO)
at com.mysql.jdbc.jdbc2.Statement.executeQuery(Unknown Source)
at GeneraTablaDiasCerrados.<init>(GeneraTablaDiasCerrados.java:99)
at GeneraTablaDiasCerrados.main(GeneraTablaDiasCerrados.java:425)
---------------------------------------------->
After this text, I get Dynamic libraries info.
I can't figure out what's happening. I have read in these forums that Signal 11 is about Segmentation Fault, or JVM trying to write in forbidden positions.
Later I read that JVM could crash on Pentium IV processors under certain circumstances, but isn't those issues supossed to be fixed in version 1.4.1?
The last trail I'm following is J/Connector, because in error messages type 2 and 3 are involved mysql classes. But it doesn't explain the fact that in developing machine everything runs properly.
I also consider the posibility of corrupted files in hard disk, but all of them seem to be OK (sizes in production machine matches those in developing machine).
Can anyone help me showing me another trail to follow?
Thanks to all in advance.
Note: Please, forgive my English and the length of this post.

Hi OMcGovern. Thanks for your answer.
I've a couple of theorys,
1) The second last stack trace call is for encoding.
The basic US version of the JRE only supports about
ut 8 basic encoding schemes. You could try running it
with the international version of the JRE.
( To check version : if i18n.jar is in JRE's lib
directory, it's the international version )I've checked it and I don't have the international version (not in production machine and not in developing machine). I downloaded the "Linux RPM in self-extracting file" version, (in both cases) and there is no choice for downloading any "international" version or something like this. I'll search for it in sun site. It seems to be a good guess to follow, because production machine is allocated in the USA, and developing machine is here in Spain.
2) Running java -Xint ( interpreted mode ), might
rule out any hotspot errors. It could give you more
debugging information too.
Worth a shot.I'm not running with that option.
3) It doesn't quite make sense that the last stack
trace entry is a
security call, in an application. Are you doing
ng anything strange ?
Eg. writing your own classloaders or the like ?No I'm not doing. Maybe a problem with J/Connector, but my deep doubt and what's driving me crazy is : Why is runnig all ok (I was really proud of this fact because this is my first "big" app in Java) in my developing machine and crashing in production machine?
I'll look for i18n.jar, will install it and let's see what happens..
Thanks again.

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 doing strange things

Hi folks,
So I recently upgraded my hard drive, and restored from my Time Machine backup and everything came back just as it was, which was great. However, now I am having some serious Time Machine issues. It deleted all of my old backups, which I understand happens when you restore? That is kind of annoying, but whatever, I can live with it.
However, what's really strange is that now it tries to backup, and it's telling me it needs 270 GB and I only have 163 GB available. But there is already one backup on there, so I'm not sure why it thinks it needs to start from scratch basically (at least I think that's what it's doing, as my account only has 235 GB of used space total). And what's really strange is that when I check out the space on my Time Machine hard drive, when I click "Get Info" on the backups folder, it says that it's 130 GB, but when I scan the drive with DaisyDisk, it tells me that it's over 200 GB, but not hidden or anything, and I just cannot figure out where all that extra space that is being taken up is.
So what I'm actually considering doing is just deleting the backup folder all together (although I don't know if this will get rid of just the 130 GB that it says it is, or all of it), and letting Time Machine start over. Is that a good or bad idea? Any ideas as to what the heck is going on? Any thoughts would be much appreciated.
Thanks in advance!

sbollag wrote:
now it tries to backup, and it's telling me it needs 270 GB
That means it's actually trying to back up about 225 GB (it adds about 20% for workspace), so yes, that's a full backup (less the things it skips, such as system work files, most caches and logs, trash, etc.).
And what's really strange is that when I check out the space on my Time Machine hard drive, when I click "Get Info" on the backups folder, it says that it's 130 GB, but when I scan the drive with DaisyDisk, it tells me that it's over 200 GB,
Believe Get Info. Time Machine backups have an unusual structure that cause many apps to count things more than once. See Hard Links in How Time Machine works its Magic for details.
So what I'm actually considering doing is just deleting the backup folder all together (although I don't know if this will get rid of just the 130 GB that it says it is, or all of it), and letting Time Machine start over.
Yes, but don't delete it (emptying the trash will take a very long time and may cause other troubles). Erase it with Disk Utility -- that will just take a few moments.
What's happened is, Time Machine is treating your disk as a new one (it shouldn't on Snow Leoaprd, but sometimes it does). So it deleted all but the last backup of the "old" one, trying to make room.
It sounds like your TM drive may be a bit too small. Usually, it needs at least twice the space of the data it's backing-up. See #1 in Time Machine - Frequently Asked Questions. You might want to put a larger one on your Christmas list.
Then you can use the old one for "secondary" backups. See #27 in that same link for some suggestions.

Strange behaviour on question slides with a countdown timer!

Hello Captivators,
I am facing a strange behaviour on question slides with a countdown timer. Whenever I place a countdown timer on a question slide, one of the options/answers disappear. What is going wrong here? Am I missing anythig in the settings?
I am using Captivate 8 (Trial Version).
Thank you for your support in advance.
Greetings

Sorry for the double question. However, I see that there are 10 Captivate communities and I thought I can post my question in one or some of them. Anyway, I know now that it is "Not very friendly" to do that. Sorry again!

Strange network performance when using Time Machine with APE External HD

All -
I am still looking into a performance issue with TM and and an external HD on the APE.
Strangely the network activity changes from a more or less steady 200-400kb/sec to a pulsed 1-2Mb, and than a few seconds later back to 200-300kb.
I posted a few screenshots from the Activity Monitor here: http://gallery.mac.com/erwinhogeweg#100039
The RSSI is -32, and I have a 130Mb connection with the base station, but I am not even using 1% of this BW. The overall CPU load is about 40%, so it is completely mystery (to me) why this transfer rate is slow.
Is there anyone who can give some insight in this?
There is 107GB of data on my local HD. With about 2GB/hour, it will take 2 days to back this up to a n APE Time Machine drive...
Kind Regards,
Erwin

Do NOT use a USB hub with an APE...
I had two LaCie HDs, so I figure I connect them both with a USB hub. This was not a good idea. As soon as I removed the hub the network BW was at a steady 1-2Mb/s, with an occasional peak to 5Mb/s. Still way lower than the theoretical maximum, but hey, I guess you can't have it all.
Thanks,
Erwin

Strange error trying to restore from time machine sparsebundle

I had my iMac hard drive go bad, so I replaced it, powered the unit back up and booted into the Snow Leopard install disk.
I got to the step where I'm trying to restore from my Time Machine .sparsebundle and I selected the date and time of the backup I wanted to restore. When I click Next to go the next screen (Select a Destination) the utility gets stuck "Searching for Disks," and below that a warning icon says
"This disk does not have enough space to restore your system."
This sounds scary, and as the Time Machine drive now has the sole copy of my data I'm reluctant to do anything to it.
Does anyone know what's going on?
Thanks in advance,
Dan.

Are you sure the new drive is formatted properly?
Check it via Disk Utility (you can get there from the same Utilities menu where you selected +Restore from backups).+
Select the top line of the drive (with size and make). Be sure the *Partition Map Scheme* at the bottom says +GUID Partition Table.+
Then select the next line, with the name you gave it, and be sure the Format shown towards the lower left is +Mac OS Extended (Journaled),+ unless you made it +Mac OS Extended (Case-Sensitive, journaled),+
Also see how much space it shows for Available to the right.

Strange behaviour of Time Machine.

Similar Messages

Maybe you are looking for