Very Slow Backup

I have a 500 GB USB hard drive that I can move files to very quickly. When I select it as my Time Machine Hard Drive the the backup runs very slow. According to the tracking bar it's only backing up about 100 MB every 2 min + I stopped spotlight from indexing the drive but it didn't make a noticeable difference. The drive is currently formated Extended but I've tried Extended (Journaled) also. The backup seems to be working and I have not seen a large performance hit. It just seems to be very slow.
Does anyone have an idea what I could have wrong?
Thanks

You probably are not in any danger. The first TM backup has huge amounts of things to do beside just copying your boot volumes data. It builds a data base and collects a bunch of other info to keep track of things.
How much data does Time Machine pref panel show it has to backup ?
Let's say it's 150 GB. Then a USB2 device will get on average around 12 MB/sec. That's some 43 GB per hour. Thus for 150 GB the backup will take 3.5 hrs.
Be patient and let TM backup finish.
Are you see a rotating set of arrows in the Finder side bar to right of your TM backup USB device ? Also, there could be a small backup status window floating about somewhere that shows the backup progress as well.

Similar Messages

VERY slow backup to external Hard Drive

I have an older external HD case (New Motion) with a Western Digital 120GB Hard Drive that I use for backup, firewire only.
I use this drive on my old slot loading iMac G3 (10.3.8) and it runs very fast, copying 16GB from the iMac to the backupin about 15 minutes.
When I connect the backup drive to my G5 iMac (10.4.2) it runs VERY slow at night, taking 6 hours to copy the same amout of information.
I notice that during the day it takes less time, but still about 1.5 hours. (The night/day differences are consistent).
Is this an issue with Tiger or a setting in Tiger or how Tiger talks to firewire, or an issues with the G5 iMac? (Both firewire ports work fine with my iPod updating music).

Hi robfromkinglake west,
Try and isolate the issue. Check if it's only with this drive.
Check the drive with Disk Utility
Using Disk Utility to verify or repair disks
http://support.apple.com/kb/ht1782
I've never seen a drive take 20 minutes to mount.
Nubz

Very slow Backup (Many little file in many subdirectories)

- I have a Netware 6.5 SP8 server with the post SP8 NSS patch installed (NSS version 3.27.01 April 7, 2009)
- iSCSI Initiator Version 1.06.05 October 30, 2008 connecting a 410 GB NSS Volume (Lefthand Networks iSCSI SAN)
- the volume contains user data, and contains, from the Root, a USERDATA directory, which then contains 32,749 individual user directories.
- The majority (90%) of the user directories are empty
- each user directory has it's own trustee assignment, and space restrictions
- compression is enabled
- 376,269 Files using 45,556,460,661 bytes in 221,439 directories so the average would be around 121K per file and as you can see it's very Directory intensive
TSATEST, indicates approximately 850 MB/min result, but when I attempt to back up the data using my backup software (NetVault, which uses NDMP), the performance is hideous. A Full Backup runs around 135k/sec or 8 MB/min (try getting that done in any size backup window) . I have also tried other backup solutions, with the same basic result.
I assume the issue is with indexing, but I'm not sure what to check at this point. I've been trying every suggestion I could find. I've gotten the throughput up to about 1.5M/s, but obviously need better. Just wanted to know if anyone here had any suggestions that might help me to make this function more efficiently, or any TID's that have proven helpful.
Thank You!

Matt Karwowski wrote:
> - I have a Netware 6.5 SP8 server with the post SP8 NSS patch installed
> (NSS version 3.27.01 April 7, 2009)
> - iSCSI Initiator Version 1.06.05 October 30, 2008 connecting a 410 GB
> NSS Volume (Lefthand Networks iSCSI SAN)
> - the volume contains user data, and contains, from the Root, a USERDATA
> directory, which then contains 32,749 individual user directories.
> - The majority (90%) of the user directories are empty
> - each user directory has it's own trustee assignment, and space
> restrictions
> - compression is enabled
> - 376,269 Files using 45,556,460,661 bytes in 221,439 directories so the
> average would be around 121K per file and as you can see it's very
> Directory intensive
>
> TSATEST, indicates approximately 850 MB/min result, but when I attempt
> to back up the data using my backup software (NetVault, which
> uses NDMP), the performance is hideous. A Full Backup runs around
> 135k/sec or 8 MB/min (try getting that done in any size backup
> window) . I have also tried other backup solutions, with the same basic
> result.
>
> I assume the issue is with indexing, but I'm not sure what to check at
> this point. I've been trying every suggestion I could find. I've
> gotten the throughput up to about 1.5M/s, but obviously need
> better. Just wanted to know if anyone here had any suggestions that
> might help me to make this function more efficiently, or any TID's that
> have proven helpful.
>
> Thank You!
Known issue....
http://www.novell.com/support/viewCo...1011&sliceId=1
I have seen this in Java development shops with millions of 1kb files
and folders. The nature of Java.
- Use tar or zip on the local server,not across the wire to compress
those types of data folders.
- Exclude those folders from backup
- Then backup only the zip or tar files.
or maybe look into rsync as I think is copies by hardware blocks not
files?????
- maybe need toreview your environment if it is a development shop like
Java.Maybe switch to GPFS or Reiser for many small files if you can, EXT
could handle it for your small amount of data though.

Time Machine Endless/Very Slow Backup

Hi All,
I've recently encountered a situation in which Time Machine never seems to think it's finished backing up. In the screenshot below you'll see that it's backing up the exact same amount of data from my HD and an external drive called "Movies" (first time 234.6mb & then started again and updated 41.5mb). The thing is, absolutely nothing was changed in the "Movies" drive, it hasn't been touched or synced with anything since the last backup. I'm thinking that's some kind of clue, but not sure what kind of clue it is. I have done many of the things listed here (including "full reset of time machine" and :
https://discussions.apple.com/thread/2057525?threadID=2057525
As well as run Clean My Mac, Repaired Permissions, verified & repaired "Movies" (it was OK), and run Yasu.
Last backup ran for :31min and nothing much had changed. This just started happening recently as outside of major activity TM used to back up in just a few minutes. The good news is the backup was completed successfully, but would love to know what anybody thinks might be the culprit. Oh also backing up to external HD with 1.3TB avail (MB Pro with 750gb HD).

Following the advice of the great Pondini and others, I found a series of steps that worked to correct this situation on ALL my machines!
Here is a link to Pondini's excellent troubleshooting site, which is where I found most of these steps. You might consider just going there and ignoring my steps below, because he is definitely the expert in this field.
http://Pondini.org/TM/Troubleshooting.html
The below is kind of a "nuclear option." Not sure which step does what, but know that after doing all of them my incremental backups are now running at :10 - :20 SECONDS where they were taking 40 minutes to an hour before (be forewarned, it takes a while to do all this).
Turn TM off!
Use Disk Utility "repair disk" function on ALL disks (TM, Mac HD, any others that get backed up). Open Disk Utility, select disk, then select "repair disk."
Instead of #2, you might consider using Disk Warrior to rebuild your directories. It costs about $100, but it's an extremely valuable tool and can save your sauce in many ways. Honestly I would advise buying DW and doing that instead of the Disk Utility option, which, while free, does not seem to be as robust a solution.
An alternative to repairing the TM drive is to just start over with a clean, correctly formatted drive (see below). You should still repair/rebuild your MacHD and any other drives that get backed up, though.
Trash this file: com.apple.TimeMachine.plist (found in MacHD > Library > Preferences).
Repair Permissions on MacHD
In System Preferences > Spotlight > Privacy add MacHD (your main/boot drive) to Privacy pane, close system preferences, then reopen and remove it (add and remove using -/+ at the bottom of the window). This will force Spotlight to re-index MacHD (wait until it's finished to do anything else).
Make sure your TM HD is formatted properly: should be using the GUID partition table (even if it's not partitioned) and be formatted Mac OS Extended (Journaled). These settings will appear at the bottom of the Disk Utility window when you select the HD itself (not by its volume name). If you are not formatted this way, it's recommended that you reformat. Unfortunately, this means your existing backups will be no more (unless you have another drive you can use and preserve the old one until you're safely backed up again).
Reset PRAM. Restart your mac and hold down these keys simultaneously: option command p r. Hold them down until you hear the second "restart" chime.
Enter TM preferences and re-select TM disk (when you trash plist TM will "forget" the drive, but all the info is still on the drive) but don't let TM run yet.
In TM options make sure any disks you prefer to exclude/include are either entered or not (TM HD should always & automatically be excluded)
In System Preferences > Spotlight > Privacy make sure TM disk is excluded from Spotlight (using +/- as above).
Finally, enter Time Machine and go through your backups to see if there are any backups that shouldn't be there: should be one backup every hour for the past day, one backup every day for the past month and weekly backups before that. If you find more than one backup on a day 3 weeks ago, for example, delete all but the most recent one for that date (on the window of the backup you want to delete you should see the "gear" icon with a dropdown arrow - click on it and select "delete backup."). You have to delete them one at a time so depending on how many you find & how big your backups are this step can take a very long time but it's critical to making sure TM doesn't get hung up on the "finishing" phase. If TM looks back in time and finds more backups than it wants it's supposed to just delete them but it doesn't always work that way and that's one of the issues that can make the finishing stage of the backup take forever.
Restart your Mac.
Restart TM & hope for the best.

Solaris 10 server(v490) very slow backup

Recently deployed Solaris 10 server(v490) into env consisting of SBU server solaris 8 (Networker 7.3). Solaris 10 system is only backing up at a rate of 125 or less Kbytes/sec. 3 other machines(solaris 8) are backing up at a rate of 17 to 20 Mb/sec. The switch that they are connected to is set to 100mbs, full duplex. When I do an "ndd -get ???", all 1's are displayed. 100hdx, 100fdx, autoneg......
Should I execute commands to make it run100fdx? If so, what are the ndd commands(if i should still use ndd)?
please email me at "[email protected]".

You can force the NIC to use onlu 100fdx like this: (in an RC-script or so)
(Pls. verify that the switch is able to realy leverage 100fdx. (Quite a few of the older switches can't, even if they say so)
Otherwise You may force each end to use half duplex)
ndd -set /dev/hme instance 0
ndd -set /dev/hme adv_100fdx_cap 1
ndd -set /dev/hme adv_100hdx_cap 0
ndd -set /dev/hme adv_10fdx_cap 0
ndd -set /dev/hme adv_10hdx_cap 0
ndd -set /dev/hme adv_autoneg_cap 0
or in /etc/system (for all hme instances) :
set hme:hme_adv_100fdx_cap = 1
set hme:hme_adv_100hdx_cap = 0
set hme:hme_adv_10fdx_cap = 0
set hme:hme_adv_10hdx_cap = 0
set hme:hme_adv_autoneg_cap = 0
/Ulf

Backup to the remote stages is very slow

Hello!
I am facing with the following problem for DB Backup to the remote stage.
If I plan the ALL ONLINE-Backup, then the backup is takes very slow, backups two or more files and aborts.
I have checked the appropriate BTC WP and saw that the WP is holding/waitng.
The reason is RFC.
How can the problem be solved?
Thank you very much!
regards
Thom

Without logs of the backups we can just guess, what is wrong.
Post the log of a failed remote backup here and let´s see then.
Markus

Time Capsule external drive very slow for backup

I am experiencing very, very slow backup times using an external drive attached to my Time Capsule. When I recently added a 3 TB Rocstor external drive to my mid-2011 iMac using FireWire, I included it in the drives to be backed up. The internal 2 TB of storage in my Time Capsule was no longer enough, so I plugged a 4 TB WD My Book Studio drive into the Time Capsule's USB 2.0 port and specified this WD drive as the only backup storage. The first backup took almost 48 hours. Now the Time Machine keeps trying to back up about 400 GB - 500 GB (though there haven't been any changes) and is transferring about 400 KB/sec over Ethernet from my iMac to the Time Capsule's external drive. What am I doing wrong? (I recently upgraded the iMac to OS X 10.10.2 Yosemite.)

Frankly, I have no way to gauge your network setup, so I can't really tell you what you should expect. I can tell you from my own experiences using a local network based on a 3rd Gen. Gigabit Ethernet AEBS that using Ethernet the average throughput (not interface) was in the neighborhood of 16-20 MBs/sec. The average throughput for a USB 2.0 drive connected directly was about the same.
This works out to an average throughput of around 60 GBs/hour. Depending upon file sizes and number of files being transferred a USB 2.0 drive might reach 100 GBs/hour, but that is a rare outcome. The USB 2.0 drive interface speed is about the same as FireWire 400 - 400 Mb/s or roughly 50 MBs/sec. This is what I know from measurement. Do not expect Ethernet to be any faster for throughput.

Time Capsule / Time Machine very very slow

I'v been having problems with very slow backups using a Time Machine / Time Capsule combo and I've been looking around this forum and the web in order to figure out what it is, but I couldn't find any specifics relating to my situation. Both the preparation and the backing up stages are both very slow.
I hadn't used Time Machine since before Christmas as it become unreliable after updating to Yosemite but thought I'd try and get backups running again. It took about 16 hours to complete it's first backup of 17gb, then today's backup of 475.9mb took 4 hours to prepare and it's only backed up 167.7mb as I write this.
Can anyone with a good technical understanding of OS X, Time Capsule & Time Machine backups tell me what the problem is by looking at the console output below?
Hope someone can help, thanks.
Specs are:-
MacbookPro early 2011
OS X 10.10.1 Yosemite
Time Capsule- 4th gen 2TB
Console:-
Feb 4 00:27:32 xxxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Ejected Time Machine disk image: /Volumes/Data-1/xxxxxxx MacBook Pro.sparsebundle
Feb 4 00:27:33 xxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Ejected Time Machine network volume.
Feb 4 00:27:33 xxxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Running automatic backup verification.
Feb 4 00:27:33 xxxxxxxMacBook-Pro-2.local com.apple.backupd[135]: Attempting to mount network destination URL: afp://xxx%20xxxxx;AUTH=SRP@xxxxxxxx%20Time%20Capsule._afpovertcp._tcp.local/Dat a
Feb 4 00:27:33 xxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Mounted network destination at mount point: /Volumes/Data-1 using URL: afp://xxx%20xxxxx;AUTH=SRP@xxx%20xxxxxx%20Time%20Capsule._afpovertcp._tcp.local /Data
Feb 4 00:28:04 xxxxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Verifying backup disk image.
Feb 4 00:32:50 xxxxxxxx-MacBook-Pro-2.local com.apple.backupd-helper[44]: Not starting scheduled Time Machine backup: Backup already running
Feb 4 08:56:30 localhost com.apple.xpc.launchd[1] (com.apple.backupd-status): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Feb 4 08:56:30 localhost com.apple.xpc.launchd[1] (com.apple.backupd.status.xpc): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Feb 4 08:56:30 localhost com.apple.xpc.launchd[1] (com.apple.backupd-helper.status): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
Feb 4 08:56:30 localhost com.apple.xpc.launchd[1] (com.apple.backupd-auto): This service is defined to be constantly running and is inherently inefficient.
Feb 4 08:56:58 xxxxxx-MacBook-Pro-2.local backupd[133]: Property list invalid for format: 200 (property lists cannot contain NULL)
Feb 4 08:56:59 xxxxxx-MacBook-Pro-2.local backupd[133]: Property list invalid for format: 200 (property lists cannot contain NULL)
Feb 4 08:57:00 xxxxxxx-MacBook-Pro-2.local backupd[133]: Property list invalid for format: 200 (property lists cannot contain NULL)
Feb 4 08:57:10 xxxxxxx-MacBook-Pro-2.local backupd[133]: Property list invalid for format: 200 (property lists cannot contain NULL)
Feb 4 08:57:20 xxxxxx-MacBook-Pro-2.local backupd[133]: Property list invalid for format: 200 (property lists cannot contain NULL)
Feb 4 08:59:24 xxxxxx-MacBook-Pro-2.local SystemUIServer[224]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
Feb 4 08:59:24 xxxxxxx-MacBook-Pro-2.local com.apple.prefs.backup.remoteservice[370]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
Feb 4 09:26:41 xxxxxxx-MacBook-Pro-2.local com.apple.backupd-helper[44]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
Feb 4 09:27:11 xxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Starting automatic backup
Feb 4 09:27:11 xxxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Attempting to mount network destination URL: afp://xxx%20xxxxxx;AUTH=SRP@xxxxxxxx%20Time%20Capsule._afpovertcp._tcp.local/Da ta
Feb 4 09:27:13 xxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Mounted network destination at mount point: /Volumes/Data-1 using URL: afp://xxxx%20xxxxx;AUTH=SRP@xxxxx%20xxxxx%20Time%20Capsule._afpovertcp._tcp.loc al/Data
Feb 4 13:06:27 xxxxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Disk image /Volumes/Data-1/xxxxxxxxs MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Feb 4 13:06:40 xxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Backing up to /dev/disk3s2: /Volumes/Time Machine Backups/Backups.backupdb
Feb 4 13:39:28 xxxxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Will copy (323.4 MB) from Macintosh HD
Feb 4 13:39:28 xxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: Found 7354 files (432.7 MB) needing backup
Feb 4 13:39:28 xxxxxxx-MacBook-Pro-2.local com.apple.backupd[638]: 799.1 MB required (including padding), 563.6 GB available

Feb 4 08:56:30 localhost com.apple.xpc.launchd[1] (com.apple.backupd-status): The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.
There is an 8 hour gap between this message and the one before it.
This message is related to the use of encryption. If you are still getting it even after you have turned encryption off then something is still hanging around. And it is a big problem.
The previous log entry that it may also be the concern is
Feb 4 00:28:04 xxxxxxxx-MacBook-Pro-2.local com.apple.backupd[135]: Verifying backup disk image.
So it is doing a full verify of the backup.. that is extremely time consuming over wireless. It takes much longer to verify than to do the backup. That is because of the long gap since the last backup. When you wait so long it is sometimes better to simply start over.
It is essential when this happens to be using ethernet with wireless turned off.
Make sure IPv6 is set correctly to link-local only in the ethernet settings of the computer.
Why your latest one is so slow is again a Yosemite bug mystery.
However I would like you to test actual network speed copying files to the TC.
Stop the present backup.. if it is still running. Then via finder simply copy a file to the TC hard disk.. a single very large file say 100-1000MB and give me a network speed using activity monitor.
Yosemite has real network issues on top of real TM issues.
Test by doing a TM backup to a USB drive plugged into the computer. If this is dramatically faster the issue is mostly network rather than TM.
If it still fails to backup in reasonable time periods.. and for people having big issues.. I recommend give up on TM until apple have managed to patch the bugs. Use an alternative like Carbon Copy Cloner.. I would do that even if TM does work if you want a backup you can trust.

Slow backup process:10mb for 50mins

Dears,
I have a early 2008 macbook pro 15" with snow leopard, and a 500G time-capsule(1st edition,firmware 7.4.1).
They worked fine in the past 3 years.
However I found my backup process became very slow about 2 months ago, I checked the log below and it shown that it took 50mins to backup just 10mb data.
2012/2/3 下午12:29:17
com.apple.backupd[6441]
Starting standard backup
2012/2/3 下午12:29:17
com.apple.backupd[6441]
Attempting to mount network destination using URL: afp://%E8%B3%B4%20%E5%BD%A5%E5%BB%B7@Time%20Capsule%20b7dd24._afpovertcp._tcp.l ocal/Time%20Capsule%20HD
2012/2/3 下午12:29:18
com.apple.backupd[6441]
Mounted network destination using URL: afp://%E8%B3%B4%20%E5%BD%A5%E5%BB%B7@Time%20Capsule%20b7dd24._afpovertcp._tcp.l ocal/Time%20Capsule%20HD
2012/2/3 下午12:29:29
com.apple.backupd[6441]
QUICKCHECK ONLY; FILESYSTEM CLEAN
2012/2/3 下午12:29:35
com.apple.backupd[6441]
Disk image /Volumes/Time Capsule HD-1/“賴彥廷”的 MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine 備份 1
2012/2/3 下午12:29:35
com.apple.backupd[6441]
Backing up to: /Volumes/Time Machine 備份 1/Backups.backupdb
2012/2/3 下午12:34:52
com.apple.backupd[6441]
No pre-backup thinning needed: 1.60 GB requested (including padding), 228.09 GB available
2012/2/3 下午12:48:25
com.apple.backupd[6441]
Copied 25495 files (9.2 MB) from volume Macintosh HD.
2012/2/3 下午12:54:31
com.apple.backupd[6441]
No pre-backup thinning needed: 1.60 GB requested (including padding), 228.03 GB available
2012/2/3 下午1:06:11
com.apple.backupd[6441]
Copied 23101 files (1.9 MB) from volume Macintosh HD.
2012/2/3 下午1:17:50
com.apple.backupd[6441]
Starting post-backup thinning
2012/2/3 下午1:17:50
com.apple.backupd[6441]
No post-back up thinning needed: no expired backups exist
2012/2/3 下午1:17:52
com.apple.backupd[6441]
Backup completed successfully.
2012/2/3 下午1:17:59
com.apple.backupd[6441]
Ejected Time Machine disk image.
2012/2/3 下午1:18:00
com.apple.backupd[6441]
Ejected Time Machine network volume.
The wifi connect is fine because the video stream is good.
I think it's just because there are some small files make time machine to process, but I have no idea where can I find these files (or logs).
any ideas?

Pondini wrote:
Sounds like something there might not be compatible, or damaged, or something.
See what the log shows -- if TM was doing a "deep traversal," it's probably normal.
the log is here
Copied 79596 files (2.6 GB) from volume Macintosh HD.
No pre-backup thinning needed: 1.51 GB requested (including padding), 81.69 GB available
Copied 79181 files (1.9 MB) from volume Macintosh HD.
Starting post-backup thinning
Backup completed successfully.
TM is not doing deeptraversal.
I'd say, first, double-check the things you did that seem to have caused the problem.
If it all seems fine, try Verifying your internal HD and Repairing your backups, per #A5 in Time Machine - Troubleshooting, to be sure it isn't some sort of directory problem.
If still no help, a few folks have had a somewhat similar problem (very slow backups with huge file counts) with 10.6.8; many managed to solve it by reinstalling OSX, but only going back to 10.6.7 via that "combo." Just why is a mystery, unfortunately.
You are right, I should double-check the problem.
I will try your suggestion, and thank for your reply

Slow backup - A Potential Culprit Found

For those of you who have been suffering from slow back ups in UK then I have finally found the culprit on my build. With all of the updates to iOS over the last couple of weeks backing up was becoming a real pain with a reasonable performance until the last ~10% before it almost stopped and took hours.
The culprit after much troubleshooting seems to have been "The Times" newspaper app. Over time you build up a cache of daily editions (~60Mb a day possibly) which seem to gum up back up.
If you go to the Settings for the app you can chose to clear the cache next time you open the app and doing this just before backing up resolves the issue.
Hopes this helps make some of your lives easier!

Pondini wrote:
Sounds like something there might not be compatible, or damaged, or something.
See what the log shows -- if TM was doing a "deep traversal," it's probably normal.
the log is here
Copied 79596 files (2.6 GB) from volume Macintosh HD.
No pre-backup thinning needed: 1.51 GB requested (including padding), 81.69 GB available
Copied 79181 files (1.9 MB) from volume Macintosh HD.
Starting post-backup thinning
Backup completed successfully.
TM is not doing deeptraversal.
I'd say, first, double-check the things you did that seem to have caused the problem.
If it all seems fine, try Verifying your internal HD and Repairing your backups, per #A5 in Time Machine - Troubleshooting, to be sure it isn't some sort of directory problem.
If still no help, a few folks have had a somewhat similar problem (very slow backups with huge file counts) with 10.6.8; many managed to solve it by reinstalling OSX, but only going back to 10.6.7 via that "combo." Just why is a mystery, unfortunately.
You are right, I should double-check the problem.
I will try your suggestion, and thank for your reply

4Th Generation Time Capsule Running Backup very Slow

I am having a problem with my 4th generation time capsule as it is running very slow , it shows that i need to backup 151 Gb data and for the last 2 days the device backup only 150 mb, pls advise what is the problem? setup of the wireless network seems fine to me without any problem
please help

When you use ethernet, make sure your wireless is turned off in the computer.
It can be worthwhile isolating the TC to the Computer so there is nothing else happening.
Also for Mavericks ensure you have ipv6 set correctly to link-local.
A 100GB backup certainly should not take 20hours..
Although the 2008 (gen1 TC is much slower than later versions).
A first backup of the computer must deal with loads and loads of little files, as a warning can go slow.
A different backup software will be just the same.. it is the speed over network and handling small files that is the issue. Once that first backup is done the later incrementals should not be a problem though.

Time machine backup is very slow after migration to Mountain Lion

After I migrated to mountain lion, Time machine backup is very slow. Time machine preference says there is no previous back up although I had Time machine on before migration. It did not help verymuch to connect an ethernet cable between my timecapsule and my Macbook Pro
Here are the screenshots I see:
Should I erase the previous backup made on Lion before backing up on Mountain lion? in this case how do I transfer the Lion backup file on another disk just in case something goes wrong before I have a good backup under Mountain Lion? just like any other file?

After further reading on the forum, the problem was solved: I used the possibility to back up on a second disk (in the preferences Time Machine choose a disk and save on both disks) to make a back up on another usb disk, and then erased the old .sparsebundle file on my Time Capsule. I have then re defined time capsule as the back up disk and then the backup was muuuuuch faster (one night instead of less than 1 giga after 3 days.....)

When i start my hot backup my database getting very slow

Hi,
I am using following commands for enabling hot backup
SQL>ALTER SYSTEM ARCHIVE LOG CURRENT;
SQL>ARCHIVE LOG LIST;
SQL >ALTER DABATBASE BEGIN BACKUP;
Database altered.
SQL>SELECT FILE#,STATUS FROM V$BACKUP;
FILE# STATUS
1 ACTIVE
2 ACTIVE
3 ACTIVE
4 ACTIVE
and using cp -rp command to copy the file (backup copying speed good) but database performance very slow
How to improve performance ...
Regards
Vignesh C

Uwe Hesse wrote:
It is very likely that you experience slow performance with ALTER DATABASE BEGIN BACKUP , because until you do ALTER DATABASE END BACKUP , every modified block is additionally written into the online logfiles . Doesn't that happen only the first time the block is modified?
>
The command was introduced for split mirror backups, when this period is very short. Else ALTER TABLESPACE ... BEGIN/END BACKUP for every tablespace one at a time reduces the amount of additional redo during non-RMAN Hot Backup. There appear to be only 4 files. We don't know how big or sparse they are.
>
RMAN doesn't need that at all - much less redo - and also archive - generation then.
Furthermore, you can use BACKUP AS COMPRESSED BACKUPSET DATABASE to decrease the size of the backup even more - if space is an issue.
In short: Use RMAN :-)
Agree with that! Unless the copy is actually going to an NFS mount or something, where I would be concerned whether it is the type of NFS that Oracle likes. I'd also advise a current patch set, as the OP didn't tell us the exact version, and I have this nagging unfocused memory of some compression problems of the "oh, I can't recover" variety.
I'd like to see some evidence on I/O and cpu usage before giving advice. When I used to copy files like this, it would choke out everyone else. RMAN was a savior, but had to wait for local SAN upgrade.

Backup to TimeMachine with WI FI is very slow!

Backup to TimeMachine with WI FI is very slow!
I set the backup with TM but backups and slow
We can Help Me ?

alexrav wrote:
Backup to TimeMachine with WI FI is very slow!
I set the backup with TM but backups and slow
We can Help Me ?
Yes, WIFI is slow. If this is your first backup, it will be much faster if you connect to your Time Capsule or Airport Express via an Ethernet Cable.
Also try the things in item #D2 of the Time Machine - Troubleshooting *User Tip* at the top of this forum.

When I connect an external hard drive to macbook pro it is very slow to appear on the desktop and Finder window, sometimes 20 mins or more, even with auto backup switched off . any clues?

when I connect an external hard drive to macbook pro it is very slow to appear on the desktop and Finder window, sometimes 20 mins or more, even with auto backup switched off . any clues?

Hi robfromkinglake west,
Try and isolate the issue. Check if it's only with this drive.
Check the drive with Disk Utility
Using Disk Utility to verify or repair disks
http://support.apple.com/kb/ht1782
I've never seen a drive take 20 minutes to mount.
Nubz

Very Slow Backup

Similar Messages

Maybe you are looking for