System-wide freeze when Time Machine begins back up - Mac Pro 10.7.5

I have recently upgraded my MacPro Intel Early 2008 to Lion 10.7.5 on an external drive. Overall this nice fresh install has been working very well. The problem is that every 2 hours Time Machine starts its automatic back up and then ...
A) Music playing on Spotify stops
B) Curser freezes
C) Application switching freezes
D) Current app stops working
This freeze typically lasts about 15 to 30 seconds, or until the small incremental back up is finished.
I have verified the cause using the Console and reading the activity. I read the log 4 times yesterday (it has been doing this since I upgraded a week ago) to confirm this activity. Usually the log reports the begin and finish of the backup with no activity in between, but in the freeze I just had there was activity in the middle relating to Spotify. That most recent log is shown below. For the record, nearly all of the log activity is something to do with Spotify unless I am doing some other system level process.
I have studied other threads, but the symptoms don't really match those, or I don't have the same suspect apps installed. I have run Disk Utility and Disk Warrior on the Time Machine internal drive, and it appears ok. In energy settings the hard drive disks are NOT set to sleep when possible, but the computer will sleep after an hour of inactivity.
My Time Machine is getting large and using some 90% of the disc. I think I need to redo it because the old (10.5.8 & 10.6) and new system (10.7) inadvertantly wrote to the same TM backup. Thoughts on that?
Here is the last freeze (I truncated the IP addresses) ... and thanks, I appreciate your help. L
7/12/13 10:54:14.857 AM [0x0-0x1c01c].com.spotify.client: 14:54 I [audio_streamer.cpp:538
] 64k-Latency: 2 ms. Play latency: 484 ms (ap)
7/12/13 10:58:35.743 AM com.apple.backupd: Starting standard backup
7/12/13 10:58:35.771 AM com.apple.backupd: Backing up to: /Volumes/Mac Pro Time Machine/Backups.backupdb
7/12/13 10:58:44.850 AM com.apple.backupd: 6.00 GB required (including padding), 99.59 GB available
7/12/13 10:59:02.068 AM [0x0-0x1c01c].com.spotify.client: 14:59 E [watchdog.cpp:171
] Deadlock detected (Thread: gui)
7/12/13 10:59:07.386 AM [0x0-0x1c01c].com.spotify.client: 14:59 E [watchdog.cpp:191
] The deadlock was a lie! (gui, 10533)
7/12/13 10:59:09.749 AM Firewall: Allow Spotify connecting from 64.55:9907 to port 64429 proto=6
7/12/13 10:59:11.619 AM [0x0-0x1c01c].com.spotify.client: 14:59 E [watchdog.cpp:171
] Deadlock detected (Thread: gui)
7/12/13 10:59:12.739 AM [0x0-0x1c01c].com.spotify.client: 14:59 E [watchdog.cpp:191
] The deadlock was a lie! (gui, 5120)
7/12/13 10:59:16.753 AM Firewall: Allow Spotify connecting from 184.17:65289 to port 64429 proto=6
7/12/13 10:59:16.764 AM Firewall: Allow Spotify connecting from 74.40.0:50925 to port 64429 proto=6
7/12/13 10:59:16.765 AM Firewall: Allow Spotify connecting from 68.41:58285 to port 64429 proto=6
7/12/13 10:59:16.766 AM Firewall: Allow Spotify connecting from 216.23.:1526 to port 64429 proto=6
7/12/13 10:59:16.807 AM Firewall: Allow Spotify connecting from 108.2:59770 to port 64429 proto=6
7/12/13 10:59:16.959 AM Firewall: Allow Spotify connecting from 64.203:62864 to port 64429 proto=6
7/12/13 10:59:16.967 AM Firewall: Allow Spotify connecting from 12.1747:3148 to port 64429 proto=6
7/12/13 10:59:16.986 AM Firewall: Allow Spotify connecting from 76.97.:52319 to port 64429 proto=6
7/12/13 10:59:16.997 AM Firewall: Allow Spotify connecting from 70.114:60921 to port 64429 proto=6
7/12/13 10:59:17.020 AM Firewall: Allow Spotify connecting from 66.214:62861 to port 64429 proto=6
7/12/13 10:59:46.808 AM [0x0-0x1c01c].com.spotify.client: 14:59 I [audio_streamer.cpp:538
] 64k-Latency: 2 ms. Play latency: 31 ms (ap)
7/12/13 11:00:03.592 AM [0x0-0x13013].com.stclairsoft.DefaultFolderX.helper: DFX: Finder query returned error -1701
7/12/13 11:00:12.784 AM Firewall: Allow Spotify connecting from 76.14.156.134:55682 to port 64429 proto=6
7/12/13 11:00:32.831 AM [0x0-0x3a03a].org.mozilla.firefox: NOTE: child process received `Goodbye', closing down
7/12/13 11:00:58.261 AM com.apple.backupd: Copied 2527 files (130.0 MB) from volume OSX Upgrades HD.
7/12/13 11:00:58.779 AM com.apple.backupd: 5.85 GB required (including padding), 99.46 GB available
7/12/13 11:01:04.028 AM com.apple.backupd: Copied 1265 files (2.3 MB) from volume OSX Upgrades HD.
7/12/13 11:01:05.428 AM mds: (Error) Volume: Could not find requested backup type:2 for volume
7/12/13 11:01:05.429 AM com.apple.backupd: Starting post-backup thinning
7/12/13 11:01:05.429 AM com.apple.backupd: No post-back up thinning needed: no expired backups exist
7/12/13 11:01:05.771 AM com.apple.backupd: Backup completed successfully.

Hi Hatter - thanks for the info, interesting. When making these upgrades, which I resisted for as long as possible, I needed to make it as quick and painless, with "minimal" disruption in my work. It still took three weeks to plan and execute, plus it has been a week of fiddling - that is a lot of time to devote to computer maintenance. I kept the original system as a back-up in case things really went south. Also I need 10.5 because I have several active legacy client web sites in GoLive CS2, which I tried in 10.6, but it did not run well.
I agree that doing things off the internal drives is faster to operate, but my approach was prudent. Later I can swap those around. My external 10.7 drive is a WD My Passport Studio, and has had no problems (except the sucker runs pretty hot). I considered the SSD but the price is still high: NewEgg, internal 500GB regular drive today is $60 - 75, 500GB SSD is $340-370. That is a pretty big difference in a small business. I am maxed out on RAM, so that helps a lot.
One last thing though, for the Adobe Creative Suite the scratch discs are the internal drives, so it still runs fast in that sense. Fast is relative ya know, I remember programs taking 40 and 50 seconds to launch, now Photoshop is 19, barely time to drink some coffee.
I have bought a number of UPS over the years, including replacement batteries. It has been expensive frustration, because in a real emergency they seldom do what they promise. In Colorado there are big thunderstorms every summer, and I field tested them a number of times - but was never happy with the protection. Dollar for dollar, investing in a whole house (or whole office) surge arrester at the main utility panel offers protection for the equipment, with about the same amount of time to save your work (which in reality is about 1 second).
I had a ton of connection issues with Spotify working in 10.5, but I am happy to say those have completely gone away with this upgrade. I also like many of the refinements in Lion, such as the improved System Profiler.
Linc, I will will take a look at your suggestion, it is a little vaque. Am I looking for a perticular result ? I don't want to operate for too long with the firewall off.
I think my first step is getting the Time Machine figured out, that could be the whole issue.
Thanks guys for the input -- it is appreciated. L

Similar Messages

Finder Freezing when time machine back up files

I've an 24 aluminium iMac. The finder often freeze (once a day at least) and I noticed that this is often when Time Machine is backing up files.
It's impossible to relaunch the finder and sometimes other mac apps are freezing (preferences etc..). On the dock I can still see that the finder and the apps are active but in fact there are frozen and it is not possible to force quit.
Then if I shut down the computer through the apple menu it doesn't work and the only solution is to shut down manually my iMac with the back button.
Be that as it may it is less frequent since the iMac last software update (graphic card) before everything on the screen was freezing.

I have a 1tb and 540 tb Ultramax Harddrive to support my Mac Pro G5. I originally bought the 650 when the G5 was running Tiger and it worked without fault on a 800 firewire. I partly purchased this model of drive as they advertised its extendibility. When time machine was announced I purchased a second 1tb version and installed the two drives running daisy chained by 800 firewire and they worked fine. Maybe 2 weeks after installing Leopard which had caused me problems because of the application enhancer i was not ready to use time machine so declined to switch it on.
After a few weeks and after the 650 had dismounted itself i started to find after waking from sleep the mac was frozen. There was no way out other than switch it off on the front switch. I later discovered that on powering down the 650 ultramax I could recover my processes but at the danger of corrupting the drive by not removing it properly. As I tried to work out an exit strategy to save data on the 650 I got a system warning to say the Ultramax was beyond repair and was available only to recover files. Eventually it started hanging after a few seconds so i had no choice but to lose data and reformat the drive. That failed and having already contacted Iomega support for advice with little support they eventually agreed the drive had become damaged and agreed to replace the unit.
With the new unit I expected the problem would be gone.. but it was a matter of hours before the symptoms re-emerged, not as bad as before they seemed to allow other apps to continue to run and work it just disabled the finder so i could open an application from recent apps but not through a finder window and if i asked it to open or save a file it would lock the application so much not even a three fingered quit would solve the problem it would close the app in the finder but in the close app window it would remain listed as not responding.. the only way to recover use of the mac was to power off the ultramax almost on loosing power all hanging functions would re-emerge sometimes i needed to switch the mac off.
I decided to risk setting time machine on and although it worked it hung on the first back up and ever since I have woken up the mac as i run a very eco friendly power management policy I would find the hang accompanied by time machine backing up.
I am sure time machine is part culprit in this problem although i cant work out why only the 650 suffers I have tried taking it off firewire and moving to usb and it still does the same....
Any ideas or pointers to an answer of any sort would be welcome

My machine grinds to a near halt when time machine is backing up

My machine grinds to a near halt when time machine is backing up. Is there any way to prevent this?

How much data is it backing-up? Are you making frequent changes to big files? Are you using any 3rd-party apps that store their data in one big file (like a database)? Entourage is one that works that way.
If you're not sure what's getting backed-up, you might want to download the TimeTracker app, from www.charlessoft.com.
It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). Take a look at it for one of the problem backups, to see what's going on.
If you see something you can't identify, post the name(s) here and we'll see if anybody is familiar with them.

When Time Machine is backing up, my computer is so slow that it is essentially useless. Backups occur irregularly, and take a long time.

When Time Machine is backing up, my computer is so slow that it is essentially useless. Backups occur irregularly, and take a long time. How do I get Time Machine to work properly?

Hello,
Have you verified both drives in Disk Utility?
See if the Disk is issuing any S.M.A.R.T errors in Disk Utility...
http://support.apple.com/kb/PH7029
Open Activity Monitor in Applications>Utilities, select All Processes & sort on CPU%, any indications there?
How much RAM & free space do you have also, click on the Memory & Disk Usage Tabs.
Open Console in Utilities & see if there are any clues or repeating messages when this happens.
In the Memory tab of Activity Monitor, are there a lot of Pageouts?

When Time Machine is backing up files, I can't work on other apps

When Time Machine backs up files, I am not able to work on other apps such as Safari. I try to cancel the back up but nothing happens. Then the rainbow-colored wheel appears and I can’t do anything. I have turn off the computer and the external hard drive, restart both and log in. After this happens, I see that Time Machine is no longer backing up anything and I am able to continue work on Safari. What is happening? Should I quit Safari before Time Machine starts backing up files? Please help. Thanks.

to ssis6:
I guess this is something that happens once in a while because Time Machine is backing up files now and I am able to work on Apple Discussions and reply to your post. I just wonder if in addition to your explanation, there is any other explanation as to why what I described happens. Thanks for your help.

Macbook Air Freezes when Time Machine backup starts

My Macbook Air (OS 10.5.5) has started freezing up whenever a Time Machine backup begins. I get the dark shade screen telling me that it has crashed and to hard power off. Everything was working well before, including the Time Machine backups, and the only changes I have made are the Apple updates. At first I thought it was random crashes, but I soon discovered that turning off Time Machine stops the problem (though obviously does not fix it). I've tried restarting and turning Time Machine back on, but it still makes the computer crash within a minute of the start of the backup process. The backup goes to a Time Capsule. I have not seen this problem on any of my other macs on the same network including a Macbook Pro that backs up to the same Time Capsule. Does anyone have any idea what the problem could be and how to fix it?

To be honest,no I don't know why you are having this problem.
It looks like a specific problem with your MBA which could be a hardware problem (RAM most likely here) or a bad sector problem on the hard disk. If you own a copy of TechTool or something similar, run a full hardware systems check. If you don't own TechTool, run the Apple Hardware check from the MBA System install disk.
And, it could be a software problem. I don't know if this sequence will help, but do it anyway because it seems to solve problems on other Leopard systems.
1.) Disable Time Machine back ups
2.) Open Disk Utility and Run Repair Permissions
3.) Run Verify Disk. If it passes go to step 4.
4.) Download the 10.5.5. Combo Updater from http://support.apple.com/downloads/MacOS_X_10_5_5_ComboUpdate
5.) Run the Combo Updater and restart
6.) Run Disk Utility Repair Permissions again
Then enable Time Machine and keep your fingers crossed.
Let me know if any of that helps.

Mac Pro freezes when Time Machine starts backup

MacPro1,1, Lion 10.7.5 (this machine won't run Mountain Lion).
Processor Name: Dual-Core Intel Xeon
Processor Speed: 3 GHz
Number of Processors: 2
Total Number of Cores: 4
L2 Cache (per Processor): 4 MB
Memory: 12 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005D.B00
SMC Version (system): 1.7f10
I'm backing up to a newer 3Tb Time Capsule. When TM backup starts other applications freeze, Force Quit is unaccessible, I have to hold down the power button to shut down. This started about a month after starting to use the Time Capsule, now 2 months old. Here's some log data from when TM starts to the shut down:
9/7/13 9:54:44.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:44.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:44.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:44.560 AM com.apple.backupd: Waiting for Spotlight to finish indexing /Volumes/Time Machine Backups/Backups.backupdb
9/7/13 9:54:45.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:45.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:45.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:45.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:46.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:46.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:46.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:46.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:47.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:47.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:47.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:47.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:48.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:48.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:48.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:48.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:49.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:49.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:49.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:49.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:50.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:50.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
9/7/13 9:54:50.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
9/7/13 9:54:50.734 AM configd: network configuration changed.
9/7/13 9:54:51.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:51.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:51.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 65.
9/7/13 9:54:51.000 AM kernel: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
9/7/13 9:54:52.031 AM configd: network configuration changed.
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
9/7/13 9:54:54.000 AM kernel: ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: Logging in with uam 13 /Volumes/Data
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
9/7/13 9:54:54.000 AM kernel: ASP_TCP ReplayPendingReqs: replaying slot 0 with reqID 2981 afpCmd 0xB on so 0x1e43ce68
9/7/13 9:54:54.000 AM kernel: AFP_VFS afpfs_DoReconnect: get the reconnect token
9/7/13 9:54:54.443 AM SLRuntimeLoader: clip: empty path.
9/7/13 9:54:54.444 AM [0x0-0x17d17d].com.canon.SLRuntimeLoader: Sep 7 09:54:54 My-Mac-Pro-6.local SLRuntimeLoader[3031] <Error>: clip: empty path.
9/7/13 9:54:58.738 AM Address Book: Subscription request completed
9/7/13 9:55:10.581 AM [0x0-0x181181].com.apple.iTunes: 2013-09-07 09:55:10.581 The plugin 'Quartz Composer Visualizer' failed to load because it has the wrong CPU architecture for this version of iTunes. (3585)
9/7/13 9:55:22.038 AM com.apple.backupd: Starting standard backup
9/7/13 9:55:22.066 AM com.apple.backupd: Network destination already mounted at: /Volumes/Data
9/7/13 9:55:33.811 AM com.apple.backupd: Disk image already attached: /Volumes/Data/My Mac Pro (6).sparsebundle, DIHLDiskImageAttach returned: 35
9/7/13 9:55:35.601 AM com.apple.backupd: Disk image already attached: /Volumes/Data/My Mac Pro (6).sparsebundle, DIHLDiskImageAttach returned: 35
9/7/13 9:55:36.791 AM com.apple.backupd: Disk image /Volumes/Data/My Mac Pro (6).sparsebundle mounted at: /Volumes/Time Machine Backups
9/7/13 9:55:36.988 AM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
9/7/13 9:55:55.532 AM com.apple.backupd: 1.77 GB required (including padding), 1.09 TB available
9/7/13 9:57:24.944 AM com.apple.backupd: Copied 3262 files (21.5 MB) from volume Internal 1 3TB.
9/7/13 9:57:31.941 AM com.apple.backupd: 1.92 GB required (including padding), 1.09 TB available
9/7/13 9:58:02.477 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.480 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.482 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.483 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.484 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:02.485 AM mdworker: CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
9/7/13 9:58:26.993 AM com.apple.backupd: Copied 1720 files (304.1 MB) from volume Internal 1 3TB.
9/7/13 10:01:45.000 AM bootlog: BOOT_TIME 1378566105 0
9/7/13 10:01:58.767 AM fseventsd: event logs in /.fseventsd out of sync with volume. destroying old logs. (307606 12 307803)
9/7/13 10:01:59.000 AM kernel: npvhash=4095
9/7/13 10:01:59.000 AM kernel: PAE enabled

Thanks, Linc. Based on earlier posts around the same problem I assumed it was something to do with the computer. TC is up to date and restarting it seems to have corrected the problem, at least during the one TM backup that's gone since.
BTW, I have two internal 3 TB HDs, one with all content, the second which mirrors the first and is updated every night. I'm using the TC/TM as the backup to my backup. I also take a new full copy offsite weekly. Curious though, what do you think of backing up to cloud storage?

My iMac freezes when time machine is running a backup

Hi Guys, this is an iMac that had tiger and I upgraded to 10.5.8
I am using time machine with a 2TB external flex drive from seagate (brand new item)
The back ups went smooth for the first few days but now my iMac totally freezes up at least once a day and the time machine status indcator shows that it is running the whole time.
I tried apple/option/escape but that does nothing so I have to force shut down using the start button on the back of the iMac.
I don't know what to do next so any help would be awesome.

bassplayer360 wrote:
Hi Guys, this is an iMac that had tiger and I upgraded to 10.5.8
I am using time machine with a 2TB external flex drive from seagate (brand new item)
Start by making sure it's set up properly, per #C1 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).
The back ups went smooth for the first few days but now my iMac totally freezes up at least once a day and the time machine status indcator shows that it is running the whole time.
That sounds like something may be corrupted, either on your internal HD or the TM drive. Verify the internal, and repair the TM drive, per #A5 in Troubleshooting
I tried apple/option/escape but that does nothing so I have to force shut down using the start button on the back of the iMac.
If a backup hangs, try to cancel it, either via +Stop Backing Up+ from the TM icon in your menubar, or by right-clicking the TM icon in your dock. If it won't cancel after a few minutes, see #D6 in Troubleshooting.
Then see #A1 for a handy widget that will display the backup messages from your logs. Look at the ones for the backup you cancelled; a clue may be lurking there.
If in doubt, copy and post them here.

Time machine super slow on Mac Pro, had to turn of Spotlight

I ran time machine on a external drive and had no problems for years. I swithed to a larger internal hardrive and the problems began. I read about turning off Spotlight and I did and everything worked fast. But do I need to turn it off with every back up? I'm on lion, did mountain lion fix the issue?

It would probably take 12 hrs to zero (long full format, zero all) a 2TB drive, and especially any that are green, that don't have 7.2k spindle speed.
The USB interface and some external cases when used with TimeMachine "drop off" and stop communicating and act as if they are no longer present. So interface like USB plus variable rpm and the fact that green drives will park the head and 'sleep' regularly, causes trouble.
Disk Utility : Help menu. Tells you how to use Erase or Secure Erase.
Use to be there was format or initialize. Now it is all just erase and erase options.
And even then zero all does not always find or map out a weak sector.
Internal would be native SATA interface and avoid the 'other' interface and the external drive bridge (has to have a bridge to talk to SATA over USB or FW interfaces).

Why am I unable to connect to my airport whenever I put my computer to sleep while the time machine is backing up?

Ever since I installed Lion (version 10.7), I am unable to reconnected to my Time Capsule and get on the internet after I put my computer to sleep and then wake it back up. This doesn't happen all the time -- just when I put my computer to sleep when Time Machine is backing up. If I put my computer to sleep when it's not backing up, it's fine. If it is backing up though, when I wake my computer up again, it is unable to reconnect to the Time Capsule to allow me to use the internet. I have to wake the machine up, click on "Stop Backing Up", wait 30-60 seconds, click "Turn Wi-fi off", wait another 30 seconds, turn it back on and then I am fine. If I just turn wifi off and on without stopping the backup, it doesn't work and I am still unable to connect to the internet. I currently have 10.7.1 but it still has the same bug. 10.6.x did not have this bug. Other than "don't put your computer to sleep when Time Machine is backing up," any suggestions? Any help would be greatly appreciated!

In this case, that hint may help.
According to Apple support, some configuration files may get damaged or corrupt by time, after updates or upgrades and should get deleted ocasionally.
OK ... switch off wifi on the machine.
Then go on and delete the files mentioned below.
You will find the files on your system drive (not your home folder) as follow:
/library/preferences/com.apple.preferences.accounts.plist
/library/preferences/com.apple.preferences.sharing.plist
/library/preferences/SstemConfiguration/preferences.plist
/library/preferences/SstemConfiguration/com.apple.airport.preferences.plist
If there are files in this folders with the same name but additional .orig at the end, delete them too.
It is possible that not all files are on your system. That will be ok.
The files will get newly created by system on reboot.
For that reboot the machine.
Join your wireless again.
If you are using Lion, the Library is hidden. You have to use (menu bar) "go to" -> "go to folder" on finder to access them.
If the problem (unlikely) persists, report back here.
Lupunus
Message was edited by: lupunus (typo's fixed)

Wifi issue - Sleep/resume when Time Machine is active results in lost connection

I was having issues with wifi connectivity to my Time Capsule since upgrading to Lion. I've narrowed down the scenario to having my Macbook go to sleep when Time Machine is backing up. When I later resume, my wifi connection is dead and I have to disable/reenable to connect to the Time Capsule.
Running early 2011 Macbook Pro 15" with OS X Lion.

I am having the same problem.
The only short term fix I have found is to Force Quit Finder (press Alt + Cmd + Esc, or go to menu bar Apple Logo -> Force Quit then select Finder and click Force Quit). Finder then quickly restarts and I am able to reconnect to my WiFi.
I was hoping the latest update, OS X 10.7.1, would have resolved this but unfortuately it has not. I hope Apple can resolve this issue quickly.
Dan
p.s. I can't confirm that this problem only occurs when my mac goes to sleep during a Time Machine back up, simply becuase I have not checked for this. I will try and check and report back.

Our iMac (intel, 11.2) freezes up when using Time Machine for Back Ups. We have 16GB of RAM and the BU drive is 1 TB on firewire.

Our iMac (intel, 11.2) freezes up when using Time Machine for Back Ups. We have 16GB of RAM and the BU drive is 1 TB on firewire.

See Pondini's TM FAQs for starters.

How can I force Time Machine to make a complete backup of my Hard Drive. I just installed a new external drive for Backup since my previous one failed. Now when I back up, Time Machine only backs up my data folder and the Users folder.

How can I force Time Machine to make a complete backup of my Hard Drive. I just installed a new external drive for Backup since my previous one failed. Now when I back up, Time Machine only backs up my data folder and the Users folder.
When I start a backup. Time Machine says "Oldest Backup: None; Latest Backup: None", so it seems like it should do a complete backup, but it only does a partial.

Hi I'd like to jump in here. Your app showed me this:
Time Machine:
          Skip System Files: NO
          Mobile backups: OFF
          Auto backup: YES
          Volumes being backed up:
                    Macintosh HD: Disk size: 749.3 GB Disk used: 453.81 GB
          Destinations:
                    Plastic Wrapper [Local] (Last used)
                    Total size: 999.86 GB
                    Total number of backups: 64
                    Oldest backup: 2013-07-24 23:25:11 +0000
                    Last backup: 2013-11-17 01:40:47 +0000
                    Size of backup disk: Too small
                              Backup size 999.86 GB < (Disk used 453.81 GB X 3)
          Time Machine details may not be accurate.
          All volumes being backed up may not be listed.
          /sbin excluded from backup!
          /usr excluded from backup!
          /System excluded from backup!
          /bin excluded from backup!
          /private excluded from backup!
          /Library excluded from backup!
          /Applications excluded from backup!
Aside from the size of my backup drive, which I will increase at some point, I'd really like to have time machine backing up all system folders, especially Applications. How to I reset this hidden exclusions?
Thanks,
Darcy

When i run Time Machine to back up my computer onto an external hard drive, i have no way of knowing when the back up process has been completed. I don't know when it is safe to disconnect the external hard drive - which is store in a separate location.

When i run Time Machine to back up my computer on to an external hard drive, i have no way of knowing when the back up process has been completed. This is necessary to know because i don't leave my external hard drive connected to the computer. I routinely disconnect it after backing up the hard drive, and then i store the external hard drive in a different location from the computer. So, knowing when the back up process has been completed would be a very helpful thing to have the computer specify.

Just enable Time Machine's menu extra (System Preferences -> Time Machine -> Show Time Machine in menu bar.
This will add a little Time Machine icon to your menubar. When Time Machine is actively backing up your data, the icon will spin as a visual indicator. You can also click the menu icon to see the backup status, including how much data is left to back up.

IMac freezes while Time Machine updates the back up. What to do?

Ever since I upgraded to Lion my iMac freezes or nearly freezes for 5 - 10 minutes every hour while Time Machine updates the back up. What to do?
I have tried everything I can think of but its only improved from total freeze while Time Machine backs up to freeze with an occasional few seconds of activity.
I am really fed up with this.

When I first updated to Lion everything was a mess with freezes happenng constantly like every two or three minutes. Then when looking at the app store I noticed in purchased items that Lion was showing install instead of installed so I downloaded and installed again.
After this install every time Time Machine updated a backup my iMac froze for about 5 or 10 minutes while the backing up was in progress. I was getting really fed up and started this thread. Then one morning I got up and the iMac would not start up. It just sat there with the progress thingy spinning. I started in T mode to look at it from my MacBookPro and two copies of the HD appeared. Both showing zero files. I ran Disk utility on the MacBookPro to try to fix the disk. It showed 8 copies of the disk and all not reparable.
I then created a startup USB drive using my MacBookPro, used it to start up the iMac and restored everything from the previous day's backup. Since then it has been running smoothly with no freezes so maybe the answer is simply to restore a recent backup.
I am using Imation external drives and I don't believe the problem is drive specific.

System-wide freeze when Time Machine begins back up - Mac Pro 10.7.5

Similar Messages

Maybe you are looking for