time machine very slow with mountain lion

How much RAM does your Mac have pls ?

Do you run 10.8.3 ?

Hi

Yes I'm running 10.8.3

And it has 8Gb

And you ran TMdiagnose ?

How to run tmdiagnose

1) Launch Terminal.app (/Applications/Utilities/Terminal.app)

2) Enter the command text below followed by the Return key on the Terminal command line:

sudo tmdiagnose

3) Enter your admin password when prompted and wait for all of the tmdiagnose processes to finish.

4) Attach the output file that looks like this: Username.tmdiagnostic.zip that is written to /private/tmp/ to the bug. This folder should appear automatically when the tmdiagnose processes are completed.

Thanks I'm working away until Friday and will do this as soon as I'm back home.

What will that diagnose?

1tombhome wrote:

I will try to be patient. TM shows backed up 1.82 GB of 19.82 GB after installing ML in about 24 hours. I am using Time Caplsual via wifi to back up.

WiFi is the slowest and least reliable method available to you, not the best choice.

WiFi is certainly slower than a wired Ethernet connection but surely relaibility is not an issue with WiFi. And one shouldn't be required to reconfigure to wired connections to do backups. If that is the case, one might as well dump Time Machine entirely.

Wireless transmission is less reliable than wired, always. It is also significantly slower.

Although the amount of RAM may be a factor in some cases, this is a red herring for my machine which has 8 GB. RAM is cheap and one can install it easily, but it won't solve the problems with Time Machine.

Wireless less reliable? Nonsense. (Guess I'd better just hook up everything with wires, I guess, so I don't drop any bits, huh.)

Believe what you will, the world is still round.

Try to watch your Wireless Speed uning the ALT button and the WiFi symbol in the menubar.

You will get surprised by the low throughput sometimes ...

My equipment hasn't changed since I used to get satisfactory backkups over wireless. That was about nine months ago or so. I was doing incremental backups as large as 15 to 20 gigs at a time (lots of large photos) and it might take one to two hours. It was likely Mountain Lion, but I have no diary of just what changed first before I noticed things weren't working. Then, having gone some time without a backup, I plugged my laptop into the ethernet in order to do a full backup. Before (this problem), such a backup might take half a day for 150 gb; but after (whatever caused this), I get a hopeless estimate as documented by others.

The point being that wireless did work for me, but slowly of course. And switching to ethernet was not a cure. As I said in an earlier post, my wife's MBAir is doing incremental backups via wireless just fine. My machine is an older MBPro and I have a three fairly large Aperture libraries that have a complicated database structure. Something in Mtn Lion or some other update to TM perhaps did not take into account my situation. Perhaps if we can stick to describing what isn't working rather than just whining, maybe we can get somewhere. What do all of us who find TM not working have in common?

Hi again all

Thought i just add my updates!

my MacMini is back to and worce than previously now, despite what Mr Apple told me todo. Tried a wired mouse but still jittery unresponcive keyboard and mouse. Not good!😢

Emailed Apple Support direct again and we will see what they come back with this time!😮

See you on there flip side!

I don't think that he meant unreliable in the sense of dropping bits, but wireless uses more power and more retries to overcome loss do to noise, which is much higher in a wireless network, resulting in significantly lower throughput (even than the bandwidth should theoretically allow).

jshrager wrote:

I don't think that he meant unreliable in the sense of dropping bits, but wireless uses more power and more retries to overcome loss do to noise, which is much higher in a wireless network, resulting in significantly lower throughput (even than the bandwidth should theoretically allow).

The additional retries compared to wired connections are because of dropped data (bits). The network will resend over and over again until the packet is correct, Thus lower performance (wires do the same thing, but have less errors and are faster)