time machine very slow with mountain lion

The guy I talked to from Apple said that is too slow. Originally my backup of about that size was done over night. It's nothing that you did and has nothing to do with network settings etc. Time Machine is broken. Apple realizes this now and is contacting people so they can try and figure out what's wrong.

did some research and did remove a sitecom router out of the same network. reset and reconfigured the time capsule, then it gave me a message that a should put it in bridge mode instead of dhcp, did it and all works fast now, time mache tells me now: 160gb in about 5 hours and the time is running still down!

on this moment 99,5 gb done of 165gb 41 min to go 🙂

also having problems using sparsebundles on network ( afp / cifs )

everything slows down extremely, mounting and ejecting takes forever.. finder hangs..

other afp actions work as expected, worked in 10.7

mikemilligan wrote:

So my conclusion now is that Mountain Lion has a severe issue with networking and/or remote sparse bundles, causing all (or at least much) of our Time Machine backup grief.

My thoughts exactly!

same, same old....tm won't even recognize my old backups.....thank god for super duper.

this has been going on since JULY?!!?

don't EVEN get me started on the ML wireless problem!

I bought recently a brand new Mac Mini i7 with SSD and 4GB internal RAM.

Started TM, and it looked it would last ages to complete.

Then I upgraded the RAM to 16GB, surprise surprise, the TM did compete in 3 hours !!!

So I guess one of the triggers micht be too less RAM.

BTW, with 4GB Ram Mountain Lion runs very sluggish, and I use now at least 8GB in every Mac I have or install for clients, and no one is ever having any problem with TM ...

I talk about more than 100 Macs, some in networks, some as stand alone.

mid - 2012 Rmbp, 16 ram, core i7, ssd, etc.

goodbye ML, hello 2 super duper backup drives.

Well, I managed to force my backup to complete. I noticed that about 9 hours into a 8GB backup, syslogd memory consumption had grown to over 1GB, so I killed it. The backup got faster and finally finished after a few more hours. By then, syslogd ended up taking another 600MB, even after the backup was complete.

So I'm not sure if syslogd memory usage is directly related to TM or if it was causing TM to deprioritize itself due to how much memory it used.

Unfortunately, upgrading RAM is not an option for those with Airs or new MBP's...

I noticed my afp connection is dropping when browsing a sparsebundle file via right click - show package contents. i'm not even trying to mount it and afp gives up..

other afp operations continiue to work fine.

seriously apple, i little tiny bit of testing.....

Feb 20 11:36:06 macmachina kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/MacmachinaBkp

Feb 20 11:36:06 macmachina kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/MacmachinaBkp

Feb 20 11:36:06 macmachina kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 8 /Volumes/MacmachinaBkp

Feb 20 11:36:06 macmachina kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/MacmachinaBkp

Feb 20 11:36:06 macmachina kernel[0]: ASP_TCP ReplayPendingReqs: replaying slot 69 with reqID 31405 afpCmd 0x1D on so 0xffffff80297f2700

Feb 20 11:36:06 macmachina kernel[0]: ASP_TCP ReplayPendingReqs: replaying slot 70 with reqID 31406 afpCmd 0x22 on so 0xffffff80297f2700

Feb 20 11:36:06 macmachina kernel[0]: ASP_TCP ReplayPendingReqs: replaying slot 71 with reqID 31407 afpCmd 0x22 on so 0xffffff80297f2700

Hi guys,

I was experiencing the same problem. A TM backup with a size of about 670 MB took more than 24 hours.

Did some digging and found out that Spotlight's indexing process was running.

Switched it off using:

sudo mdutil -a -i off

TM backup is now back on its original speed, AFAICT.

HTH,

Gerard

Hi Gerard,

does that command switch off indexing only for the backup disk or also for the boot disk? I wouldn't want to lose spotlight...

Time for a resume (https://discussions.apple.com/thread/4145494?answerId=20854329022#20854329022)

Everything works perfect!

I have a MBP 3,1 Core 2 Duo 2,4Ghz.

I've upgraded from 10.7 to 10.8. When I'm trying to use time machine on my time capsule (last gen) with airport express (802.11n) the transmission speed drops from 160/200 to 6/13. (with LAN everthing OK)

Downgrading the IO80211Family.kext from 5.0 to 4.2 using Kext Wizard solved all the problems for me.

Now, 1 1/2 months later, everything still works perfect!

Apple, please dont`t forget the MBP 3,1 Core 2 Duo 2,4Ghz users in your updates!

It switches it of for the boot disk as well. I personally don't mind, cause I use 'Alfred' instead of Spotlight.

Gerard

TM seemed to get hung up at some point during the innaugural back-up (I think it went to sleep while I was getting the power supply hooked up) so I restarted the backup and it wanted to take over a couple million days to complete.....

I was backing up via usb to a Gdrive. New Retna Macbook running 10.8.2

I was able to fix with the classic delete everything and restart manouvre

- deleted the backup folder off the drive

- empty trash

- restart

- bingo

I didn't have to turn off spotlight indexing or anything.

As a professional computer repair technician of over 10yrs, you would be suprised how many issues can be solved with this method...