Time Machine not working with Yosemite

Just completed it, hopefully something comes out it, 160 billion in cash and they can't get it right, makes me wonder where all the money is going?

Bug report submitted. Thanks for the link jdaddy404.

Ronback, I don't claim to be an expert (far from it, actually) but I did spend a bunch of time with an Apple guru trying to fix this... to no avail I might add until I found this thread. However, I am successfully running on USB 2.0 and USB 3.0 currently (OS 10.10.1). During the trouble-shooting, I reformatted several external USB drives and all of them were accepted by Time Machine for back ups. Let me suggest when formatting (Partitioning): select Mac OS Extended (Case-sensitive, Journaled) and in Options, GUID. If you've done that already, I don't know what else it my be... sorry.

John

I have tried all those options and no success, still haven't been able to do a time Machine backup since the upgrade to Yosemite. I have also contacted Apple support am hoping something comes out of it.

Third bug report now submitted for this issue beginning with PB3 and now with 10.10.1.

The squeaky wheel gets the grease.

Hello, for me, the access has improved to the backups, as I have the internal firewall disabled from my iMac at Yosemite.

I've never enabled the firewall in Yosemite and still have the problem. The source of the problem appears to be a bug in Yosemite as it occurs on different machines with clean installs, no custom apps and with my existing generation 3 and brand new generation 4 Time Capsule.

I've started getting a "Time Capsule not found" error message intermittently when a snapshot refuses to load (becomes visible) now. No changes were made to the system when this started appearing. If I open Airport Utility when this error occurs I've noticed a spinning curser and my TC's backup disk can't be found yet I'm still connected wirelessly to the WWW and can get to websites. After a few more minutes of cursor spinning it ends with a warning window asking me if I want to forget this backup disk. I simply click yes and reboot the TC or my iMac and the connection re-establishes itself for x number of hours until I try and enter TM again whereupon navigating TM snapshots more often than not fails repeating the whole process above.

I can wait until Apple gets this resolved as both OS X and Internet Recovery still function if disaster strikes in the meantime as well as a manual backup on a spare external HDD kept locked up in a cabinet and DVDs in a locked fireproof box offsite.

This is just a crazy issue. I backed up my Mac on 10-31 prior to installing Yosemite -- to my time capsule. I have not been able to "talk" to my time capsule ever since. I have spent 30 minutes on phone with Apple support and three trips to various Apple stores with the last experience VERY UN-Apple-like as the Geek tech refused to acknowledge there is any issues with Yosemite -- denying any information on the Apple website. He insists the issue is a broken time capsule and ordered a refurbished capsule to the tune of $259.00 --- with a new one at $299.00.

I would believe him except for all the posts here and a further strange happening. I have reinstalled Yosemite to the latest patch level. IN ADDITION, MY SIGNIFICANT OTHER HAS A MAC, UPGRADED TO YOSEMITE AT THE SAME TIME (WITHOUT A PRIOR BACKUP) AND HE CAN ACCESS MY TIME CAPSULE.

So, is it the time capsule or Yosemite? I'm leaning toward Yosemite.

Any suggestions and yes, living in hope that I do not need any files from my backup until Apple acknowledges and fixes this...?

Thank you and yes, I feel you pain.

If you will go back a few days to a post by GroveMan, he states a conversation with Apple regarding this issue in which they agreed that it is an Apple Yosemite problem that will be addressed in the next update. There are many apple customers using iMacs, and notebooks that are having the exact same problem. Time Machine will make the save, however, you will not be able to access any backup with the side bars, nor can you recover any backup in the normal manner. There are several different work arounds already posted that will help you in the meanwhile, but Time Machine as you knew it under Mavericks is broken. We are all hoping for a fix in 10.10.2

hey DorJamJr Still i am not getting your point. Please help. i am clicking my HD in finder but when i open time machine its not getting access to my documents backup folder.

Please help.

Hi Zohaib,

1. Open a finder window

2. Select your Mac under Devices (if you Mac isn't there, select Preferences, Sidebar, and add a check to your Mac under Devices).

3. Enter Time Machine

4. Navigate to the folder you want - DO NOT CHANGE THE SELECTION OF YOUR MAC!

That method works for me. I have access to all my backups. Another way is to open a Finder window, select Desktop, enter Time Machine, select you Mac under Devices in the Sidebar, and then navigate to your desired folder.

Good luck!

Hi Jon,

Ok I did what you said and time machine does travel back to backups. However, "restore" button is shaded and it's not possible to click on. What's next??

HI. Sorry it doesn't work for you. I am able to recover any item on my Time Machine back up using that method.

BTW: R U using OS 10.10.1? And just to be sure, are you going into your User account via your computer under the Devices? I am not able to access most things using any of the choices under Favorites. Documents seems to be the worst for me. Not sure why.

I'm on my cell cuz of power outage so no more posts till power returned.

My problem is that no snapshots are being created hourly or daily or even weekly, as promised. AND my time machine won't even open if my external hard drive that was set up for TM is not connected. I have a MBP 2011. It always kept a version of files every hour for the last 24h. BTW I have 300gb of storage free. on 2 disks, one HD, and one SSD. Contacted support they don't even know what is happening.

Seems that Apple is aware of this problem. I filled a Bug Report (https://bugreport.apple.com/) 2 weeks ago regarding this problem on OS X 10.10.1 and they just closed that as a duplicate of #18870638, which is still opened. So, that means they acknowledge the problem and are somehow fixing it 🙂🙂