Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
After 10.6.1 update remote Time machine will not connect
- Thread starter Europe calling
- Start date
- Sort by reaction score
My situation:
MBP 10.6.1 via ethernet to Time Machine network share (a shared external FW800 drive) on 10.6.1 Mac mini host - OK
MacMini 10.6.1 to same FW800 drive via firewire - OK
PPC MacMini 10.5.8 Server via ethernet to Time Machine network share (a shared external FW800 drive) on 10.6.1 Mac mini host - NOT working, the backup never starts transferring.
MBP 10.6.1 via ethernet to Time Machine network share (a shared external FW800 drive) on 10.6.1 Mac mini host - OK
MacMini 10.6.1 to same FW800 drive via firewire - OK
PPC MacMini 10.5.8 Server via ethernet to Time Machine network share (a shared external FW800 drive) on 10.6.1 Mac mini host - NOT working, the backup never starts transferring.
Time Machine stopped working for me after 10.6.1, too. Contact Apple and let them know about the issue.
http://www.apple.com/feedback/macosx.html
http://www.apple.com/feedback/macosx.html
Time Machine hell
Include me in on this- TM won't backup anymore after SL upgrade! I have tried everything from erasing disk completely ( SL ate all my backup files!) running repair , throwing away prefs and reformatting disk..Have also called Apple 3 times with no help given other than to do a Clean install!!!!
The error message I keep getting is the error 11
Include me in on this- TM won't backup anymore after SL upgrade! I have tried everything from erasing disk completely ( SL ate all my backup files!) running repair , throwing away prefs and reformatting disk..Have also called Apple 3 times with no help given other than to do a Clean install!!!!
The error message I keep getting is the error 11
After calling Apple and jumping through their hoops, the guy finally said he did not know why this happend and that he saw nothing in his database about this being a problem with SL.
I finally had to downgrade to 10.5.8. Backups are working again.
I finally had to downgrade to 10.5.8. Backups are working again.
Time Machine Backup Full
I had the same issue as those discussed here and called tech support. They too were unable to find a solution.
On my own, I did the following and perceive that (1) I no longer see the 'filled up' message and (2) in clicking on the external HDD that I use for the TM backup, I see that backups have been working since that time.
Don't ask me why or to explain how this worked, but: Go to Preferences, click on Time Machine, select Options and then 'UNCLICK' the box entitled 'notify after all backups are deleted'. Maybe this is a 'head in the sand' solution, but it seemed to work for me - or I don't recognize an error anymore!
Bob
I had the same issue as those discussed here and called tech support. They too were unable to find a solution.
On my own, I did the following and perceive that (1) I no longer see the 'filled up' message and (2) in clicking on the external HDD that I use for the TM backup, I see that backups have been working since that time.
Don't ask me why or to explain how this worked, but: Go to Preferences, click on Time Machine, select Options and then 'UNCLICK' the box entitled 'notify after all backups are deleted'. Maybe this is a 'head in the sand' solution, but it seemed to work for me - or I don't recognize an error anymore!
Bob
Ok.. I am also trying this.. Needing desperately to backup my files.. I tried using Backup- this also crashes after just a few minutes of cataloging the files. What's going on ?????
Don't ask me why or to explain how this worked, but: Go to Preferences, click on Time Machine, select Options and then 'UNCLICK' the box entitled 'notify after all backups are deleted'. Maybe this is a 'head in the sand' solution, but it seemed to work for me - or I don't recognize an error anymore!
Bob[/QUOTE]
Don't ask me why or to explain how this worked, but: Go to Preferences, click on Time Machine, select Options and then 'UNCLICK' the box entitled 'notify after all backups are deleted'. Maybe this is a 'head in the sand' solution, but it seemed to work for me - or I don't recognize an error anymore!
Bob[/QUOTE]
Sorry it doesn't work for you - such things can really frustrate one.
As a test, I just now did a test that went as follows: (1) I wrote a junk letter in Word and saved it to the 'desktop'; (2) then I right clicked on the TM icon in the tool bar and selected 'back up now'; (3) after it quit doing the audible action, I double clicked on my external 500 GB HDD that I use for backup, and in the screen that opened from the backup drive I clicked on the 'desktop' icon in the left hand column and the letter I made in step (1) above is the very first item in the middle column. Clicking on it brought it to the screen for any further action.
Also, another method is to click the backup drive, then selecting the backup file shown, then 'users', then 'home' (my name or whatever name given), then 'desktop' and the file I saved is located.
I tried to include an attachment of a screenshot of it, but it wouldn't upload.
Not sure why you are getting the 'crash' you describe, nor why my method worked for me.
Bob
As a test, I just now did a test that went as follows: (1) I wrote a junk letter in Word and saved it to the 'desktop'; (2) then I right clicked on the TM icon in the tool bar and selected 'back up now'; (3) after it quit doing the audible action, I double clicked on my external 500 GB HDD that I use for backup, and in the screen that opened from the backup drive I clicked on the 'desktop' icon in the left hand column and the letter I made in step (1) above is the very first item in the middle column. Clicking on it brought it to the screen for any further action.
Also, another method is to click the backup drive, then selecting the backup file shown, then 'users', then 'home' (my name or whatever name given), then 'desktop' and the file I saved is located.
I tried to include an attachment of a screenshot of it, but it wouldn't upload.
Not sure why you are getting the 'crash' you describe, nor why my method worked for me.
Bob