Reported a similar problem on another thread, sure seems to match my experience. See https://discussions.apple.com/message/16569546#16569546Network destination already mounted when start Time Capsule backup after reboot
I also see the situation where the first Time Machine backup mounts the Time Capsule, a Finder window opens and the backup fails. If I then unmount the sparse bundle and /Data directory on the TC my backups work until the next reboot.
Sorry can't be of more help, but at least it seems good to know there are several of us having a similar issue.
Glad to see im not the only one with this problem, i have this problem for some weeks after upgrading to Lion and setting up " back to my mac" and Icloud. I have tried everything including a full new installation of my timecapsule and a full new backup (advise of applecare) but after a reboot i have to disconnect all users and connect again to make timemachine work. Drives me crazy, Apple do something about this bug please!!!
Apple must be a bit overwhelmed with bugs to fix just now. They are a bit silly not to acknowledge - as Jean's message finally does - that they are working on it. You'll just have to leave your machine running (sleep is OK, just don't shut down.) Harder to do with a laptop of course. Like you I'd love to see a fix and move on.
Jean, thanks for posting that. I tried to follow up on the original reply from Express Lane and headn't heard anything so I was hoping someone would get a reply. Now, I'm running into the problem even when I put my Mac Mini to sleep, I have to go thru the disconnect/reconnect sequence twice!!!!!
I'm just glad I got the backup drive doing Carbon Copy Cloner before I put MacMini to sleep.
Hi Joseph !
I was lucky to get in touch with a very smart 2nd level Apple Care engineer who reported to US. devellopers
as soon as he realised usual remedies wouldn't make it and that I wasn't the only "ugly little duckling"
having this problem.
I was requested to answer to a survey related to the help I got about this issue.
I gave a 100% satisfaction appraisal for the engineer who really deserved it.
But in the free comments at the end I strongly suggested Apple should give access to a kind of digest
feed-back of the most recurrent problems showing up on Apple communities and already in hands
of Cuppertino devellopers so their Apple Care hot line people and their customers wouldn't loose time
I also registered as a develloper (free) to be able to report bugs straight to Apple.
I believe Apple's future is also our business.
let's keep Steve's spirit alive !
Just to signal that i have exactly the same problem in a slightly different set up: instead of the Time Capsule i have a Mac Mini running Lion Server and acting as a Time Machine server.
I have a Mac Book Pro, that has been updated from Snow Leopard to Lion, that behave as you all described.
And a shiny new Mac Book Air that came with Lion and backup without problems to the server; i upgraded both to 10.7.2, by the way.
Thanks for your answer !
Is your Mac Book Air running Os 10.7.2 ?
If so, did you try to reboot it ?
If you did, does Time Machine behave normally after ?
I think my Mac Book Air is working fine with Time Machine because it is still running 10.7.
instead of my Imac already under 10.7.2 having troubles finding the sparebundle on the Time Capsule disk
after every reboot.
It is the reason why I wait for the next release - supposed to solve the problem - to upgrade my Mac Book Air,
after testing it on the Imac first to see if the problem is solved or not.
To sign up to the party - my set up is doing exactly the same thing since 10.7.2 - Error -1, then have to disconnect all users using the AirPort utility, then into SysPref and Time Machine to reconnect.
Then it all works until the MBP gets rebooted, and so we go around again....
Looking forward to 10.7.3!!
Sorry, i wasn't clear.
Both laptops (and the mini server) run 10.7.2. The Time Machine backup works just fine with the
Mac Book Air (end 2011); rebooted, switched off and on, sleep, whatever.
It doesn't with the Mac Book Pro (early 2011). The only different between the two machine is that
the Mac Book Pro was upgraded from Snow Leopard to Lion, while the Air came with Lion.
Thanks for your answer.
I am in a certain way in the same configuration as you, the Imac having troubles finding the sparebundle after reboot was upgraded from Snow Leopard to Lion and the brand new Mac Book Air doing fine came with native Lion.
The difference with you is that the Imac is running Lion 10.7.2 and the Mac Book Air Lion 10.7.
I was advised by Apple care engineer to leave the Mac Book Air on Lion 10.7. until next Lion release.
The only negative point is that I cannot use Icloud on the Mac Book Air for the moment to synchronise Contacts Ical etc ...
Let's hope the upgrade is comming soon !