Time Machine not working with Yosemite

I got a message from them having me perform the operations and send them a report. I did. Never heard back, but hopefully it's something that helps.

I am able to recover items as well; I can go in and copy paste documents from backups but the restore button is shaded, can you click on your restore button and do a full restore ?

I am using 10.10.1

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, and SEEMS THEY DON'T KNOW ABOUT THE PROBLEM. Just finished a fresh install of yosemite, without the migration assistant on the beginning of the install, and now I can't see files from my older back-ups. I could save my files copying and pasting them folder to folder.

It seems that older MBP (2011) are having this issues, while 2014 Macbooks airs are not, since my friends who have a MPB 2011 are having the same issue, and one friend who just bought an air are not having problems at all.

Gokaygs: Yes, my Restore button is active when I enter Time Machine via the method I described. I cannot, in most attempts, do what you can and enter my Time Capsule drive on the desktop and select items to copy/drag to my desktop.

Paulo: Your problem (and apparently some of your acquaintances) is as you describe. If you read all the posts in this thread, you will see that there are multiple manifestations of THE problem, which is the failure of Time Machine to work as it historically (😉) has.

My problem is multiple: 1) that I have almost no access to the Time Machine drive - when I attempt to open it on my desktop I get an error message, 2) that I cannot enter Time Machine and select any item listed under Favorites and then Restore it. OTOH, I can enter Time Machine, select my computer under Devices, navigate to my Home, and Restore any item, at least those I've tried to restore. AND (vigorous knocking on wood can be heard now) both my Mac Pro and my MacBook Pro Time Machines are continuing to create backups as expected.

My machine is a MacBook Pro (17-inch, Late 2011), 2.5 GHz Intel Core i7, 8 GB 1600 MHz DDR3 running 10.10.1. Its Time Machine, connected via Airport, resides on the disk drive on a 2TB Airport Time Capsule 802.11AC, Part No. FE177LL/A, Model No. A1470.

My other machine is a Mac Pro (Early 2009), 2.66 GHz Quad-Core Intel Xeon, 8 GB 1066 MHz DDR3 ECC running 10.10.1. Its Time Machine, connected via USB 3.0, resides on a new 4-Bay Drobo w/ 4x4TB drives.

Hi,

Recently upgraded from Mavericks to Yosemite. Ticked iCloud Drive in System Preferences and started a backup (circa 2GB). First thing I noticed was poor performance and not being able to access previous backups in Time Machine. In fixing the performance issue I logged out of iCloud and unchecked iCloud Drive in System Preferences. That stopped this "bird" (a background iCloud daemon) process in Activity Monitor from hogging the CPU.

I then went to try and "fix" my Time Machine issue and hey presto there is no issue any longer. So it appears that this background "bird" process related to iCloud Drive was the culprit.

Hope this helps somebody.

Regards,

Sean.

Hey! I de-selected iCloud drive in System Prefs and now I see to have my Time Machine back. It isn't perfect; for instance, I have to navigate to the documents folder via the users folder, rather than directly through documents, and it takes a while to load each card when switching between folders, but it's working!

Didn't affect my situation (except I lost the pictures I had on the Cloud Drive... I have copies, fortunately. Documents is still the bugbear in my experience.

I had and stil have the same problem (Time Machine noy working with Yosemite )

what do you mean by Starwars Interface ?

how to fix in"details"

thks

jyce: October is a long time ago in computer years... much has happened since then. Read the intervening posts. I'd go from newest first, myself.

As far as I know. in the second beta of 10.10.2, Apple asks to pay attention to WIFI problems, but doesn't say anything about the bug in TimeMachine.

Not surprising. I bet it's a big problem considering the variable manifestations. It is especially unfortunate for those users who rely upon Time Machine as a storage device and not, as I do (mostly), as a emergency replacement back up for a total failure. Not to mention those who seem to not be able to continue Time Machine backups!

Personally, I would really like Apple to fix the broken VNC Screen Sharing connections. I use Screen Sharing daily and currently have to enter its IP address instead of clicking on a VNC doc to screen share with my Mac Pro.

Everthing is working fairly normal, except for not being able to search & restore things back into current system using time machine. I don't think everyone has issues using there time machine. I don't think that I did anything wrong on my clean install, that would cause this kind of problem, but maybe I did?

What I thought I said, though not clearly apparently. My main use for Time Machine is if I have a failure of my computer (including my accidentally erasing my hard drive... been there, done that!) I start up in Restore mode (holding "Command" and "r" while starting up) and I can do a complete restore from the most current Time Machine copy... I do have trouble, as do most posters here, attempting to restore a specific file from a specific Time Machine backup, e.g., xxx.jpg from 11/02/2013.

I hear you John. My Time Machine problems are fairly identical to yours. I'm able to restore the whole computer using time machine wt command r, but I have a huge problem finding individual files in time machine. It takes a little bit longer, searching for the file to restore, but I found that by just going into your backup drive, and specific date you can restore files. It kinda of makes the concept of Time Machine unusable, but it works!