Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Carbonite Takes Over My Processor!

Hello- Has anyone else noticed that Carbonite sends the processor utilization to over 100%? This seems to be pretty constant and the only way to stop this is if I turn off Carbonite.


Any thoughts or anyone else noticed this?


Thanks!

MacBook Pro, Mac OS X (10.6.5), iMac, MacPro, Mac 128, Newton, Apple II+, Atari 2600

Posted on Jan 5, 2012 8:38 AM

Reply
65 replies

Aug 14, 2017 3:26 PM in response to mr.bill

Add this to your .bash_profile file and you can turn on and off the Carbonite Daemon by command line (handy for turning off when you need to conserve power just remember to turn it back on)


alias CarboniteOff='sudo launchctl unload -w /Library/LaunchDaemons/com.carbonite.launchd.daemon.plist'

alias CarboniteOn='sudo launchctl load -w /Library/LaunchDaemons/com.carbonite.launchd.daemon.plist'

Jan 19, 2012 6:32 AM in response to mr.bill

Same here. Carbonite nearly completely locks up my computer. I can only due very minimal functions and must unintall or disable Carbonite and reboot. So, that is what I do to back up using Carbonite - reinstall it, let it back up and uninstall it once every week or so. I have called them and emailed them - they admit there is a bug but have done nothing. I think it is a conflict with Time Machine but I don't know that for sure. I don't see to many posts on this problem so it may just be something about our setups. But it is a huge problem for me that I cannot find a workaround other than what I mentioned above.

Feb 3, 2012 2:00 PM in response to mr.bill

I've endured this problem since installing Carbonite four months ago and have to do the same as skybax, though I usually only have an error free run for a few days. I notice that there is a lot fo flack about Carbonite not running on Lion, so a Mac OS X upgrade will not help me.


Locking Preferences seems to extend MTBF a few days.


I am considering using Arc but having paid a lot up front for the Carbonite service I hope the bug gets fixed.

Feb 4, 2012 8:13 AM in response to phillmack

Hello- Thanks for the ideas.


I have spent a lot of time with Carbonite's support. I have to say that the support team has really tried and been very good on the phone (once you get past level 1), but in the end, they are only support.


Carbonite clearly has a lack of development ability (or care) when it comes to their mac versions. The processor runs at over 80%. This is even after I have basically deselected everything and am only backing up my documents. Thus, Carbonite isn't very good on the mac since its really only doing the bare minimum. I've Spent too much time on this and am going to give up on them. Carbonite doesn't work well on the mac. I think I'll accept that now.


So... on to other's suggestions...


As for CarbonCopyCloner and SuperDuper.. I know of these, but they are not necessarily automatic and I'm looking for an offsite backup that is basically virtual.


Arc looks incredibly interesting. I'll give that a try and I really appreciate the idea sharing. I'll report back.


Thanks!

Feb 4, 2012 8:20 AM in response to mr.bill

I tested Carbonite long before Lion came out. The part that was the breaking point for me during my testing was the inability of Carbonite to be able to restore databases from Apple products, such as iPhoto and Aperture. It seems that it is too dumb to be able to restore them in a usable format.


I use SuperDuper and I have it schedule to do automatic backups for me.


Allan

Mar 19, 2012 4:41 PM in response to mr.bill

This was happening to me. Very high processor usage with Carbonite. A quick check of their web support pages suggested that a faulty disk sector or somesuch might cause this problem. Restarted with Cmd-R and ran a disk repair. Fixed the disk gremlins. Restarted and Carbonite back to normal - low CPU usage. Problem appears solved. Try checking your disk for problems.


Colin

May 8, 2012 3:23 AM in response to mr.bill

I'll lend my voice to the chorus here... I have used Carbonite on my v10.6.8 Snow Leopard MacBook without much of a problem for more than two years until recently. (If you don't count the trip to the Genius Bar to ascertain why my fan seemed to be constantly running.) Within the past six months, Carbonite has begun to hog most of my processor at very inopportune times.


Recently, it has begun to run backups far too often (and for far too long.) I called Carbonite a few days ago and was passed to a second-level support tech, who I allowed to take control of my computer. I watched as he jumped through the depths of the various Carbonite file trees, deleting files as he went. For a day or two after that, it ran fine again. And then the problem returned.


Last night, for example, it supposedly began a backup at midnight... but five hours later it was still churning away, "backing up." Unless Casper the Friendly Ghost was downloading HD feature films all night, there couldn't have been any new files put on my hard drive that needed to be backed up.


Like many here, my only work-around has been to Pause/Unpause Carbonite, and occasionally Re-Install the application.


Could my MacBook power settings have anything to do with the problem? My settings are set to put both the computer and display to sleep after ten minutes of inactivity. Also, the box labeled "put the hard disk to sleep when possible" is checked. Is Carbonite being stopped when my machine goes to sleep, and restarting when I wake it up?


I don't think that is the issue - the backups still run too often and too long while I'm actively using the machine. But I may change the power settings just to test the theory.


If that doesn't work, I may jump ship to something else for my offsite backup. (I don't back up locally, to another hard-drive. Not since I had one go down and wipe some important photographs.)

May 9, 2012 8:57 AM in response to mr.bill

I couldn't figure out why the fan on my 20" 2008 iMac would run from cold start when all my iMacs have been awesomely quiet. A look at Activity Monitor showed the CarboniteDaemon hogging 196%.

User uploaded file

***? -- I wasn't online and Carbonite was not actively backing-up squat. System Preferences would hang when I went to the Carbonite pane necessitating a force quit. I did a restart and was then able to open System Pref and hit Uninstall, then remove every related file I could find. I can't have a fan running while I'm working on audio or tolerate this sucker punch to the CPU.


I suppose I could back-up with Carbonite week to week by downloading the app, running it and then deleting it each time, but this really defeats the whole purpose of easy back-up, doesn't it? I've paid upfront for three years of Carbonite and I'm not happy about having to troubleshoot and do workarounds.

May 9, 2012 9:17 AM in response to mr.bill

Just as an update since I did the original post:


- I spent many hours trying to fix this incouding a very good effort from Carbonite Support.

- It finally came down to poor engineering and one the Carbonite Support team simply couldn't fix.

- To be clear: Carbonite support was exceptional, but the product is obviously defective.


In the end, I wound up cancel my subscription and uninstalling Carbonite. My machine is MUCH cooler and quieter. I use TimeMachine so I'm ok for now, but I will explore another a competitor's online solution since it adds redundancy.

May 9, 2012 4:30 PM in response to mr.bill

mr.bill and fred briggs et al


I have endured the same problems on my iMac, and had a 3 yr Carbonite subscripton. The good support was there but Carbonite couldn't run for a week on Leopard. I have been using Macs forever and hadn't come across such an irksom program - it was like a Windows virus.


Ended up moving my subscription to a Windows variety - 14Gb backup took +10 days = bottleneck their end.


For my iMac I now use Arq, no dramas.


Phill

Carbonite Takes Over My Processor!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.