Time Machine - Last Backup 4/5/2010

Hi,
TM has been working flawlessly, but just noticed recently that the icon for TM in the menu bar is spinning constantly, and the last backup was over two months ago. I back up to an external Maxtor 1TB drive, and there is about 500mb of free space left on that disk.
I manually started a back up about an hour ago today, and when i click on the spinning TM clock icon in the menu bar it says "backing up: 56 bytes of 13.37 gb".
Any ideas what is going on?

dnonnema wrote:
OK, repaired the internal disk. Re-verified the external and internal disks one more time. Once I start the TM backup process it scans about 700k items then starts the backup. Now, rather than getting stuck at about 35k, it is getting stuck at 103.4mb.
Leave it alone for a while. Sometimes when recovering from problems, especially a failed or cancelled backup, it will appear to stall.
Here are the results of the TM Buddy app while the backup is in process (line 3 looks to be problematic):
Event store UUIDs don't match for volume: Main Disk Drive
Node requires deep traversal:/ reason:must scan subdirs|new event db|
Those are normal after booting from your Install disc and repairing the internal HD. See #A6 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum).
No pre-backup thinning needed: 15.38 GB requested (including padding), 397.80 GB available
Although it says it's going to back up about 12.5 GB (plus 20% for workspace, the "padding" in the message), it may seem to be proceeding at a snail's pace, then suddenly finish after backing-up much less than the 12.5 GB. This appears to be part of recovering the partial backup.
Go to dinner . . .

Similar Messages

Time Machine, last backup = none?!?

Hi,
Suddenly Time Machine wont recognize my backups anymore.... Yesterday I renamed the TM USB disk from "unknown" to "Time Machine".
When I wanted to make a new backup, Time Machine told me the latest backup was "None" so I quickly renamed the disk back to "unknown".
But no TM still wont display my last backup and now TM is making a full backup of ALL my files?!? (about 400GB)...
How can I fix this please?
Thank you!

Unfortunately you discovered that you cannot just simply "rename" your Time Machine volume without it "reformatting" the hard drive itself and erasing all the previous files. Which is what is has done. I am afraid at this point you must start from scratch acquring backup files to save for the future. The old backups are gone.
Hope this helps

Time machine - Last backup failed - how i fixed it...

I woke up this morning to see that time machine had failed to backup. It has been a couple of days since installing 10.5.3, so I'm not sure if it's related to the update or if it's just the way that time machine works.
I ran diskwarrior, www.alsoft.com
and it came back with more file structure errors than i have ever seen on a hard drive! instead of tell you, here is an picture.
needless to say, once i replaced the directory time machine began working again, and it's way faster than it ever has been before.

I promise this thread is not an ad for diskwarrior
it has just saved my *** so many times that i wanted to share the information. apple disk utility does not do as good of a job at repairing HFS+.
here is a link to get latest version (4.1 for 10.5)...
http://thepiratebay.org/tor/4000433/DiskWarrior4.1___serial_for_Leopard10.5

Where did this backup window come from on my desktop. I have always used time machine to backup to an external disc and within the last 2 weeks, this backup window keeps appearing. Where did it come from? Thanks for any help

where did this backup window come from on my desktop. It specifies personal data & settings and tells me when the next backup is scheduled [which I never set up]. I have always used time machine to backup to an external disc and within the last 2 weeks, this backup window keeps appearing. Where did it come from? Thanks for any help

To check your S.M.A.R.T status open disk utility and click on your drive and then click on the info icon.

Cannot open time machine; message on screen: time machine in backup. I want to find last 12 mos. of pictures.

cannot open application to time machine: Message on screen: time machine in backup.
Purpose to get into time machine; is to pickup lost photos

northernresort wrote:
I workedwith apple support on the phone it believe the backup is corrupt.
Yup, sure sounds like it.
It does have a .sparsebundle for the machine that is backup up. There is only 52G free on the 1T time capsule, so it seems that the data is there,
That's good, obviously. Often it won't mount at all, and you're in a very large pickle.
I'm not seeing nor beleive I'm having a hardware issue with the time capsule.
Probably not.
I'm wondering if I have some sort of version issue between 10.7.x that the Time machine on the time capsule was created with and 10.8.4
No, at least not that's been reported. A sparsebundle is a sparsebundle, as far as we can tell.
I don't use hdiutil or fsck, so bear with me. Drag the sparsebundle into Disk Utility's sidebar and try Repair Disk on it. See what messages it shows. (They may not appear in the window; click the Log icon or select Window > Show Log from the menubar.)
Do you have a copy of DiskWarrior? It can operate on a sparsebundle, and sometimes can fix things Disk Utility (and hdiutil or fsck) can't.
I haven't found any good way to parse out/copy files from a sparse bundle
If you double-click it, does the disk image (named "Time Machine Backups") mount (should appear on your Desktop and/or Finder sidebar)? If it does, can you open it via the Finder? If so, you'll find the usual Backups.backupdb folder inside, with one folder named for your Mac, and inside that all the date-stamped backup folders, each with one folder per drive that was backed-up, and inside that the full folder structure.
If so, you can probably drag & drop, but depending on what kind of damage there is, and where, that may not work well, if at all.
Best, of course, is if you can repair it and just do a full restore.

Can I use the new Time Capsule to backup my mid 2010 Macbook Pro? Also can I want to free up my hard disk, can I save my photos and files on the time capsule and later access through wifi?

Can I use the new Time Capsule to backup my mid 2010 Macbook Pro? Also can I want to free up my hard disk, can I save my photos and files on the time capsule and later access through wifi?

Can I use the new Time Capsule to backup my mid 2010 Macbook Pro?
Yes, if you are asking about using Time Machine to backup the Mac.
Also can I want to free up my hard disk, can I save my photos and files on the time capsule and later access through wifi?
You are not thinking of deleting the photos and files on your Mac, are you? If you do this, you will have no backups for those files.
Another concern is that Time Machine backs up the changes on your Mac. At some point, Time Machine will automatically delete the photos and files from the Time Capsule.....you just don't know when this might occur.
In other words, only delete files from your Mac that you can afford to lose.

Does Time Machine bundle backup sets when it deletes a month's daily sets?

I'm asking this question to find out if I can delete the all but the last week in a month, each month, in order to extend the useful capacity of my backup drive.
In some backup systems, a periodic "bundle" is made when previous sets are deleted, so for instance, the last backup of the month has the cumulative hourly changes of that month. In this way, transient files which appear and disappear within the month are retained in the monthly backup.
Is this true of Time Machine? Exactly what does Time Machine do? Does it simply wipe out the daily sets and chose the last one to be the "weekly backup?" Or something more sophisticated and useful?
Thanks for any insight!

I've devised a little experiment to discover Time Machine's behavior in this regard:
On my Time Machine's backup schedule, August 27 corresponds with the end of a week. So, on August 26 at 9:15AM, I created the following [folder]/file structure:
[Time Machine Test -Transient Roll-up]
   [Time Machine Test - 1. Hourly Transience
      A one hour lifetime file.rtf
   [Time Machine Test - 2. Daily Transience
      A one day lifetime file.rtf
   [Time Machine Test - 3. Weekly Transience
      A one week lifetime file.rtf
At 10:10AM of that day I removed
[Time Machine Test - 1. Hourly Transience
      A one hour lifetime file.rtf
At 10:10 the next day, August 27, I removed
   [Time Machine Test - 2. Daily Transience
      A one day lifetime file.rtf
On August 28 at 10:30AM, acheck today of the earliest backup of this structure reveals only the following:
[Time Machine Test -Transient Roll-up]
   [Time Machine Test - 3. Weekly Transience
      A one week lifetime file.rtf
I draw the conclusion that transient files within a time period are not subject to a "roll-up" mechanism that displays all changes after out-of-date files are deleted by Time Machine. Thus, for instance, any file that appeared and disappears during an hour will be lost in Time Machine's daily history. Similarly, files that only persist for a day will be lost in the weekly history. And, presumably, if one wanted to choose a week which represented an accumulation of transient changes during the month it would be impossible to do so.
Even so, if one wants to manage only one backup volume, rather than accumulating a stack of them over the years, one might well think about selectively deleting all but one week per month in the earliest backups available, as the projected remaining time approaches less than a few weeks. BackupLoupe's Statistics gives an estimate of remaining time left for backups on a volume, and I would suggest using that as a forecast, unless others have experience to the contrary.
Hope this is useful. It certainly is to me.

Trouble getting time machine to backup latest numbers file.

I'm able to use Time Machine to backup my macbook wirelessly to an external hard drive attached to my iMac. However, I recently noticed that I am failing to back up the latest version of a numbers file.
Has anyone noticed any incomplete or outdated files - that shouldn't be - in their number file back ups?

Well, Time Machine unfortunately is bugged beyond use for some people. It is nearly impossible to tell if TM will work every single time until Apple will take a look at their programming and fix the darn thing.
Anyways, back to the point. The problem with updated files is that TM will look for new things that are indexed as new, and by indexed as new as in the Spotlight regards the file as updated since last backup. I don't really know if this would work, but you could give it a try.
Try this:
1) Duplicate the file into the same folder with a different name
ex. filename.doc, and make a new file called filename_1.doc
2) Make sure that this file is in the same folder as the other file.
3) Back up
I think that would make Spotlight tell TM to backup the updated documents.

Time Machine hourly backup seems a tad large

Hi all
Occasionally, my hourly Time Machine incremental backups to my Time Capsule seem a tad large. One hour the backup is a sensible size, then an hour later, when I've been doing very little on my machine, the backup is massive (as in, several gigabytes).
Not only that, but the backup seems to grow in size as its happening. the pictures below should help illustrate.
The backup is listed as being 719MB, only an hour after a more modest backup. Time Machine seems to be claiming that is has transferred all of the required backup:
!http://img6.imageshack.us/img6/4988/picture2gih.png!
But then, only two minutes later, see how the situation has changed:
!http://img5.imageshack.us/img5/3739/picture3m.png!
And the situation continues:
!http://img87.imageshack.us/img87/9339/picture5.png!
Any ideas? This issue happens intermittently (although it is happening now... that last image was taken a few minutes ago and the backup was still going - up to 3.1GB - before I told it to stop).
I'm not certain if Time Machine is actually transferring this amount of data to the Time Capsule or not.
Cheers.

Hi,
I had the same problem today as well. The last backup was done this morning at 2 a.m. When I turned my PowerBook G4 on again this afternoon, the backup size continually grew, just like on your machine, Rob. I aborted the backup a couple of times, deleted the inProgress file, but it always got bigger and bigger. After downloading Time Machine Buddy and Time Tracker, I just let Time Machnine "do it's thing". Luckily, I had enough free space on my WD MyBook 500 GB I use for the backups, because it stopped only at 24.8 GBs, after initially displaying 61,3 MB in the menu bar, and requesting 1.05 GB according to Time Machine Buddy.
Time Machine Buddy protocol:
Starting standard backup
Backing up to: /Volumes/My Book/Backups.backupdb
No pre-backup thinning needed: 1.05 GB requested (including padding), 32.74 GB available
Copied 139261 files (24.8 GB) from volume Macintosh HD.
No pre-backup thinning needed: 1.16 GB requested (including padding), 7.36 GB available
Copied 7042 files (2.0 MB) from volume Macintosh HD.
Starting post-backup thinning
Deleted backup /Volumes/My Book/Backups.backupdb/Claas Olthoffs PowerBook/2009-03-05-202501: 7.36 GB now available
Deleted backup /Volumes/My Book/Backups.backupdb/Claas Olthoffs PowerBook/2009-03-05-192342: 7.37 GB now available
Deleted backup /Volumes/My Book/Backups.backupdb/Claas Olthoffs PowerBook/2009-03-05-123736: 7.37 GB now available
Deleted backup /Volumes/My Book/Backups.backupdb/Claas Olthoffs PowerBook/2009-03-05-113526: 7.38 GB now available
Post-back up thinning complete: 4 expired backups removed
Backup completed successfully.
So I took a look at Time Tracker to see what was backed up. I was suprised to see, that the biggest chunk was my Macintosh HD/Library/Application Support folder. This folder is 23,9 GB in size, mainly because it contains Final Cut Studio media and templates. Time Machine backed it up completey. This seems weired, because none of the files I looked at in this folder were changed during the last couple of months, if not the last year, since I installed them. I don't know why Time Machine would backup all of those unchanged files.
For the sake of completeness, the external drives contains other, non-backup, files as well.
I hope this gives you some more information to work with Pondini.
Greetings,
Claas

Time Machine - Preparing backup - It's endless

My C2D Mac Mini is hanging on Time Machine - Preparing Backup for the second time since "Upgrading" to 10.5.2
I had to re-format my backup disk last time and start all the backups again.
Here is an extract from the console log:
29/04/2008 23:50:13 /System/Library/CoreServices/backupd[1094] Starting standard backup
29/04/2008 23:50:13 /System/Library/CoreServices/backupd[1094] Backing up to: /Volumes/LaCie Disk/Backups.backupdb
29/04/2008 23:50:15 /System/Library/CoreServices/backupd[1094] Event store UUIDs don't match for volume: Macintosh HD
29/04/2008 23:50:15 /System/Library/CoreServices/backupd[1094] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
Does anyone recognise this? I'm a Mac novice so I don't understand what it all means. I hope I don't have to reformat and start again as I was converted to Mac from PC on the advice that "A Mac Works!"
My backup drive is a 500GB Lacie Mini if that is of any relevance. Spotlight is told not to index the drive and also the Lacie drive is told not to back itself up.
Can anyone help as it's driving me nuts!

Are Lacie really that bad? I thought that the main reason they are mentioned in these forums is that Lacie are one of the only brands of external storage that apple actively promote through their own web stores so there a good chance that quite a few Mac users will buy one. Anyway I can't afford to buy another Hard Drive at the moment and the lacie works perfectly apart from Time Machine.
The problem seems to be with Mac OS the more I delve into these forums and more importantly the 10.5.2. update which is where Time Machine appears to be providing users with a lot of troubles.
The Apple support self service on the website is far from comprehensive as I guess they want you to purchase Apple Care for ongoing support after the 90 days initial period but come on apple give us a break and sort it out or provide a support email address for specific problems!

Time machine fails backup

Can anyone advise me?
I use Time Machine to backup. All has been well the backups were flawless until recently when I decided that I needed to encrypt my sensitive work and personal files placing them into an encrypted Apple Disk Image on my hard disk. Ever since then at some stage Time Machine had decided that there is insufficient disk space and the backup fails.
When it first began to fail I increased the backup disk space and began a fresh start backup.
The backup disk is now 1 TB and the total amount on my hard disk to be backed up to backup is 183 gb which includes the disk image which is 40 gb.
The only change has been the creation of the disk image otherwise everything else is the same. Would it be better to have a number of disk image files and spread the encrypted material across smaller dmgs?

Thank you for your response which is very helpful. I have changed the dmg to a sparse bundle and Time Machine appears to be handling the backup better.
Initially I was confused about the difference between a sparse image and a sparse bundle but read in https://discussions.apple.com/thread/2001162?start=0&tstart=0 what the difference is and see that the sparse bundle appears to have been developed by Apple for exactly my kind of problem.
You say that "… be aware that disk image files are not backed up at all while the image is mounted."
I do not wish to disagree but when I was backing up the vanilla dmg and also last night backing the sparse bundle dmg the back up has worked and did work on the mounted disk. In my case the disc is always mounted as it contains the bulk of the files I work on. Perhaps I have misunderstood what you were saying.
Thank you again for your response.

Time Machine same backup size every time

Anyone have any idea why Time Machine would backup the same amount every time? Every hour mine backs up 1.8 GB, unless I've added more than that to my hd.
I only back up the internal drive on my macbook to a 500 GB Time Capsule via wifi (802.11n only, 5GHz). Not that I figured it would make a difference, but it still does it if backed up via ethernet.
I've also noticed that as soon as it completes the backup, it will backup all over again - and not because an hour has passed. I'm not sure if it does this every time (but I think i does), or if it does it more than twice when it happens.
Thanks in advance!

See if the following might give you some ideas as to why...
*_Incremental Backups Seem Too Large!_*
Open the Time Machine Prefs on the Mac in question. How much space does it report you have "Available"? When a backup is initiated how much space does it report you need?
Now, consider the following, it might give you some ideas:
Time Machine performs backups at the file level. If a single bit in a large file is changed, the WHOLE file is backed up again. This is a problem for programs that save data to monolithic virtual disk files that are modified frequently. These include Parallels, VMware Fusion, Aperture vaults, or the databases that Entourage and Thunderbird create. These should be excluded from backup using the Time Machine Preference Exclusion list. You will, however, need to backup these files manually to another external disk.
If you do a lot of movie editing, unless these files are excluded, expect Time Machine to treat revised versions of a single movie as entirely new files.
If you frequently download software or video files that you only expect to keep for a short time, consider excluding the folder these are stored in from Time Machine backups.
If you have recently created a new disk image or burned a DVD, Time Machine will target these files for backup unless they are deleted or excluded from backup.
*Events-Based Backups*
Time Machine does not compare file-for-file to see if changes have been made. If it had to rescan every file on your drive before each backup, it would not be able to perform backups as often as it does. Rather, it relies on a process called FSEvents. This is a system log that records changes that occur with all the directories on your Mac. Moving / copying / deleting / & saving files and folders creates events that are recorded in this log. At the beginning of each backup, Time Machine simply looks at this log to determine what has changed since the last backup. [http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/14]
Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your directories. Every one of these changes is recorded by the OS as an event. Time Machine will backup every file that has an event associated with it since the installation.
Files or folders that are simply moved or renamed are counted as NEW files or folders. If you rename any file or folder, Time Machine will back up the ENTIRE file or folder again no matter how big or small it is.
George Schreyer describes this behavior: “If you should want to do some massive rearrangement of your disk, Time Machine will interpret the rearranged files as new files and back them up again in their new locations. Just renaming a folder will cause this to happen. This is OK if you've got lots of room on your backup disk. Eventually, Time Machine will thin those backups and the space consumed will be recovered. However, if you really want recover the space in the backup volume immediately, you can. To do this, bring a Finder window to the front and then click the Time Machine icon on the dock. This will activate the Time Machine user interface. Navigate back in time to where the old stuff exists and select it. Then pull down the "action" menu (the gear thing) and select "delete all backups" and the older stuff vanishes.” (http://www.girr.org/mac_stuff/backups.html)
*TechTool Pro Directory Protection*
This disk utility feature creates backup copies of your system directories. Obviously these directories are changing all the time. So, depending on how it is configured, these backup files will be changing as well which is interpreted by Time Machine as new data to backup. Excluding the folder these backups are stored in will eliminate this effect.
*Backups WAY Too Large*
If an initial full backup or a subsequent incremental backup is tens or hundreds of Gigs larger than expected, check to see that all unwanted external hard disks are still excluded from Time Machine backups. Time Machine will attempt to backup any hard disk attached to your Mac, including secondary internal drives, that have not been added to Time Machines Exclusion list.
This includes the Time Machine backup drive ITSELF. Normally, Time Machine is set to exclude its’ own backup disk by default. But on rare occasions it can forget. When your backup begins, Time Machine mounts the backup on your desktop. (For Time Capsule/AirDisk users it appears as a white drive icon labeled something like “Backup of (your computer)”.) If, while it is mounted, it does not show up in the Time Machine Preferences “Do not back up” list, then Time Machine will attempt to back ITSELF up. If it is not listed while the drive is mounted, then you need to add it to the list.
*Recovering Backup Space*
If you have discovered that large unwanted files have been backed up, you can use the Time Machine “time travel” interface to recovered some of that space.
Launch Time Machine from the Dock icon.
Initially, you are presented with a window that represents “Today (Now)”. DO NOT make changes to file while you see “Today (Now)” at the bottom of the screen.
Click on the window just behind “Today (Now)”. This represents the last successful backup and should display the date and time of this backup at the bottom of the screen.
Now, navigate to where the unwanted file resides.
Highlight the file and click the Actions menu (Gear icon) from the toolbar.
Select “Delete all backups of <this file>”.
*FileVault / Boot Camp / iDisk Syncing*
Note: Leopard has changed the way it deals with FileVault disk images, so it is not necessary to exclude your Home folder if you have FileVault activated. Additionally, Time Machine ignores Boot Camp partitions as the manner in which they are formatted is incompatible. Finally, if you have your iDisk Synced to your desktop, it is not necessary to exclude the disk image file it creates as that has been changed to a sparsebundle as well in Leopard.
Let us know if this resolved your issue.
Cheers!

Time Machine Slow Backup

I use Time Machine to backup to a G-Technologies 4TB external HD. The backup is extremely slow, many times saying it will take 69,000 days to back up. I have almost a TB to backup. The G-Technology HD will go off line. I'm not sure if this is a HD problem or Time Machine problem. My iMac is a IntelMac with 2.4Ghz Core 2 Duo, 4GB of Ram, OSX 10.8.2. Any thoughts?

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

Time Machine nuking backups, starting from scratch!

ok, i just received this warning:
and now i't doing a backup that is slated to take more than "several hours."
is this common? how often can i expect this?

Hello,
Should you click “Start New Backup”? Not yet! If you see the dialog above, your existing Time Machine backup is corrupt, and you might not be able to recover data from it. But you can save a copy of the corrupt bundle and, perhaps, extract some data from it if needed.
Ask yourself if Time Machine has saved data you might need before deciding what to do next:
If you are sure you won’t need anything backed up before today, click “Start New Backup” and let Time Machine do its thing.
Otherwise, click “Back Up Later” and save a copy before letting Time Machine start a new backup. Just look for a file called “computername.sparsebundle” (for network backups) or “Backups.backupdb” (for local ones) and create a copy with a different name. You can open sparsebundle files with DiskImageMounter and browse them like any other disk. More information is available here.
There you go. If you click “Start New Backup” when you see this dialog box, Time Machine will erase all of your old backup data and start a new bundle. It won’t be corrupt, but it will be empty.
Note that you can manually initiate a Time Machine backup integrity check by option-clicking the “Time Machine” icon in the menu bar and selecting “Verify Backups.”
http://blog.fosketts.net/2010/08/11/time-machine-completed-verification-backups- improve-reliability-time-machine-create-backup/
According to This Time Machine resource “This appears only on Snow Leopard, and started with the Time Capsule Backup Update 1.0 in mid-May of 2010. It also seems to have been included in the 10.6.3 v1.1 update and 10.6.4.”
So, what can you do about it? Grin and bear it, it seems, until Apple fixes it.
One thing you can do to make the backup take less time is to connect your machine to your Time Capsule or other backup drive via Ethernet for the duration of the initial backup.
http://www.theinternetpatrol.com/the-dreaded-time-machine-has-completed-a-verifi cation-of-your-backups-to-improve-reliability-time-machine-must-create-a-new-bac kup-for-you-message-and-why-you-are-seeing-it/
Time Machine: About "Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you."...
http://support.apple.com/kb/HT4076

Time Machine deleting backups?

When Time Machine is finishing taking a backup of my Mac, why does it delete something, maybe old backups, even if I have nearly 200GB free space on my external disk?

And now it's stuck with 18,9MB and canceled
6.4.2014 13.36.37,783 com.apple.backupd[1294]: Starting automatic backup
6.4.2014 13.36.37,895 com.apple.backupd[1294]: Attempting to mount network destination URL: afp://;AUTH=No%20User%20Authent@WDMyCloud._afpovertcp._tcp.local/TimeMachineBac kup
6.4.2014 13.37.06,076 com.apple.backupd[1294]: Mounted network destination at mount point: /Volumes/TimeMachineBackup using URL: afp://;AUTH=No%20User%20Authent@WDMyCloud._afpovertcp._tcp.local/TimeMachineBac kup
6.4.2014 13.37.06,099 mds[79]: (Normal) Volume: volume:0x7fd3e386f000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/TimeMachineBackup
6.4.2014 13.41.52,245 com.apple.backupd[1294]: Disk image /Volumes/TimeMachineBackup/Samu - MacBook Air.sparsebundle mounted at: /Volumes/Time Machine -varmuuskopiot
6.4.2014 13.42.13,441 com.apple.backupd[1294]: Backing up to /dev/disk2s2: /Volumes/Time Machine -varmuuskopiot/Backups.backupdb
6.4.2014 13.47.45,821 com.apple.backupd[1294]: Will copy (2,6 GB) from Macintosh HD
6.4.2014 13.47.45,845 com.apple.backupd[1294]: Found 1010 files (2,72 GB) needing backup
6.4.2014 13.47.46,251 com.apple.backupd[1294]: 3,51 GB required (including padding), 183,9 GB available
6.4.2014 13.52.22,072 com.apple.prefs.backup.remoteservice[1380]: assertion failed: 13C64: liblaunch.dylib + 25164 [38D1AB2C-A476-385F-8EA8-7AB604CA1F89]: 0x25
6.4.2014 13.52.22,090 com.apple.prefs.backup.remoteservice[1380]: assertion failed: 13C64: liblaunch.dylib + 25164 [38D1AB2C-A476-385F-8EA8-7AB604CA1F89]: 0x25
6.4.2014 13.52.22,332 com.apple.prefs.backup.remoteservice[1380]: Bogus event received by listener connection:
<error: 0x10aae4b50> { count = 1, contents =
"XPCErrorDescription" => <string: 0x10aae4e60> { length = 18, contents = "Connection invalid" }
6.4.2014 13.56.31,228 com.apple.backupd[1294]: Cancellation timed out - exiting
6.4.2014 13.56.31,245 com.apple.backupd-helper[869]: XPC error for connection com.apple.backupd.xpc: Connection interrupted
6.4.2014 13.56.31,245 com.apple.backupd-helper[869]: Not starting scheduled Time Machine backup: Failed to send message to backupd
And yeah, that deleting takes hours (about 10 last time).

Time Machine - Last Backup 4/5/2010

Similar Messages

Maybe you are looking for