Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

JonMikel

macrumors newbie
Oct 21, 2015
1
0
I'm having similar issues with Time Machine. I'm running El Capitan in a brand new MacBook 12 in.

I have a network attached storage (Seagate's Personal Cloud), since the update my Finder can't find the network drive, if I want to access I have to connect directly to the IP trough 'Connect to a server'.

After 30 attempts when finally TM finds the Personal Cloud, it takes more than 30 hours for a 20GB backup and it gets freezed at 17GB.

My wife's 2010 MacBook Air is working fine.

Damn you, El Capitan.

Regards to all of you.
 

netnothing

macrumors 68040
Original poster
Mar 13, 2007
3,822
422
NH
UPDATE: Someone on the Apple discussion mentioned unplugging the USB cable that is plugged into their Mac and their UPS battery backup. When you do this it seems you have to restart to get things to work.....but it looks like this may fix the issue for now. I did this on my 2010 Mac Pro and it worked for the first backup.....I will watch for other backups.

Of course, this doesn't help anyone with a Macbook, as that always has a battery activated. I'm wondering now if it's a Energy Saver issue.

-Kevin
 

netnothing

macrumors 68040
Original poster
Mar 13, 2007
3,822
422
NH
Nope, it's an inadequate testing issue due to pushing updates out the door on Marketing's schedule rather than on Engineering's schedule. Something as critical (to many people) as TM not working, even after the first bug-fix update, is very wrong.

Most of this I agree with.....the only issue is that is doesn't affect everyone.....so it clearly got missed. Now, the fact they couldn't get it fixed in the .1 update is sad.

Gone are the days of "it just works". Now marketing pushes for "it should work" ;-)

-Kevin
 

madsci954

macrumors 68030
Oct 14, 2011
2,736
673
Ohio
Just saw this post and wanted to chime in, as I had a similar issue. I have a 2014 Mac Mini with a 6th gen TC hardwired to it, it runs on a sleep/wake schedule from Energy Saver settings.

About a week ago, I noticed my last TC update was not run since 9/30. I don't use my Mini all that often, so that's why I just noticed it. I tried doing a manual backup and it appeared to run but still gave me the 9/30 last back up. Me being used to computer issues, I ran the tried and true method of "did you try turning it off and on again?". I rebooted and as soon as my Mini finished setting up (platter HDD >_<), my TM icon in the menubar told me last update was today. I thought Yay, fixed it, and walked away.

I just now went into Time Machine and saw I did have daily backups from October 1 to today, so I just assumed it was just a display glitch. OP might have a bigger issue though, but I figured I'd give my 2 cents.
 

MuckSavage70

macrumors member
Jan 10, 2013
60
99
Denver, CO
Same issue here. Sent the log files to Apple, so we'll see what happens with that. 10.11.1 didn't fix it for me.

Running a hackintosh, so stuff like this happens, but this same box worked perfectly in Yosemite and Mavericks. Backing up to another hack running Server 5.

Some other weird things I noticed, may or may not be related. My other macs (iMac, MacBook Pro and old Macbook) backup just fine. Get some weird errors from time to time about the "identity of your backup drive has changed" but other than that has been pretty smooth. The one thing I do notice on my Pro though, is there is a folder on the root level called "TSSleepHandlerHelp" with no files. Deleting it causes it to come right back when you reboot. And sometimes on the pro the sparse bundle won't eject after a backup. I can force eject it, but don't want to for fear of messing it up. In my Server logs it shows my Pro backup as always "in progress", I assume since it never ejects the volume. Hourly backups work fine however.

Since none of you (that I saw) are backing up to a Server, I think we can eliminate that as the problem. It's got to be something with backupd. I've noticed a few lines in the console about sandbox not allowing backupd. hopefully apple gets a fix soon, manual backups are lame. :)
 

AlteMac

macrumors regular
Jul 21, 2011
215
80
New York suburb

AlteMac

macrumors regular
Jul 21, 2011
215
80
New York suburb
Further follow-up. Reconnecting the USB connector to the APC broke the TM schedule, so there is a clear connection here. Mine is going to remain unconnected until I Apple fixes it. My expectations are low.
 

gmanWA

macrumors newbie
Nov 12, 2009
29
11
unplugging my APC ups usb cable and restarting fixed this issue for me. firewire drive and NAS time machine backups are now operating on schedule.
 

Ebenezum

macrumors 6502a
Mar 31, 2015
782
260
I am not certain if this is relevant or if I should make a new thread but my problem with Time Machine isn't that it won't make backups, instead it crashes when I try to restore files from backup.

I tested both external hard drives with Techtool Pro and DiskWarrior, furthermore drives are otherwise functioning normally and Mac Mini had its motherboard replaced a few months ago so I am almost certain problem has to be in the El Capitan and not hardware.

Apple discussion had a few threads about similar issue but they may not be relevant because I am not using multiple monitors unlike most people on those threads and only Time Machine crashes, Finder doesn't...
 

Riwam

macrumors 65816
Jan 7, 2014
1,095
244
Basel, Switzerland
I am not certain if this is relevant or if I should make a new thread but my problem with Time Machine isn't that it won't make backups, instead it crashes when I try to restore files from backup.

I tested both external hard drives with Techtool Pro and DiskWarrior, furthermore drives are otherwise functioning normally and Mac Mini had its motherboard replaced a few months ago so I am almost certain problem has to be in the El Capitan and not hardware.

Apple discussion had a few threads about similar issue but they may not be relevant because I am not using multiple monitors unlike most people on those threads and only Time Machine crashes, Finder doesn't...
****
IMO the probabilities speak for a (further) bug in El Capitan.
After making the great mistake of installing THAT I had so many bugs that tried restoring Yosemite from the TM.
It did not work no matter which backup out of those proposed to me I chose.
El Capitan had obviously screwed the TM function.

Thanks God I had made before a bootable clone USB drive with Yosemite. Booting from it I could erase the inner drive and clone Yosemite back.

With all my respect for Apple I am afraid that 10.11 should not have been released to the public, at least not in the present condition...:oops:
Ed
 

piratemc74

macrumors member
Jul 15, 2008
52
0
Holly Springs, NC
Adding in my issues here. I use two targets. 1is a USB connected 4TB drive. The other is to a Synology NAS TM Volume. I noticed that I wasn't getting automatic backups. I don't know for sure when this started. Manual backups will rotate between the two targets.

Interesting for me, I see no message "Next backup at HH:MM". I'm going to follow this thread thanks.
 

vonProteus

macrumors newbie
Oct 29, 2015
2
0
hi
i had problem with TM and now its seems that it works now
i have Mac Mini 2014 and APC UPS connected via USB
i change System Preferences -> Energy Saver -> Power -> Enable Power Nap
as i said before it seems it works now

sorry for poor english
 

netnothing

macrumors 68040
Original poster
Mar 13, 2007
3,822
422
NH
Some on the Apple forums are reporting that backups aren't running if you have the UPS USB plugged in at startup. If you startup the Mac without it plugged in, and then plug it in afterwards, backups run.

-Kevin
 

vonProteus

macrumors newbie
Oct 29, 2015
2
0
hi
i had problem with TM and now its seems that it works now
i have Mac Mini 2014 and APC UPS connected via USB
i change System Preferences -> Energy Saver -> Power -> Enable Power Nap
as i said before it seems it works now

sorry for poor english

sorry it doesn't work
 

u2mr2os2

macrumors member
Aug 11, 2002
58
0
Albuquerque, NM
There may be two problems here. I did a normal upgrade to El Capitan and was having no TM problems until I replaced my hard drive. I cloned the drive with SuperDuper to the new drive and then installed it. After that, TM would not run automatically. I did not run Migration Assistant from the clone into a clean El Cap install.

Since it did not clone the recovery partition, I ran the El Cap installer over the cloned drive. It put the recovery partition back but did not fix TM. Also, the 10.11.1 update did not fix it. I also have a 2nd TM backup off-site that would not automatically run, so it wasn't a problem with the TM drive. I also tried TimeMachineEditor, but its scheduled backups wouldn't run either. I also tried removing the drive from TM and re-adding it.

What seems to have worked is doing the steps given here: http://www.creativetechsupport.com/help/it/install/timemachine-inherit.html

When cloning the drive, since it was not a perfect clone, the ID of the HFS+ volume was not preserved, and TM thinks the backup does not belong to it. These steps seem to do what re-adding the drive didn't which was to change the ID on the backups to be that of my new hard drive volume.

Even if you didn't do exactly what I did, this might still fix things if nothing else has worked since whatever the El Cap bug is for some might be related.
 

netnothing

macrumors 68040
Original poster
Mar 13, 2007
3,822
422
NH
Good news - this is working for me. I am running two TM targets. 1 to a NAS device (Synology), and the other to an external USB. TM is doing "round robin" backups to both, as it should.[/QUOTE

I ended up doing the other workaround of plugging in the USB after the machine has restarted. That's been working for me.

-Kevin
 

rkitover

macrumors newbie
Nov 16, 2015
2
0
Philadelphia, PA, USA
This worked for me:

First, turn off time machine in sysprefs.

Then, run this command in terminal:

sudo rm -f /Library/Preferences/com.apple.TimeMachine*

Reboot.

Turn time machine back on.
 

rkitover

macrumors newbie
Nov 16, 2015
2
0
Philadelphia, PA, USA
This worked for me:

First, turn off time machine in sysprefs.

Then, run this command in terminal:

sudo rm -f /Library/Preferences/com.apple.TimeMachine*

Reboot.

Turn time machine back on.

Sorry, this actually does not work. It does the first backup, but then automatic backups don't run anymore again.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.