Time Machine - Time Capsule hangs when finishing

Recently upgraded to Leopard and added a 500 GB TC. After many hours the initial backup finally finished, but now whenever it tries to do the hourly backup, it hangs at the "finishing backup" stage. No error message, just stays in that state until I finally tell it to stop. Any clues how I get it to finish its backup?

Looks like the situation resolved itself. I just needed to let the first "hourly" backup run as long as it needed to (a couple of hours). Since then, the hourly backups have run just fine, and only taken a couple of minutes.

Similar Messages

Time Capsule error when interrupting a regular hourly backup

Okay... So it's supposedly common knowledge that if you interrupt an hourly Time Capsule backup (not the big initial one) by putting your Macbook to sleep, the next time you wake your computer up Time Machine is supposed to just pick up where it left off. Right?
Not for me. I got Time Capsule right when it was released and it worked like a charm for a whole entire month... Until one day I made the mistake of interrupting one of its backups. When I got back to my computer I got an error saying the backup could not be completed. I thought it was no big deal until I actually tried to start a backup again. First it stayed on "Preparing" for a long time... Then a similar error message. I tried again and again and got nothing but error messages. Nothing I tried worked.
I decided to erase the Time Capsule disk and start over, essentially losing a month's worth of backups. Once again it worked for a few days until once again I put my Mac to sleep while it was doing a regular backup. Once again, coming back to my computer resulted in an error message. Once again it couldn't recover no matter what I did. I decided to try again from scratch, erased the drive, did the big backup.
Today, after three days of it working just fine, I had to leave my house in the middle of a backup. I paused for a moment wondering if I should do it, but then thought, what the ****, you're SUPPOSED to be able to interrupt it.
Um, no. Error message again. Except today I decided to run Disk Utility on it, which did work in reviving its backup abilities... HOWEVER something very strange happened. Spotlight started indexing the backup disk image-- something I'm pretty sure is not supposed to happen. It insisted on doing this every time I mounted the disk image, and only when it was finished indexing would it agree to dismount itself after backing up (like it's supposed to). Aside from that, Time Machine no longer asks for my password when I choose the Time Capsule disk... It just chooses it. It also doesn't alert me when I delete a file stored inside the Time Capsule disk (to tell me it will be permanently deleted) but instead sends it to the trash. And when recovering a file from Time Machine, the disk image doesn't dismount itself once it's done-- I have to do it manually.
In short, it's not acting normal, as far as I can tell.
So my question is twofold:
1) why the **** can't I interrupt the backup without getting an error? It's not supposed to work this way. Does this work for anyone else?
2) What the **** happened to the disk image now that I've got it to work again? It backs up fine and everything but it's acting weird.
Thanks... Hope someone has any clue what this all means!

I have a very similar issue. Spotlight is now indexing the backup volume on Time Capsule, and it is taking forever.
Nobody else using Time Machine / Time Capsule here? I can't believe that.
-Erik

Time Capsule hangs at end of full backup, Disk Utility "not responding"

I'm running a Mid 2011 iMac 27" with OSX 10.8.4 and using a WiFi connected 3TB Time Capsule (4th Gen).
I've noticed that the Time Capsule seems to get stuck at the end of a full back-up (let's say 260 GB of 260 GB) and won't end, even after hours of being left alone.
When I mount the Time Capsule Sparse Disk Image Bundle and then try to run Disk Utility, Disk Utility is shown as "Gathering Information," but the Finder and Activity Monitor list Disk Utility as "not responding." (No disk information is shown in Disk Utility.) This happens both when I connect via WiFi to the Time Capsule and when I connect directly using an Ethernet cable. If I don't mount the Sparse Disk Image Bundle, Disk Utility works fine, immediately showing my iMac's Hard Drive, so it only happens when the Time Capsule Sparse Disk Image Bundle is mounted.
1. Is Disk Utility truly "not responding" or is it just taking forever to load because of the 3TB hard drive?
2. If it truly isn't responding, what can I do to see if the TC needs to be "repaired"?
3. What's going on with my TC that it hangs up at the end of a full backup?
Thanks.

thefliss wrote:
I see an occasional deep node traversal, but sounds like that can be normal.
Not normal, exactly, but TM's way of handling a problem. See below.
Aug 17 21:35:50 Erics-iMac.local fseventsd[48]: event logs in /Volumes/Time Machine Backups 1/.fseventsd out of sync with volume. destroying old logs. (86990 10 86991)
Aug 17 21:35:50 Erics-iMac.local fseventsd[48]: log dir: /Volumes/Time Machine Backups 1/.fseventsd getting new uuid:
Something went wrong with or on the TM drive (Time Capsule in your case), such as a power failure or abnormal disconnection, where OSX was unable to "close it out" properly, so is unsure if all the changes are in the File System Event Store. If you're not familiar with the Event Store, see the blue box in How Time Machine works its Magic for details (it's talking about the one on your internal HD, but OSX keeps one on every drive/partition and disk image, including your TC backups.)
Aug 17 21:36:07 Erics-iMac.local com.apple.backupd[1728]: Event store UUIDs don't match for volume: Macintosh HD
That's one of the causes of a deep traversal. The UUID (Universally Unique IDentifier, the long string of numbers and letters) for the Event Store on your internal HD doesn't match the one in TM's records from the previous backup, so it must do a deep traversal instead, comparing everything on your Mac to the latest (completed) backup.
Aug 17 21:42:09 Erics-iMac.local diskarbitrationd[22]: mds [39]:22019 not responding.
Aug 17 21:42:09 Erics-iMac.local diskarbitrationd[22]: fseventsd [48]:17923 not responding.
Aug 17 21:42:15 Erics-iMac.local fseventsd[48]: disk logger: failed to open output file /Volumes/Time Machine Backups 1/.fseventsd/0000000000362fde (No such file or directory). mount point /Volumes/Time Machine Backups 1/.fseventsd
Trouble talking to a disk. The first two probably involve the TC, the third one definitely does -- it's trying to create the new Event Store.
Aug 17 21:44:03 Erics-iMac.local com.apple.imfoundation.IMRemoteURLConnectionAgent[1789]: [Warning] Denying xpc connection, task does not have entitlement: com.apple.private.imcore.imremoteurlconnection (IMTransferAgent:1786)
Aug 17 21:44:03 --- last message repeated 1 time ---
Aug 17 21:44:03 Erics-iMac.local com.apple.imtransferservices.IMTransferAgent[1786]: [Warning] Remote loader crashed for request: <NSMutableURLRequest http://init-p01md.apple.com/bag>
Aug 17 21:44:03 Erics-iMac.local com.apple.imtransferservices.IMTransferAgent[1786]: [Warning] Bag loading failed! Error (__kIMRemoteURLConnectionErrorDomain:-1): The operation couldn’t be completed. (__kIMRemoteURLConnectionErrorDomain error -1.) (null)
Out of my comfort zone, but sure looks like some sort of connection problem . . . with something.
Aug 17 21:48:08 Erics-iMac.local com.apple.backupd[1728]: Deleted 3 backups containing 299.76 GB total; 300.65 GB now available, 209.78 GB required
TM did (finally) connect, figured out how much sp it needed, and started deleting old backups to make room. Since it did, actual copying would have started just after that was sent.
Aug 17 22:07:03 Erics-iMac.local com.apple.SecurityServer[15]: Session 100018 created
Aug 17 22:07:06 Erics-iMac.local ScopedBookmarkAgent[1853]: CFURLCreateByResolvingBookmarkData failed with error [Error Domain=NSCocoaErrorDomain Code=4 "The file doesn’t exist."].
Aug 17 22:07:08 --- last message repeated 7 times ---
Aug 17 22:07:08 Erics-iMac.local QuickTime Player[1845]: It does not make sense to draw an image when [NSGraphicsContext currentContext] is nil. This is a programming error. Break on void _NSWarnForDrawingImageWithNoCurrentContext() to debug. This will be logged only once. This may break in the future.
Aug 17 22:08:37 Erics-iMac.local WebProcess[1866]: objc[1866]: Object 0x7fec4841c8c0 of class NSUserDefaults autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
Aug 19 16:35:11 Erics-iMac.local mds[39]: (/)(Warning) IndexQuery in bool preIterate_FSI(SISearchCtx_FSI *):Throttling inefficient file system query
Most of that is also out of my area, but doesn't seem related to the TC or backups.
Hard to tell so far, but it looks like problem is on your network, or power, or with the TC. Trying backups to a directly-connected external HD would be a quick way to confirm that, and especially if these are your only backups, a wise thing to do anyhow.
It's always prudent to keep "secondary" backups, more so if your main ones are on a network, and especially if there's the slightest doubt about them. See Time Machine - Frequently Asked Question #27 for more info and some suggestions.
And/or, start through the list in the green box in #D2 of Time Machine - Troubleshooting.

Time Capsule freezes when transferring files

My time capsule freezes when data is transferring from my Macbook Pro during its initial update. I tried to connect it through WiFi or ethernet cable. It just freezes like when 800 Mb - 5 Gb were transferred (I have left it overnight). What can I do?
How about doing it by USB cable?

This is from Time Machine Buddy widget
Starting standard backup
Network destination already mounted at: /Volumes/Data
Disk image already attached: /Volumes/Data/Samuel Ng’s MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
Disk image /Volumes/Data/Samuel Ng’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Backup content size: 232.4 GB excluded items size: 10.4 GB for volume Macintosh HD
266.50 GB required (including padding), 2.73 TB available
Waiting for index to be ready (101)
Then my Macbook Pro freezed when 5.16Gb was transferred...

Time Capsule hangs up

Hi Community,
since 3 Month I have now a time capsule and enjoy it very much. I have a MacBookAir (mid 2011) with Mountain Lion installed.
But I have one problem.
My Mac runs the hole night. I can start checking my emails in the morning etc. all fine. But when I start to use for example iTunes (was open the hole night) Time capsule hangs up. My Library from iTunes is stored on the Time Capsule. Time maschine is switch off.
I am getting the impression that there is a problem when the HDD from Time Capsule has to start again from the sleep mode. When I use the Mac over the day all is fine. It does not happen all the time.
When I start to look onto the Time Capsule via Finder it can happen the Time Capsule does not hang up.
Can someone tell what I can do in order to avoid it?
Kind regards,
MacBistram

Hi Chameleon,
thanks for the fast reply.
my Library is to big to move it somewhere else and it was one of the reason why I bought the time capsule.
It does not only happen when I use iTunes. TC hangs also up when I try to copy a large amount of data from my local dirve to the TC (after the 'sleep mode').
I use the TC HDD as my Server-Disk-Storage. It cannot be the case that it hangs up after it comes out of the sleep mode.
Just as additional information. I access the TC over WLAN. Maybe it is the case that the TC hangs up when the WLAN has to mutch to do.
Kind regards

My macbook pro is connected to internet via my time capsule but my iPad and iPhone won't. it shows wifi connection to the time capsule but when i go on to the internet on the iPad or iPhone, it comes up with network error. can anyone help?

my macbook pro is connected to internet via my time capsule but my iPad and iPhone won't. it shows wifi connection to the time capsule but when i go on to the internet on the iPad or iPhone, it comes up with network error. can anyone help?

This can be caused by a number of issues.
Was everything working and then suddenly stopped??
Or is this a new clean setup and has never worked.
Do you have a cable modem which is not a router and the TC setup in bridge? That will cause it. The TC must be in router mode, ie dhcp and nat.
Check the IP the MBP gets including dns and gateway..
Then check the ipad/iphone.. post what IP dns and gateway (router in applespeak) they get.

I bought a new time capsule. When I try to set it up, at the end, it says an expected error occurred. It now won't recognize my time capsule. What do I do?

I bought a new time capsule. When I try to set it up, at the end, it says an expected error occurred. It now won't recognize my time capsule. What do I do?

Do not setup a TC over wireless.. it is like sitting on the branch you are sawing off.
Plug it into the computer by ethernet.. press and hold the reset until the front LED flashes rapidly and start over.

Replace a 2003 (not R2) File Server with a 2012R2 files server and preferably keep the same machine name and IP when finished

I am wanting to replace a 2003 (not R2) File Server with a 2012R2 file server and preferably keep the same machine name and IP when finished. For the moment I just need some "high level" guidance, little details can be worked out once I know
which direction I will go. I was considering that DFS might be a way to help get through the process although when finished the 2012R2 Files server will be by itself with no other file server planned at this time. DFS can stay installed for maybe
future purposes but clearly I wouldn't need the DFS Replication with only one machine.
Here's a few details of the environment....
1. DC's are 2012R2 but it is still 2003 DFL because the old 2003 DCs are still present. But likely they will be gone and the DFL elevated before I start on the File Server project
2. Nearly all machines in the facility have a shortcut on the "All Users" Desktop that points to the existing old File Server. Editing or replacing that shortcut would be a major pain,...hence why I want to keep the same machine name at least,
and maybe the same IP if not too much trouble. This way the existing shortcut would continue to work with the new 2012R2 File Server. The UNC path represented in that shortcut is also configured into one or more of our major business applications,
futher emphasizing the need to keep the UNC path the same throughout the process.
3. The facility runs 24/7/365 but is "light" on weekends. The political environment is such that there is little to no tolerance for any down time at all.
4. Would DFS (based from the 2012R2 machine) be a good tool to get where I need to go?
Thanks for any suggestions.
Phillip Windell

Hi Sharon,
I've done some more reading and have a few new ideas to run past you....
Yes regular DFS wouldn't help and the Namespace would still be different than how it was with just the old server. However I was thinking DFS Replication could replace the purpose of RoboCopy and it would keep the two locations "in sync" until I was ready
to flip over to the new server. DFS Rep can exist independently of a DFS Namespace, so a Namespace is not even needed. It needs a minimum of 2003R2 for the "later & better" DFS Rep but I believe 2003 can do an "in place" upgrade to 2003R2, so I would upgrade
the old server to 2003R2 first. As long as the DFS Rep on 2012R2 and 2003R2 will properly interact I think that will work.
Thanks for the reg info on the Shares. I'm debating if editing that would reg file would really be much better than manually creating the Shares on the new server while the DFS Replication was doing its job. I'll probably export that Key as a
safety move whether I use it or not.
Once the DFS Rep is fully in sync and the Shares are in place on the new server, I figure I would then:
1. Remove the DFS Replication Object (optionally remove DFS Services completely)
2. Rename the old File Server to something else and set it to DHCP
3. Rename the new File Server to the name I want to use and give it the IP the old server had.
How does that sound?
Phillip Windell

Why does Time Capsule echo when time machine backs up?

Every time time machine backs up I get horrid echo sounds from my Bose speakers which are attached to the computer. I use Time Capsule and have for quite a while but this is a new problem - probably about two weeks since it started. It is driving me nuts as it is loud.

There is always a low hum from TC which i dislike but I moved it so it is faint.
Bad.. very bad.. there should not be a low hum "always" from a TC.. If the hum is 50hz, 60hz 100hz or 120hz.. it is a power supply issue that probably just got worse. They do not hum in normal use.. there is a fault in the power supply.
Take it back to apple and get it replaced. Wipe it before you take it in.. they should exchange it.
In normal operation you can put your ear up against the TC.. and power it on..
The start up cycle goes like this.
Fan will immediately start up.. and front LED will flash momentarily green go off then begin flashing amber.
Fan will cut off and the hard disk will spin up.. this is several seconds into the boot cycle.
Hard disk will settle to normal operation.. disk test complete. TC will finish the boot. LED will go green (if everything is good).. after about 1min the disk will stop spinning. From this point the TC should make no noise at all. Audio noise at least. If you have internal power supply hum.. it has faulty transformer or some other part. Since it is under warranty pass it back for replacement.

I used Migration Assistant to copy data to an new MacBook Pro from an old via my Time Capsule. When asked if to inherit time machine history on the new Mac, I mistakenly said no. How do I go back one step to say yes?

There isn't enough space on the Time Capsule to create a separate backup of the data on the new MacBook. And I am reluctant to delete old backups of the old MacBook to create space to backup the new machine. This occurred about 3 weeks ago so the data on the two machines are now out of sync. If I start over by formatting the new MacBook and rerunning Migration Assistant to pull data from the Time Capsule, how do i preserve the last 3 weeks of data on the new MacBook, considering that I didn't keep track of which files changed in the last 3 weeks?

All the rest of the stuff is where it should be. As best I can tell. I have been going through my programs one at a time to see what works. With the change in the OS (Launchpad? What the heck?) I am finding a significant number of my old programs are not working. Some I have found upgrades. But without a working mail program, the machine is pretty useless for work.
The Apple techies had me run through 3 hours of 'stuff' (holding down keys and restarting, etc, etc). It still does not launch. I think we are waiting for a 'miracle', but I need to know now if they should just come get this piece of junk or if they really are able to find a solution in a timely manner.

Time Capsule crashes when Time Machine starts a backup

I've not searched through the postings here to see if other people have seen a similar problem. I've not attempted to repeat the problem I've seen here so I'm not very clear about the cause.
I'm using a MacBook Pro with OS 10.5.4 connected via a network cabled directly to a Time Capsule which is connected to a DSL/Cable modem. The Time Capsule is updated with v 7.3.2 of the firmware. I've got Time Machine enabled but I'm also using the Time Capsule disk (1TB) to store photos that I've previously archived to CD. I'm in the process of copying all the data from CD to the Time Capsule.
Having copied some photo data to the Time Capsule I was trying out some photo cataloguing SW to see if it was any good (iPhoto is no good to me as I don't want to store photos on the local drive of my machine) - Kodak EasyShare v6.1. Having loaded some images into EasyShare I tried to use finder to search for the file names of some of the images to check that EasyShare was not copying images to my local drive. While I was doing this I think Time Machine tried to kick in and start doing a backup. I believe that Time Capsule crashed at this point. Finder froze and after I restarted it (via Force Quit not a re-boot) I discovered that I had no network connection and Mac OS couldn't see the Time Capsule under FInder or via AirPort Utility (the Time Machine backup also timed out and failed). Time Capsule just sat there with the disk spinning and a green light on the front as if all was OK. Actually - the disk just kept spinning (Time Capsule normally shuts down the drive after it is idle for a while). Because of this I'm pretty sure that Time Capsule had crashed.
I experimented with re-booting my Mac but still no network etc so I tried power cycling the Time Capsule and everything came back to life.
I'm guessing that my doing a search (or some other drive activity on Time Capsule) at the same time as Time Machine kicking in with a backup caused Time Capsule to crash.
Perhaps this is not a very interesting point if this problem is not repeatable but - well, I'd be interested to know if others have seen similar behavior...

I'm having a very similar problem and it is detrimental.
Here is the scenario: I have a 1TB Time Capsule as my primary router. I am able to perform backups on all but one of my machines. My iMac backs up via 1GB ethernet to the TC, my MacBookAir (60GB,SS) backs up via wireless N (270mb) and my other MacBookAir (80GB,IDE) also backs up via wireless N without any problems.
I used to use a 500mb external drive to backup my iMac but outgrew it, so I started backing up to the TC instead. No problems at all.
I also used to back up my Intel MacMini running Mac OS X Server 10.5.5 to a similar external hard-drive but haven't in a while.
I decided it finally made sense to backup ALL my Mac's to the same 1TB TimeCapsule but it's just not working out!
On the MacMini; I turn on TimeMachine, the TimeCapsule has been chosen as a backup location, it prepares backup for a moment, mounts the backup drive and then appears to begin backup up... No...! First I get a message the the TimeCapsule closed the connection, next I lose Internet connection across my entire network both wired and wireless and then the TimeCapsule light turns amber, flashes and essentially does a completel crash / reset and then comes back to life a few moments later. I can backup any other computer except the MacMini to the TimeCapsule without "crashing" it and it makes no sense! Every computer is completely up to date with all the latest patches and the TimeCapsule is running 7.3.2
I sure hope this gets resolved, seems like other people are pretty disgusted with the performance of the TimeCapsule with problems that have no resolution.

Time Capsule Hangs with USB Drive Connected after installing 10.5.6 update

The 10.5.6 update basically made my External USB Disk connected to the Time Capsule unusable. I've repaired the permissions as suggested in other posts - this did not fix the problem.
I was unable to perform any incremental backups initially after the 10.5.6 update, so I archived my sparsebundle and created a new one by doing a full fresh backup - which completed successfully. However, after the backup, I was unable to connect to the Time Capsule or the USB drive connected to the Time Capsule via Finder - when trying to connect, my computer hangs and I'm forced to do a hard restart of BOTH my computer AND the Time Capsule, if I just restart one or the other the problem persists. If I let the connection attempt run long enough I get an "Error Code: -8072" message and still have to do a hard restart. After the hard restart of my computer and Time Capsule I'm able to connect to the Time Capsule and the USB drive connected to Time Capsule just fine. However, once the Time Machine backup runs again - the same problem returns, I can no longer access the Time Capsule or the USB drive connected to Time Capsule via Finder and have to do a hard restart of BOTH my computer AND Time Capsule. This 10.5.6 update has been havoc, anyone have the same troubles or ideas for resolving this? Before updating to 10.5.6 my system was working flawlessly with Time Capsule and the connected USB drive.
UPDATE: I've just verified that this problem only occurs with my external LaCie Hard Drive connected to Time Capsule via USB. If I disconnect my LaCie Hard Drive from the Time Capsule and restart the Time Capsule everything works fine (backups, access to Time Capsule Disk from Finder). If I connect the LaCie Hard Drive via USB to the Time Capsule, I am able to access the LaCie Hard Drive in Finder UNTIL the next Time Machine backup. After the first Time Machine backup with the USB drive connected, I can no longer access the USB drive from Finder - Finder hangs and eventually produces "Error Code: -8072". If I disconnect the USB drive, then plug it back in - Finder no longer hangs and I can access the drive connected to Time Capsule until the next backup occurs.
Anybody have ANY ideas? This worked fine before the 10.5.6 update!

I am having a similar problem. Never tried it before installing 10.5.6, but have a Time Capsule (500GB) with a 1TB WD MyBook Essential Edition connected via USB. Hardware is password protected by authorized users of network and needs separate login to access. When I initially set it up, it worked fine (though too difficult to set up). The WD storage drive showed up in Finder window as a subset of the Time Capsule after clicking on the Time Capsule icon. I had an "-8072" error message yesterday that I ignored, but then the file contents of the WD storage drive took forever to be viewed in Finder (though video files could be accessed wirelessly). Today started having a problem... coincidentally?... after a Time Machine backup, and got the message: "The operation could not be completed. An unexpected error occurred (error code -8072)." Now I am unable to get into the WD drive when I click on "Connect As" on the Time Capsule icon in the Finder menu... I just get the -8072 error. I no longer even see the Time Capsule disk as a subset of the Time Capsule icon in the Finder Toolbar.
What is going on???

Time Capsule hangs in initial backup after having deleted all data.

Hi,
I'm having a big problem trying to set up my time capsule after deleting all data on it again.
In the beginning the problem was that I have used the time capsule as a file server and a backup volume. I guess it was the main problem was that the disk was full and time machine had no more place to backup any longer.
So I always got an error that the time machine had a problem to backup.
I decided to delete all data on time capsule and start from the beginning.
After deleting all data and trying to start from zero, Time Machine is trying to initiate the backup.
But nothing more happens. It seems to hang up while initiating. I tried to delete the disc several times but the problem is still occuring.
Maybe you had the same difficulties and found a solution?
Thanks a lot for your help!
Carsten.
Macbook Pro Core 2 Duo 2,2 GHz Mac OS X (10.5.4) 4 GB Ram

same here although I get to "finishing Backup" and then mine hangs and it can be hard to shut down. I discovered the only way I could get it to stop once was to launch Disk Utility and eject the sparsebundle listed there. I have no backups at all.I will call Apple on Monday and see if they have anything floating around there that might fix us. I will report back-If you make any progress please let us know here! We will get this thing working I am sure of it!

Time Capsule stuck in "Finishing Backup"......what to do?

Well...I finally am about to finish my first full backup and it is now stuck in "finishing Backup" and has been for over two hours.....please help.

Ok, here's what I had to do (with the help of a networking genius friend) to make Time Machine actually finish a backup on my Time Capsule. Now it's working perfectly, and the backups are really fast:
I erased the Time Capsule to start everything from scratch. I reselected it using the Time Machine preferences.
I connected the TC DIRECTLY to my Imac using Ethernet rather than depending upon wireless (there is just too much interference in the air from other networks, my Airport Express, cordless phones - I think this was creating problems - it works much better if actually wired through Ethernet). I also gave my Imac a fixed IP address, and on the Time Capsule I changed in the Network settings the "Renew DHCP lease" tab to every 4 days, rather than every 4 hours (it's possible this was causing hiccups).
I excluded Time Capsule from Spotlight using the 'Privacy' tab in the Spotlight preferences.
I uninstalled Microsoft Entourage and transferred all my mail to Mail instead - Time Machine doesn't work too well with Microsoft applications, apparently, and wants to back up your entire email database (in my case, around 3GB) every time you send a single email. It works better with Apple software (cunning plan by Apple!)
Then I ran the initial backup again - it worked fine, and has been automatically backing up without any hitches ever since. I have it connected through Ethernet still and will leave it wired up that way. I think it was my unstable wireless network - which has an old Airport Express and an ancient Powerbook which kept not only slowing down the speed but confusing Time Machine. It seems to work much better when I have reduced the number of wireless elements in my network. Wireless networks are just not that reliable - they drop out all the time and that creates corrupted data in Time Capsule, and it then spins forever trying to work out what's wrong.....

Time capsule hanging up after OSX Lion upgrade

Hello
After my recent upgrade to OSX Lion, my MacBookPro is hanging up when trying to connect and update my Time Capsule update...
After 8 hours of unsucessful trials for a 8 Go back up, I have given up.
Something to be advised in order to get back on the same easy/seamless Time Capsule updates I enjoyed previously ?

I am using a 2010 iMac and tried a completely new 250+Gb Time Machine copy to a WD Passport USB 2.0 500Gb external HD. It's taking like more than 2 days. Never took that long before. Not a web or wi-fi issue. Before Mountain Lion, should have taken 3-4 hours max. I tested the external hard drive on a another Mac with a large file transfer and there were no problems. I also turned off all the spotlight choices. The issue has something with Mountain Lion.
Has anyone heard from Apple acknowledging the issue and that they are working to resolve the problem?

Time Machine - Time Capsule hangs when finishing

Similar Messages

Maybe you are looking for