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

Amnesiac1

macrumors 6502
Original poster
Oct 11, 2010
412
0
Hello,

I recently picked up a portable SeaGate 1 TB HD. It uses USB 3.0, although I doubt my 2007 MBP can take advantage of it (the HD is still compatible with USB 2.0).

Anyways, I am doing my initial back up via Time Machine and it is going very, very slowly. It is backing up 122.97 GB and I usually only transfer approximately 100 MB of data an hour...

What should I do? I already removed my HD and the SeaGate HD from Spotlight indexing.
 
I also had such issues when I made my initial TM backup. After half an hour, only 6 MB had been copied. But suddenly, there was a strong acceleration.

Yes, it might say 100 MB. But that will take a lot of time if it's like 80,000 small files...
 
I also had such issues when I made my initial TM backup. After half an hour, only 6 MB had been copied. But suddenly, there was a strong acceleration.

Yes, it might say 100 MB. But that will take a lot of time if it's like 80,000 small files...

I haven't gotten a boost, though... only errors, which prevent me from being able to leave the transfer on indefinitely. Errors inevitably crop up. I can resume the transfer once said errors appear, but they make it so that I can't leave the transfer on unattended.
 
I haven't gotten a boost, though... only errors, which prevent me from being able to leave the transfer on indefinitely. Errors inevitably crop up. I can resume the transfer once said errors appear, but they make it so that I can't leave the transfer on unattended.

Make sure the disk never goes to sleep in the power settings.
 
Was the drive formatted as OSX's JFS, or is it something like NTFS? That would cause some major slowdown.
 
Also, just so everyone knows, I'm backing up 745, 889 items.

It's currently 'stuck' on 34.3 MB out of 122.65 GB. It should move up ever so slightly in five minutes, and if I'm lucky, I'll make it to 100 MB in an hour. If I'm lucky.

Strangely enough, the transfer was quite fast when I first started... then it crawled down to a snail's pace!
 
Was the drive formatted as OSX's JFS, or is it something like NTFS? That would cause some major slowdown.

When I go to the info for the external HD, it has the following listed beside 'Format': "Mac OS Extended (Case-sensitive, Journaled)".
 
If you just drag and drop a few GB in files to the external how long does it take? You could just have a bum drive.
 
I also had such issues when I made my initial TM backup. After half an hour, only 6 MB had been copied. But suddenly, there was a strong acceleration.

Yes, it might say 100 MB. But that will take a lot of time if it's like 80,000 small files...

BTW, this acceleration occurred after just a half an hour?
 
When I go to the info for the external HD, it has the following listed beside 'Format': "Mac OS Extended (Case-sensitive, Journaled)".

That looks right. Do you use bootcamp at all on your machine? I ask because I've noticed behaviour similar to what you're experiencing whenever OSX has to deal with NTFS formatted partitions.
 
That looks right. Do you use bootcamp at all on your machine? I ask because I've noticed behaviour similar to what you're experiencing whenever OSX has to deal with NTFS formatted partitions.

No Bootcamp.

I did drop my laptop last week, though. Ever since, it's been making an intermittent clicking sound. That's why I'm backing everything up -- I'm having my internal HD replaced soon. I notice that when the back up is in progress, the clicking is more frequent.

So, normally, I'd chalk up the slow pace to the evidently damaged HD. However, two factors make me doubt this: a lot of other people have experienced extremely slow TM progress, and the HD transfers quite well when I manually drag a few GB worth of files over to the external HD.
 
No Bootcamp.

I did drop my laptop last week, though. Ever since, it's been making an intermittent clicking sound. That's why I'm backing everything up -- I'm having my internal HD replaced soon. I notice that when the back up is in progress, the clicking is more frequent.

So, normally, I'd chalk up the slow pace to the evidently damaged HD. However, two factors make me doubt this: a lot of other people have experienced extremely slow TM progress, and the HD transfers quite well when I manually drag a few GB worth of files over to the external HD.
That sound from the HDD isn't good after a drop. Neither is it good that you're getting errors during the Time Machine backup. It is quite possible that running Time Machine -or any cloning routine- puts too much strain on the internal disk if that disk was damaged in the fall. Depending on the errors, it is possible that even if the disk survives until the eventual completion of the Time Machine transfer, the resulting Time Machine Data Base will be corrupt and can be nearly useless as a straight back up to do an automatic restore later on.

If your External drive is big enough -to accommodate a large amount of individual files transferred separately as well as a clone or Time Machine back up - I would stop the Time Machine transfer for the time being (Given the amount of data transferred you will loose little but time by halting the process right now). I would first perform a sort of triage. Concentrate on transferring the most vital personal files manually in relatively large chunks in order of priority. Only after the transfer of these irreplaceable personal files has been completed would I attempt another cloning operation or Time Machine back up from that internal drive.

(Straight Cloning seems more logical to me at this point -after saving your personal files- since Time Machine is more for preserving incremental changes to the files over time and you are going to replace the internal drive soon. Cloning can be done with Disk Utility and doesn't require additional software. I would start using Time Machine from scratch after the Mac has a new internal drive and is running smoothly again)

If the disk was damaged the risk is also there that System files are "damaged" or "corrupt". I would not trust a full restoration to a replacement drive based on a Time Machine Back-up or a clone created from a potentially damaged internal drive like that. System files can be recreated from a OS Installation onto the new drive and it seems like a wasted effort -to me- to try to transfer those to the External Drive at this point.
The only reason to perform a clone right now would be to preserve preference / plists / settings etc that are easily overlooked during a manual transfer of files for back up but most of these settings -to me- have lower priority than personal files that can't be replaced even with time consuming re-configuration of Applications. That's why I would go the route outlined above before I'd do a clone or TM backup where you don't have a say on the order of the file transfer and can't set your priorities.

If you have a way to start the Mac from another start-up volume then you could run the "Repair Disk" routine found under "First Aid" in Disk Utility. That repair may improve the internal drives' performance during back up as well. Couldn't hurt to have a hardware check after a machine is dropped. (Cable connections can become loose, RAM modules can get unseated etc)

P.S.

[At the risk of sounding crude, insensitive, sanctimonious and pedantic ... I'm sure the people who advised you above would agree that info about dropping the computer changes things. I'm sure they would have liked to have that info about dropping the Mac in the OP at the start of the thread - as well as more info about the errors you were getting.

Sorry to say that -as you've now no doubt realized - the incremental Time Machine back-ups should have been made prior to the drop. But you're working to get your files to safety now so Good Luck salvaging your files from a drive that could fail catastrophically at any moment. (Best to presume the worst and be wrong about being "over" cautious. IMNHO.)]
 
Last edited:
How about if you're backing up with CCC? Still slowly? The reason why I'm asking is that for your needs - I.e. to save your files - it doesn't matter which one of the systems you choose.
 
How about if you're backing up with CCC? Still slowly? The reason why I'm asking is that for your needs - I.e. to save your files - it doesn't matter which one of the systems you choose.
Assuming CCC is already installed. Otherwise it requires download and installation of new software (On a drive that may be failing as a result of being dropped.)

Why not advise to use the MAC OS built in cloning abilities of Disk Utility in a situation like this?
 
Assuming you already had a backup in place before the drop, could you not just take a backup of the files you do not already have backed up and try a restore from your last TM backup, then move the files back across onto a new hdd? Or is this your first TM backup?
 
Assuming you already had a backup in place before the drop, could you not just take a backup of the files you do not already have backed up and try a restore from your last TM backup, then move the files back across onto a new hdd? Or is this your first TM backup?

According to the OP it's his "initial backup". That's why there is so much to copy and nothing to recover from.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.