Trouble with Time Machine/Time Capsule try Backup instead

Trouble with Time Machine preparing to download taking hogging your system followed by errors that don't make any sense even if you look at the console logs to try to figure out. Try Backup instead.
Find the software here:
http://www.apple.com/downloads/macosx/apple/application_updates/backup312.html
It allows you to configure when to do back ups and specific data you want, and includes templates for configurations to make it easy. The only catch is you loose the Time Machine benefits of restoring an individual file easily. For me it gets around the issues w/ Time Machine hogging my system resources (Finder at 98% CPU cycles both cores) while "preparing backup", followed by strange failures that can't figure out, followed by more "preparing backup".

I was running backup instead of time machine until I saw snow leopard had time machine improvements. I'm very happy with the performance so far w/ snow leopard (OS X 10.6) time machine performance.

Similar Messages

Time Machine randomly performing full backups instead of incremental

I've been using a Time Capsule since October 2009 with my 13" MBP running Snow Leopard with no issues.
A few weeks ago, I noticed Time Machine decided to do a full 160GB backup, which then filled the Time Capsule and then deleted older backups. It then kept trying to do full backups every single time, resulting in the error 'Not enough space'.
I archived the backups from the Time Capsule, disabled Time Machine and completely erased the Time Capsule.
I set up Time Machine again and it's been working for about a week, but it's doing the same thing again - trying to do another large HD sized backup of 160GB or so (the amount of data my drive has).
I have noticed in the logs the following line
*17/02/2010 13:36:16 com.apple.backupd[946] Event store UUIDs don't match for volume: HD*
Which seems to appear as Time Machine starts to do it's full backup.
Any ideas? It's getting to the point that Time Machine is becoming unusable as I can't rely on it.

Cool, I'll give that a try.
Log files are here. I did rename my machine to remove spaces and punctuation but haven't backed up since then (only a few hours ago).
Should I resume this backup or erase the TC and start again? (I've also renamed the TC network and drive)
Feb 20 00:16:14 marty com.apple.backupd[8919]: Starting standard backup
Feb 20 00:16:14 marty com.apple.backupd[8919]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:16:22 marty com.apple.backupd[8919]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:16:32 marty com.apple.backupd[8919]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 20 00:16:32 marty com.apple.backupd[8919]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Feb 20 00:16:38 marty com.apple.backupd[8919]: No pre-backup thinning needed: 1.13 GB requested (including padding), 264.22 GB available
Feb 20 00:16:47 marty com.apple.backupd[8919]: Copied 8 files (15 KB) from volume HD.
Feb 20 00:16:47 marty com.apple.backupd[8919]: Starting post-backup thinning
Feb 20 00:16:48 marty com.apple.backupd[8919]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Marty/2010-02-18-234422: 264.22 GB now available
Feb 20 00:16:48 marty com.apple.backupd[8919]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Marty/2010-02-18-225109: 264.22 GB now available
Feb 20 00:16:48 marty com.apple.backupd[8919]: Post-back up thinning complete: 2 expired backups removed
Feb 20 00:16:48 marty com.apple.backupd[8919]: Backup completed successfully.
Feb 20 00:16:50 marty com.apple.backupd[8919]: Ejected Time Machine disk image.
Feb 20 00:16:51 marty com.apple.backupd[8919]: Ejected Time Machine network volume.
Feb 20 00:23:42 marty com.apple.backupd[9017]: Starting standard backup
Feb 20 00:23:42 marty com.apple.backupd[9017]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:23:52 marty com.apple.backupd[9017]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:24:11 marty com.apple.backupd[9017]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 20 00:24:11 marty com.apple.backupd[9017]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Feb 20 00:24:11 marty com.apple.backupd[9017]: Backup canceled.
Feb 20 00:24:14 marty com.apple.backupd[9017]: Ejected Time Machine disk image.
Feb 20 00:24:14 marty com.apple.backupd[9017]: Ejected Time Machine network volume.
Feb 20 00:25:24 marty com.apple.backupd[9017]: Starting standard backup
Feb 20 00:25:24 marty com.apple.backupd[9017]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:25:25 marty com.apple.backupd[9017]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
Feb 20 00:25:30 marty com.apple.backupd[9017]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 20 00:25:32 marty com.apple.backupd[9017]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Feb 20 00:34:44 marty com.apple.backupd[9017]: No pre-backup thinning needed: 200.38 GB requested (including padding), 264.22 GB available
Feb 20 00:35:46 marty com.apple.backupd[9017]: Copied 283 files (6.5 MB) from volume HD.
Feb 20 00:35:46 marty com.apple.backupd[9017]: Backup canceled.
Feb 20 00:35:49 marty com.apple.backupd[9017]: Ejected Time Machine disk image.
Feb 20 00:35:50 marty com.apple.backupd[9017]: Ejected Time Machine network volume.

Time machine deleted all my backups instead of the one selected

I have a one year old Macbook Pro with 16 GB of RAM, running OSX v10.9.5 (Mavericks). I use a LaCie 2TB external hard drive for my time machine backups, and I needed to delete some of the old TM backups to make space.
Following the instructions at pontini.org (http://pondini.org/TM/12.html ), I opened TM, navigated to the external HD and selected the oldest folder in backups.backupdb, right clicked it and selected 'Delete all backups in [the oldest folder's name]'. Then I went home for the weekend, and when I got in this morning, Voila! ALL files in the backups.backupdb folder were gone! Not only that, but there was nothing in the trash to restore!
Has anyone else had this wonderful experience?
Thanks,
Casey

Wow -- thanks for all the comments, folks, I must have struck a nerve! I'll try to respond to all of them here, in sequence:
John Galt: I loved your comment about "no user serviceable parts inside"! It was echoed by etresoft, too, later in the chain; sounds like good advice if this ever happens again. You mentioned that Yosemite incorporated a lot of changes to TM, but I'm not using Yosemite (have been avoiding this upgrade, as it sounds too buggy). But apparently your advice holds with Mavericks, too.
Etresoft (3:17am): very good point -- I think that's exactly what I did. What I'm still not clear on is: are the backup files themselves (ie the actual data being backed up, as opposed to hard links) stored in the backup folder that TM creates, or are they kept in a separate file or folder? It sounds like it's the former, as I had originally thought. But pondini led me to believe that, if the data WAS stored in the folder, it would not be deleted if there were any links to it in future backup folders. From what you said, I'm thinking that's probably true IF you are dealing with a backup that's INSIDE TM, but not if its a folder OUTSIDE TM. Is that right? If so, this really is a pit that's ripe for idiots like me to fall into.
Lex Schellings (3:52am): I don't think I understand your comment -- you said "All these instructions are to delete a specific file... You should never deleted a dated FOLDER". But instruction #2 says "One or more individual backups -- it's best to use Time Machine, per the green box below" -- then, in the green box, it says " Locate the backup or item you want to delete via the Timeline or "cascade" of Finder windows". Since I was trying to delete a "backup", what was I supposed to select, if not a folder?
Etresoft (4:15am): that's an interesting thought, but I don't think I used the sidebar to navigate to the backup I deleted. When I opened TM, it showed me a sequence of Finder windows with the Star Wars background, but the external hard drive in the Finder window was grayed out and inaccessible. So I checked pondini again, and it said I could get to it by right-clicking on the TM icon in the task bar (after exiting TM), selecting 'Browse other TM Disks', and selecting the one I wanted. After I did that, I could see the external hard drive in TM was not gray anymore, and I navigated to the first backup folder. Apparently, that's what took me "outside" of TM, even though I thought I was inside it. I will definitely follow up on your suggestion to go to Apple's bug report site and file a report; thanks!
Lex Schellings (4:39am; do you guys ever sleep?): I didn't hear that pondini had died -- I hope you folks weren't close to him; sounds like he was very thorough, and trying to do the right thing. He just didn't realize there were people like me out there.
I'm surprised at your comment that "the behaviour of deleting one of the TimeMachine dated folders in Finder has always been the wrong way, leading to unhappiness." That is exactly what our tech support department (which is run by Lockheed Martin; they're supposed to know what they're doing -- at least they certainly charge JPL enough for their service) said was the approved way to delete old TM backups, and in several cases in the past, it has worked for me. In any event, I didn't think I was deleting the TM dated folder through Finder -- I thought I was doing it through TM, as pondini recommended. Silly me.
Etresoft (5:24am): It's a little scary that you said "I don't know of anyone who knows Time Machine well enough to actually update it." Were you joking? I definitely agree with your (and John Galt's) advice that "I wouldn't recommend any kind of interference with Time Machine, especially with the Finder". In the future, I think I will just set up a separate partition on my external drive for TM backups, and let TM figure out how to thin itself out.
Lex Schellings (5:43am): "a magic black box" -- that's a very good take-away from this misadventure. Thanks for your advice.

Time machine not doing incremental backups - instead doing full backups

hi,
Time machine does a complete full backup, and then instead of doing incremental backups, it wants to keep doing full backups.
help.

why do you think it's doing full backups?
install TimeMachineBuddy widget and see exactly what it says. also install TimeTracker and see what exactly is being backed up every time
http://www.charlessoft.com/
but first, verify both the internal and TM drive with disk utility. verify disk, not permissions. if it reports any errors repair both drives. you'll need to boot from the snow leopard DVD to repair the main startup drive.
also, see Pondini's troubleshooting tips at the top of the TM forum.
http://discussions.apple.com/thread.jspa?threadID=2057525
Message was edited by: V.K.

Time Machine/Time Capsule backups successful, but take a long time

I purchased a 512GB Time Capsule about a year ago. Since I got it, backups have been successful, but very slow. An average backup takes about 40-50 minutes, usually for less than 20 MB transferred.
Here are a couple summaries of recent backups (see end of post for full logs):
BACKUP 1:
11 minutes to detect if pre-backup thinning was necessary
18 minutes to copy 281 MB
5 minutes to copy 5.4 MB
4 minutes to start post-backup thinning
2 minutes to delete 1 expired backup
There were no error messages.
BACKUP 2:
4 minutes to detect if pre-backup thinning was necessary
12 minutes to copy 15 MB
5 minutes to detect if pre-backup thinning was necessary
15 minutes to copy 3.8 MB
1 minutes to start post-backup thinning
2 minutes to delete 1 expired backup
This time, there were error messages about "Unable to rebuild path cache for source item. Partial source path:"
My Time Capsule is placed about 5 feet from my laptop, with no obstructions between them. I don't think it's a wireless speed issue, because I use the Time Capsule as my router, and my connection to the net is fine. Also, operations that don't require wireless connections, like detecting pre-backup thinning, also take a long time.
Does anyone have any idea what might be going wrong to cause my regular backups to take so long?
BACKUP 1:
14/09/09 2:09:47 PM /System/Library/CoreServices/backupd[18612] Starting standard backup
14/09/09 2:09:55 PM /System/Library/CoreServices/backupd[18612] Mounted network destination using URL: afp://Peter%[email protected]/turban
14/09/09 2:09:55 PM /System/Library/CoreServices/backupd[18612] Backup destination mounted at path: /Volumes/turban
14/09/09 2:10:02 PM /System/Library/CoreServices/backupd[18612] Disk image /Volumes/turban/buttercup_001ec2146608.sparsebundle mounted at: /Volumes/Backup of buttercup
14/09/09 2:10:02 PM /System/Library/CoreServices/backupd[18612] Backing up to: /Volumes/Backup of buttercup/Backups.backupdb
14/09/09 2:21:15 PM /System/Library/CoreServices/backupd[18612] No pre-backup thinning needed: 860.3 MB requested (including padding), 280.02 GB available
14/09/09 2:39:05 PM /System/Library/CoreServices/backupd[18612] Copied 12159 files (281.3 MB) from volume butternut.
14/09/09 2:39:08 PM /System/Library/CoreServices/backupd[18612] No pre-backup thinning needed: 529.5 MB requested (including padding), 280.02 GB available
14/09/09 2:44:18 PM /System/Library/CoreServices/backupd[18612] Copied 11775 files (5.4 MB) from volume butternut.
14/09/09 2:48:43 PM /System/Library/CoreServices/backupd[18612] Starting post-backup thinning
14/09/09 2:50:11 PM /System/Library/CoreServices/backupd[18612] Deleted backup /Volumes/Backup of buttercup/Backups.backupdb/buttercup/2009-09-13-132947: 280.02 GB now available
14/09/09 2:50:11 PM /System/Library/CoreServices/backupd[18612] Post-back up thinning complete: 1 expired backups removed
14/09/09 2:50:11 PM /System/Library/CoreServices/backupd[18612] Backup completed successfully.
14/09/09 2:50:18 PM /System/Library/CoreServices/backupd[18612] Ejected Time Machine disk image.
14/09/09 2:50:22 PM /System/Library/CoreServices/backupd[18612] Ejected Time Machine network volume.
BACKUP 2:
14/09/09 9:09:46 AM /System/Library/CoreServices/backupd[15833] Starting standard backup
14/09/09 9:09:54 AM /System/Library/CoreServices/backupd[15833] Mounted network destination using URL: afp://Peter%[email protected]/turban
14/09/09 9:09:54 AM /System/Library/CoreServices/backupd[15833] Backup destination mounted at path: /Volumes/turban
14/09/09 9:10:07 AM /System/Library/CoreServices/backupd[15833] Disk image /Volumes/turban/buttercup_001ec2146608.sparsebundle mounted at: /Volumes/Backup of buttercup
14/09/09 9:10:10 AM /System/Library/CoreServices/backupd[15833] Backing up to: /Volumes/Backup of buttercup/Backups.backupdb
14/09/09 9:14:06 AM /System/Library/CoreServices/backupd[15833] No pre-backup thinning needed: 542.2 MB requested (including padding), 280.02 GB available
14/09/09 9:23:27 AM /System/Library/CoreServices/backupd[15833] Unable to rebuild path cache for source item. Partial source path:
14/09/09 9:23:27 AM /System/Library/CoreServices/backupd[15833] Unable to rebuild path cache for source item. Partial source path:
14/09/09 9:24:30 AM /System/Library/CoreServices/backupd[15833] Unable to rebuild path cache for source item. Partial source path:
14/09/09 9:24:30 AM /System/Library/CoreServices/backupd[15833] Unable to rebuild path cache for source item. Partial source path:
14/09/09 9:26:00 AM /System/Library/CoreServices/backupd[15833] Copied 1223 files (15.3 MB) from volume butternut.
14/09/09 9:31:35 AM /System/Library/CoreServices/backupd[15833] No pre-backup thinning needed: 527.5 MB requested (including padding), 280.02 GB available
14/09/09 9:46:07 AM /System/Library/CoreServices/backupd[15833] Unable to rebuild path cache for source item. Partial source path:
14/09/09 9:46:07 AM /System/Library/CoreServices/backupd[15833] Unable to rebuild path cache for source item. Partial source path:
14/09/09 9:46:07 AM /System/Library/CoreServices/backupd[15833] Unable to rebuild path cache for source item. Partial source path:
14/09/09 9:46:07 AM /System/Library/CoreServices/backupd[15833] Unable to rebuild path cache for source item. Partial source path:
14/09/09 9:46:20 AM /System/Library/CoreServices/backupd[15833] Copied 11336 files (3.8 MB) from volume butternut.
14/09/09 9:47:06 AM /System/Library/CoreServices/backupd[15833] Starting post-backup thinning
14/09/09 9:49:14 AM /System/Library/CoreServices/backupd[15833] Deleted backup /Volumes/Backup of buttercup/Backups.backupdb/buttercup/2009-09-13-082428: 280.02 GB now available
14/09/09 9:49:14 AM /System/Library/CoreServices/backupd[15833] Post-back up thinning complete: 1 expired backups removed
14/09/09 9:49:15 AM /System/Library/CoreServices/backupd[15833] Backup completed successfully.
14/09/09 9:49:19 AM /System/Library/CoreServices/backupd[15833] Ejected Time Machine disk image.
14/09/09 9:49:25 AM /System/Library/CoreServices/backupd[15833] Ejected Time Machine network volume.

peterjm wrote:
I checked all of the steps in #D2 of the Troubleshooting Guide.
One other thing thing you might try, is a +*Verify Disk+* (not permissions) on your internal HD. That will not take anything like 40 hours! If it reports problems, you'll have to boot from your Install disc and use it's copy of DU to repair it. Post back if you need to do this but aren't sure how.
I think it's very fishy that Repair Disk took 40 hours -- it seems like any operation that touches the hard drive on the Time Capsule takes a long time. Maybe the hard drive is having problems? What sort of problems could a drive have that would make everything VERY slow, but still successful?
Try connecting via an Ethernet cable; see what effect that has. Everything should be faster, of course, but not wildly. Just as an example, I'm doing backups to a USB hard drive via my Airport Extreme, about 15 feet from my iMac. When I first started that way, I did a full backup via Ethernet (about 21 gb/hour), then erased it and ran again wirelessly (about 12 gb/hour).
Even 5 feet apart, you may have some sort of interference or other communications problem; if Ethernet is many times faster, then you may need to have your TC and/or wireless card examined.

Time Machine (Time Capsule) INSANELY slow on one mac (millions of days to backup)

I have been experiencing impossibly slow speeds backing up to a Time Capsule from a MacBook Pro 2.2GHz i7 running 10.7.3 (and many previous versions of the OS). As you can see in the attached image, transfer speeds are slower than if I were to manually type out the data, with estimated completion times of over 80 million days.
The Time Capsule is "joining" my existing network.
Things I have tried:
     - Connecting Time Capsule directly to router (three different ones, different cables)
     - Tried three completely different networks
     - Changing each network's channels, etc. to eliminate interference (my Web speeds are blazing, so this wouldn't be it anyway)
     - Renaming Mac (Sharing prefs) and Time Capsule with short, alphanumeric-only names
     - Restarting/reformatting Time Capsule
     - Buying a NEW Time Capsule as a last resort (turned out not to be)
I discovered that my MacBook Air, which I hadn't previously been backing up, works just fine and completed a wireless backup of several hundred GB in under 48 hours.
I am hesitant to do a wipe and install of my OS as this is my production computer for all of my video work, and I rely on many software packages and add-ons (which of course should be considered suspects).
Has anyone else experienced such insanely not-great speeds with their Time Capsule?
I am about to try backing up to a Thunderbolt drive to see if it still suffers.

I forgot to mention that one. I scoured the "All about TIME MACHINE" info, including 'D2. Backup is slow or "hung"' to no avail. I have Time Machine Buddy (widget) installed as that page recommended, and I am not seeing any messages it says to look out for. The reports are all very clean w/ no alarm bells whatsoever.

How to safely remove all backups from Time Machine/Time Capsule?

I plan to 'clean up' my Time Machine/Time capsule completely, whereby I want to make it impossible for third parties to recover all or part of these old backups.
After I have accompished this I want to start from scratch backing up my Mac.
Can you please let me have a step by step procedure to accomplish my goal.
Thank you in advance!

Muizen wrote:
Thank you WZZZ.
1) I am now specifically looking for info regarding deleting emails from backups.
It is my impression so far, that this is not possible?
Delete all backups of <home folder>/Library/Mail, per Time Machine - Frequently Asked Question #12.
And exclude that folder from future backups, per FAQ #10.
2) In addition I feel that being somewhat better in control of TM that it would be an advantage to really clean out TH completely and start a new back up, thereby systematically blooking certain matters from backing-up since there is no need for doing so.
How would I best accomplish this?
If the emails are all you're worried about, the procedure above will be fine.
But if you want to erase the TC's internal HD, see #Q5 in Using Time Machine with a Time Capsule.

Lost Backups in Time Machine - Time Capsule

Last week I decided to upgrade to Mountain Lion. I was running low on space on my harddrive so I decided I would delete some things in order to upgrade & after I installed Mountain Lion, I would put the files I needed back on using Time Machine. I have a 500GB Time Capsule & my computer backs up at least 3-5 times a week, so I thought I'd be safe.
I went ahead with the install & then went into Time Machine. When the backups showed up, I have most of my backups there, dating from 2009 to about 2011, but from 2012 up until the present there is nothing. I can see the dates on the side where it backed up, but I can't click on them like I can the others.
Does anyone know anything that would help me get these files I need back from the blackhole that seems to be my Time Machine or am I just screwed?

Manually mount the backup and search with finder..
Use the method Pondini gives here.
http://pondini.org/TM/15.html
Look through all the stuff on restore.. Q14-18..
You did not just copy the files or folders.. to TC.. ??

I tried to install a new hard drive using Snow Leopard to back up with Time Machine. When I installed the new HD I installed Leopard (10.5) on it and tried to use time machine to restore the backup I had made using 10.6. Kernel panic screen occurred.

I backed up my system using 10.6 Snow Leopard's Time Machine to an external hard drive. I did this because I purchased a new internal hard drive to upgrade my 2007 White Macbook from 80GB to 320GB. When I installed the new hard drive, I installed 10.4 (Tiger) and then 10.5 (Leopard) and once Leopard was in I tried to use Time Machine to restore my backup from 10.6 (Snow Leopard) and received a kernal panic screen directly after the bootup.
The screen had code asking for 10.6, so does this mean that the computer is searching for Snow Leopard? If so, how can I do this? Will a bootable drive with Snow Leopard on it be able to solve the issue or will I somehow need to find a way to wipe out this new hard drive?
-Steve

Booting From Snow Leopard Installer Disc
1. Insert Snow Leopard Installer Disc into the optical drive.
2. Restart the computer.
3. Immediately after the chime press and hold down the "C" key.
4. Release the key when the spinning gear below the dark gray Apple logo appears.
5. Wait for installer to finish loading.
Drive Preparation and Installation
1. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
7. After formatting is complete quit DU and return to the installer. Install Snow Leopard.

HT3275 Can some HELP, I keep getting this error with my Time Machine Back up, "The backup disk image "/Volumes/JKPN Safe/JKPN IMAC.sparsebundle" is already in use.

Can some one HELP me , I keep getting this error with my Time Machine Back up, "The backup disk image “/Volumes/JKPN Safe/JKPN IMAC.sparsebundle” is already in use.

See > http://pondini.org/TM/C12.html

My Time Machine / Time capsule gets the error: The backup disk image could not be mounted

My time machine / time capsule gets the error: The backup disk image could not be mounted.

Reboot the TC.
If you normally have multiple computers backing up, under Lion there seems to be some issues.. you need to force other users off the system. You can do that through the Airport utility, manual setup, disks, disconnect all users. Note carefully if you use Lion you probably need to download the real airport utility.. 5.6 to accomplish anything useful.

HT3275 I received this message and I'm unsure how to fix it "Time Machine couldn't complete backup to Time Capsule the backup disk image"/Volumes/The Vision Board/Alex Parry.sparsebundle" is already in use

I received this message and I'm unsure how to fix it "Time Machine couldn't complete backup to Time Capsule the backup disk image“/Volumes/The Vision Board/Alex Parry.sparsebundle” is already in use

Look at the more like this on the right column of the web page.
This is the most common error here.. we answer it 5-10times every day.
Simple method.. pull out the TC power cord .. count to 10.. plug in the TC power cord.
Look at the other references for more info.

Time Machine, Time Capsule, Keychain! I am totally lost!

Hi,
I desperately need some help here! I had my Time Machine setup correctly for a while and have been doing manual backups to Time Capsule without any issues until recently, my backup failed!
The first error I get from Time Machine is:
===
Time Machine Error
The network backup volume could not be mounted because there was a problem with the network username or password.
Open system preferences and choose time machine then re-select the Time Machine backup destination to enter the correct username and password.
===
I went to the preferences and selected change disk and re-selected my TC. I was prompted for a password and I entered the correct one. Now I get another error:
===
Keychain error -25299 occurred while created a system keycahin entry for the username "*" and URL "afp://**@***.local/**"
You can try using the keychain Access Utility to edit or repair your system keychain.
===
After searching the forums, here is what I did so far without any different outcome:
1- Did keychain first aid scan and repair (tested - same errors)
2- double checked all password files related to TC in system and login (tested - same errors)
3- Deleted all password entries related to TC & Network drive from Key Chain to recreate them automatically again (tested - same errors)
4- Reconfigured Airport and TC and changed device pass to disk pass (tested - same errors)
I should also mention that the TC mounts as a disk through the finder without any problems. Only when it is mounted in the finder TM is able to pick it up and display the blue disk icon, but still same errors and backup fails.
What do I do now?
Will I loose all my previous TM data?
Can I get TM to work again and continue where the last TM backup left off? Or do I need to backup my machine completely again?
It doesn't make any sense that an error like this could happen so easily! It kills the purpose of TM!
Any help would be appreciated ...

Thanks Bob & tomvs for your quick replies. I tried both solutions but no change. I also tried changing the TC name so new password items will be created in the keychain, no change.
If I dont get any new suggestions or solutions, I might as well try resetting my keychain! but I dont know if I will lose my passwords and security notes if I do! But I think it leaves a copy of it somewhere, right?
by the way, after I changed the TC name, all password entries were successfully created in KC, or thats at least what it seams to me.
any ideas?

Time machine does not recognize backup disk after Yosemite

I have this issue in both macs I own, a 2010 MBP, and a 2012 Mac mini. After I upgraded to yosemite, Time Machine will not find my backup disk. I have been using the same network attached storage drive for 4 years for time machine backups. I has worked fine with all the macs I've owned until now. I can see the disk in Finder, I can go to disk utility and mount the Time Machine disk, but when I go to Time Machine preferences and try to select the list, the disk is not listed there, even though is mounted.
Any ideas?
Thanks!

A third-party NAS is unsuitable for use with Time Machine, especially if it's your only backup. I know this isn't the answer you want. I know Time Machine accepted the NAS as a backup destination. I know that the manufacturer says the device will work with Time Machine, and I also know that it usually seems to work. Except when you try to restore, and find that you can't.
Apple has published a specification for network devices that work with Time Machine. None of the third-party NAS vendors, as far as I know, meets that specification. They all use the incomplete, obsolete Netatalk implementation of Apple Filing Protocol.
If you want network backup, use as the destination either an Apple Time Capsule or an external storage device connected to another Mac or to an 802.11ac AirPort base station. Only the 802.11ac base stations support Time Machine, not any older model.
Otherwise, don't use Time Machine at all. There are other ways to back up, though none of them is anywhere near as efficient or as well integrated with OS X. I don't have a specific recommendation.
If you're determined to keep using the NAS with Time Machine, your only recourse for any problems that result is to the manufacturer (which will blame Apple, or you, or anyone but itself.)

Time Machine doesn't make backups

Hi,
I have problems with Time Machine. I deleted by error the backup file in Time Capsule, but now Time Machine doesn't create a new one, simply it doesn't work. External disks are recognized (Time Capsule or USB disk) but it doesn't make backups, only appears the "preparing" for one or two seconds and then nothing. It's the same if I try to make backups on a external USB disk.
I can not enter to Time Machine to see the backups.
Looking at "Console" for the last logs there many crash reported, for example:
18/02/09 11:59:26 /System/Library/CoreServices/backupd[3053] Backup requested by user
18/02/09 11:59:26 /System/Library/CoreServices/backupd[3053] Starting standard backup
18/02/09 11:59:27 ReportCrash[3054] Formulating crash report for process backupd[3053]
18/02/09 11:59:28 com.apple.launchd[1] (com.apple.backupd[3053]) Exited abnormally: Trace/BPT trap
18/02/09 11:59:28 ReportCrash[3054] Saved crashreport to /Library/Logs/CrashReporter/backupd2009-02-18-115926GK.crash using uid: 0 gid: 0, euid: 0 egid: 0
Any one with a similar problem???
Is it possible to reset Time Machine in order to restart the backups?
I bought Time Capsule and I can't use Time Machine!!!!
Thanks.

magali mistral wrote:
Hello!
Thanks for your message. The Time Machine Buddy widget was helpful. Although I couldn't mark the text, copy and insert it here.
You should be able to highlight them by dragging your mouse over them, then cmd-C to copy to the clipboard, then cmd-V to copy it here.
Event store UUID don't match for Volume: Macintosh HD
This means TM isn't sure whether the last changes to your internal HD got logged to OSX's File System Event Store, a log of all changes that TM can normally use to see what needs to be backed-up. Most commonly caused by an abnormal shutdown.
Node requires deep traversal:/
Reason: kFSEDBE even FlagMustScanSubDrs /kFSEDBE vent Flag Reason Deep Backup/
Since it can't trust the Event Store, this means it has to examine every file and folder on your HD. Quite a lengthy procedure, of course.
Then it said - I didn't copy that - something like "thinning out" isn't necessary because there was still 368 GB or so space left - 7 GB were backed up - but it did "thin out" some outdated file afterall, whatever that is - hope it didn't delete something I wanted to keep.
All normal. TM automatically deletes it's hourly backups after 24 hours, except the first of the day, which is called a Daily backup. That is kept for a month, when a similar process converts the first of a week into a Weekly backup, and deletes the others.
Only when the disk is near full (TM does need some workspace) will you see deletion of one or more of the oldest weeklies, instead of the first message.
Then the next problem started. It wasn't possible to eject the external drive. I waited for quite some time but each time tried to eject it, a window opened saying that it was still in use and could not be ejected. Although it had defenitely finished doing the backup and the next one was to be done about half an hour later.
Is there anything else on your external drive, besides TM backups? Could you have been looking at it via the Finder, when you tried to eject it?
Try this: de-select the drive (chose the "none" icon) in TM's preferences, then quit System Preferences. Then go back and re-select it. Sometimes this resets TM's lock on the drive.
If not, and it happens again, try turning TM off, then ejecting the TM drive. You shouldn't have to do this -- TM is supposed to let you eject it, then automatically do another backup whenever you re-connect it.
Now that you have a good full backup, just keep an eye on it. Your incremental backups should be very, very quick under normal circumstances.
There are a few things that may cause long backups, such as an abnormal shutdown, certain hardware repairs, not letting TM back up for several days (seems to be about 10, some say), and the use of certain apps. File Vault, Entourage, vmWare, running Windoze are a few. If you do see long backups, post the messages here in a new thread.

Trouble with Time Machine/Time Capsule try Backup instead

Similar Messages

Maybe you are looking for