Level 1

28 points

Time Machine not doing hourly backups on El Capitan

I noticed on Oct 21 that my Time Capsule had not performed an automatic hourly backup of my Mac Pro since Oct 17. Time Machine Preferences said it would perform an hourly backup at a stated time less than an hour in the future. However, I tracked it over the next 24 hours and saw that it kept advancing the scheduled hourly backup by about an hour but did not actually perform any of the promised hourly backups. I went into Time Machine itself and confirmed that none of the hourly backups were present, and I also examined the backup disk in the Finder with the same result. I ran a full backup yesterday, and that worked correctly, but automatic hourly backups are still failing silently. Holding down the Option key while opening the Time Machine menu in the menu bar, I ran Verify Backups and got a report from Console.app that "Backup verification passed!" I filtered the Console log on "backupd" and found that, although backupd reports when I verify backups, there is no hint that backupd has tried to perform any automatic hourly backups.

I also examined my MacBook Pro, and it is experiencing the same failure. I ran a full backup of the MacBook Pro, and that worked correctly. The automatic hourly backups continue to be promised but never happen.

Googling the problem, I found similar reports here: <http://apple.stackexchange.com/questions/210832/why-doesnt-time-machine-do-sched uled-backups-after-my-yosemite-el-capita…>. These reports indicate that people have tried all sorts of remedies, including completely removing the Time Machine backups volume and starting over again, without success. The problem reportedly affects external backup disks as well as Time Capsules like mine. The problem started for me days before I installed OS X v10.11.1 on these two machines, so the problem apparently began in OS X v10.11.0 El Capitan.

My wife's MacBook Air is on the same network, but it is still running OS X v10.10 Yosemite -- and her automatic hourly backups are working correctly to the same Time Capsule. Her Console log shows several messages every time an hourly backup begins and proceeds. So the problem was clearly introduced in El Capitan and must be a bug in the new operating system.

This is on my home network. Both of my Macs are wired into the network using Ethernet cabling built into my home. My wife is running on wi-fi so she can easily move her Mac around the house. I am confident that this problem does not point to the Ethernet network as the culprit, however, because I am able to move all manner of files from Mac to Mac, examine the contents of the Time Capsule disk in the Finder, download files over the Internet and surf the Internet, all over the wired network through the Time Capsule without difficulty.

This is an urgent and critical problem, because most users rely on Time Machine for automatic hourly backups and, like me, can go for days without checking to make sure it is still working.

Mac Pro, OS X El Capitan (10.11.1)

Posted on Oct 23, 2015 4:40 AM

81 replies

SBeattie2

Level 2

221 points

Nov 14, 2015 10:11 AM in response to SBeattie2

Correction to my previous post about resetting SMC (on the Mid 2010 MacBook Pro 15"). Sorry for the error.

1. Reset SMC (remove mag safe connector - allow the battery level to run down enough that it is less than fully charged - shutdown mac - reattach the mag safe connector - (LED will be orange) simultaneously press and hold Left Shift-control-option and power buttons - then release (The LED will change states - orange - green - orange again - indicating the reset has occurred). Press the power button to boot the Mac.

Nov 14, 2015 11:24 AM in response to SBeattie2

Thanks SBeattie2. Fixing the (/Library/Preferences/com.apple.TimeMachine.plist) did the trick. My Mac Pro 5,1 is now doing hourly TM updates with the USB APC plugged in.

xco

Level 1

13 points

Nov 19, 2015 5:47 AM in response to cheeseb

I have the same TM scheduled backup issues AND use an external UPS (w/USB).

Will try disconnecting the USB cable and reboot as suggested here.

This whole discussion has been very helpful! Thank you all!! 🙂

SBeattie2

Level 2

221 points

Nov 19, 2015 8:00 PM in response to xco

I have submitted a bug report with Apple and they have responded to it. I was expecting them to say it was a duplicate - but apparently not. Based on the testing I have done the following seems to true:

1. The problem surfaces (or the condition that causes it is created) only when Yosemite is upgraded using the 10.11 (Original release) of the installer.

2. The problem will not occur if Yosemite is upgraded using the 10.11.1 (subsequent release) of the installer.

3. The problem will not occur if you perform a clean install of 10.11.1

4. Unfortunately - if you created the problem by upgrading Yosemite with the 10.11 (Original release) of the El Capitan - subsequently installing the 10.11.1 upgrade is not going to fix the problem.

I suspect that Apple will fix this quickly - due to the seriousness of the issue - just a guess. I am not affiliated with Apple in any way - so I can't speak for them.

To recap the workaround:

For Mac Desktops - disconnect the UPS Data Cable and reboot (you will still have UPS power - but you will lose the automatic clean shutdown capability because the UPS data cable is disconnected).

For Mac Portables - ensure that the Backup While on Battery Power box is checked in the Time Machine Preferences.

If you really want your UPS data cable to remain connected and still get your automatic backups - then try the edit to the Time Machine plist fix that I posted earlier in this discussion. It has been working for me.

~Scott

Nov 20, 2015 1:29 PM in response to SBeattie2

For me the fix had to be done by adding the additional line in the TimeMichine.plist as described by SBeattie2. Just be aware that I needed restart and log in as the root user to make the fix.

I am providing a detailed description of my Mac in case it helps anyone.

Mac Pro Early 2009. 4,1 8core upgrade to:

Mac Pro Mid 2010, 5,1 12 core using firmware upgrade

CPU (Processor) 2 x 3.46 GHz 6 Core

Memory 32 GB 1333 MHz DDR3 ECC

System Software upgrade from Yosemite to El Capitan 10.11 and then to 10.11.1.

System Location; PCIe card: Mercury Accelsior E2, 960GB SSD

Nov 20, 2015 6:45 PM in response to SBeattie2

Thanks for this, been looking for a solution since I upgraded. Never even occurred to me that it could be confused about UPS connection, good call with the plist key. Hopefully they'll react quickly to the bug reports, as unplugging the UPS USB negates half the benefits of using an UPS.

Chief

SBeattie2

Level 2

221 points

Nov 20, 2015 10:03 PM in response to MajorMatt

Yes - you are correct - you can't edit the plist file directly in the /Library/Preferences folder - even if you authenticate as administrator. What I ended up doing - was copy the original plist file to the desktop - edit it on the desktop using Xcode - then rename the original plist in /Library/Preferences (have to authenticate as administrator to do that) - then copy the updated plist from the desktop to /Library/Preferences (have to authenticate as administrator here as well). Sorry that I neglected to include that step in the original instructions.

~Scott

SBeattie2

Level 2

221 points

Nov 21, 2015 9:12 AM in response to cheeseb

Another way to continue to use a UPS and keep the UPS data cable attached - without making any plist modifications is to do the following. This fix is only temporary - in that it only remains in effect until the next reboot - and of course only applies to desktop Macs.

1. Shutdown the Mac.

2. Remove the UPS data cable.

3. Restart the Mac (with the cable still removed)

4. When the login screen appears - re-attach the UPS data cable.

5. Your hourly backups will continue to run. However - beware that workaround only persists until the next reboot. You need to remember to remove the UPS data cable and boot without it being attached in order to restore the hourly backup functionality.

~Scott

Nov 21, 2015 11:09 AM in response to SBeattie2

If you run Xcode with sudo, you can edit it in place with no issues. If you've recently updated Xcode, you'll need to run it normally first to complete the install or the file will still show that it's locked. Then run Xcode via command line: "sudo /Applications/Xcode.app/Content/MacOS/Xcode". Then just use the File, Open menu to browse to "/Library/Preferences" and open com.apple.TimeMachine.plist

Thanks again to Scott for the temp fix!

Chief

lkrupp

Level 7

22,147 points

Nov 21, 2015 7:22 PM in response to SBeattie2

Some users are reporting that OS X 10.11.2 beta 4 fixes the issue.

SBeattie2

Level 2

221 points

Nov 21, 2015 8:09 PM in response to lkrupp

This is good news. Apple has not asked for any further troubleshooting info for the bug report - so I am assuming they got what they needed from me. Hopefully those that are reporting that the 10.11.2 beta is "fixing" the issue - are actually applying the 10.11.2 over a problem installation - and not simply avoiding the problem by doing a clean install. I have never installed any of the developer or public betas - so I can't really provide input. Apple typically doesn't inform the bug submitter (except on rare occasion) that the submitted bug has been fixed - so it's a matter or continuously checking for the fix and then closing the bug report.

~Scott

lkrupp

Level 7

22,147 points

Nov 22, 2015 5:43 AM in response to SBeattie2

I have the same issue being discussed here. I upgraded from Yosemite to El Capitan with the original OS X 10.11.0 installer and applied the OS X 10.11.1 delta update when it came out. Unplugging my UPS brings hourly backups back to life. I don’t normally use beta software but I am tempted to install the public beta to see if it does fix the issue.

R C-R

Level 6

17,794 points

Nov 22, 2015 6:57 AM in response to SBeattie2

SBeattie2 wrote:

Another way to continue to use a UPS and keep the UPS data cable attached - without making any plist modifications is to do the following. This fix is only temporary - in that it only remains in effect until the next reboot - and of course only applies to desktop Macs.

That's what I have been doing (removing the cable while starting up & then plugging it in after login). I don't restart my iMac very often, usually just putting it to sleep when I'm not using it, so this works well for me -- as long as I remember to pull the cable during startup, of course. I can live with this workaround for a while longer, but if the next El Cap update doesn't fix it, I will try your Time Machine pref file hack.

I think another way to apply it would be with a Terminal 'defaults write' command. Using sudo, that would add the key/value pair in place, & avoid the need for installing Xcode for those that don't have or want it. Still another way to edit the file without having to use Xcode is with Pref Setter, a lightweight freeware utility that has a display very much like the Xcode one.

SBeattie2

Level 2

221 points

Nov 23, 2015 1:33 PM in response to R C-R

Thanks R C-R for the suggestion. Somehow using defaults write did not cross my mind - and I think it's a much better solution than editing the plist file (with Xcode) and having to deal with the permission issues in the process. I tested out the following defaults write command and it seems to work well. You have to run it with sudo and authenticate - and then reboot afterward.

For those interested in trying the "defaults write" solution - here it is (I have validated that this works) - be sure to copy exactly as shown here.

sudo defaults write /Library/Preferences/com.apple.TimeMachine RequiresACPower -bool FALSE

Enter the administrator password when prompted by sudo.

To validate that your change was successful - use the "defaults read" command as follows:

defaults read /Library/Preferences/com.apple.TimeMachine RequiresACPower

If successful the defaults read command will return the value as 0.

Be sure to reboot the Mac so that the change takes effect.

~Scott

SBeattie2

Level 2

221 points

Nov 23, 2015 5:07 PM in response to lkrupp

Apple sent a notification today that my bug is a duplicate of another bug and my issue will be closed. Unfortunately they do not indicate whether the other bug report has fixed the problem. We will have to wait and see - thus there could be some validity to the reports that the 10.11.2 beta corrects the problem. At least we have several acceptable workarounds here - while we wait.

~Scott

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Time Machine not doing hourly backups on El Capitan