Previous 1 2 3 4 5 6 Next 206 Replies Latest reply: Jun 14, 2010 8:57 AM by lolondonkb Go to original post
  • Sandman Level 4 Level 4 (3,270 points)
    Have you tried manual backups? It's worked fine for me.
  • henry67 Level 1 Level 1 (0 points)
    Well, I have waited some days before come back, because I wanted to have as much infos as possible.
    I erased my old backup and started over.
    It took a very long time (about 16 hours!) for the first backup and it wasn't still finished that the AEBS disk was expelled, then I rebooted it and instructed TM to perform the backup: TM recognized the previous backup not finished yet and after another 8 hours the backup was finished.
    Since I'm at home on vacation, I have left my MBP on with TM on, to let it perform hourly backups and I have to say that it's more than 2 days that TM is working good, performing hourly backups flawlessly.
    I'll have to check what will happen the first time I'll bring the MBP to office, that means disconnect the MBP from my home network, connect it to my office network, and that back home; I'll keep you informed.
    I have noticed that the first huge backup created a sparsebundle file, but now after several incremental backups, I have a Backups.backupdb folder that contain all the backups (same like when the HD was connected to the USB).
  • Harv Nagra1 Level 1 Level 1 (65 points)
    It's horrible that this issue isn't being resolved, and so many of us are having issues. I have a feeling that this configuration is only "not supported" because Apple doesn't want to deal with 3rd party hardware, or take responsibility for the configuration not working... regardless of whether it's their own software, NOT the 3rd party hardware that's causing the issue.

    It's frustrating that it works for quite a while seamlessly and then you have to start from scratch.. I'll probably be reformatting my backup disk for the 3rd time now and starting over since SL... some are suggesting manual backups are the way to go, so I'll give that a shot.

    (Is there any hope in waiting a few weeks to see if a SL update or a miracle magically fixes it...or is that wishful thinking?)
  • tincha Level 1 Level 1 (40 points)
    Sandman, what do you mean by "manual backups?" Do you mean "wired" instead of "wireless" -- or something else?
  • Michael Steen Level 1 Level 1 (5 points)
    Argh, I too have this problem, but running on a Time Capsule, so not even vaguely attempting anything unsupported.

    Despite some glitches in the past, wireless Time Machine backups were running fine for months under Leopard and even for several weeks under Snow Leopard... But at the weekend I noticed that the Time Capsule was running firmware 7.4.1 and let it upgrade to 7.4.2. And since then, the dreaded 109 error message. (I am not saying I can prove there's a correlation but to the best of my knowledge the firmware update is the only thing that changed from the time that Time Machine backups worked to when they did not.)

    Haven't tried hard wiring the Time Capsule to iMac to see if that works as the Time Capsule is in a cupboard in another room, acting as wireless router... (Which is kind of the point.)

    Error message: "Time Machine could not complete the backup. The backup disk image "/Volumes/TimeCapsule-1/..." could not be accessed (error 109)."

    Can't repair permissions for some reason. Can't mount the sparsebundle. Tried changing disk name from Time Capsule to TC as per this support doc (https://support.apple.com/kb/HT1170) but to no avail.

    To be honest Time Capsule fails the "just works" test in a very big way.
  • mikeraburn Level 1 Level 1 (0 points)
    Here is some info that may help Apple people (you are reading this I hope). I am running a non-Time Capsule external hard drive with my Airport Extreme 802.11n (firmware 7.4.2) and using it to wirelessly backup TWO different laptops: a 2.2 Ghz Intel Macbook running SL 10.6.1, and a 1.5 Ghz PPC G4 Powerbook running Leopard 10.5.8. The G4 PB is still backing up fine, it is only the MB that is getting the 109 error. The MB was updating fine for a while, so I know my configuration is good.

    This leads me to conclude that there is some hitch in the interaction between firmware 7.4.2 (when all this started) and SL (the only OS affected by it).
  • Pondini Level 8 Level 8 (38,720 points)
    mikeraburn wrote:
    Here is some info that may help Apple people (you are reading this I hope).


    No. This is a user-to-user forum. If you want Apple's attention, call AppleCare (800-275-2273). You can also make an appointment at the Genius Bar of your local Apple Store, but their expertise with TM is limited.

    I am running a non-Time Capsule external hard drive with my Airport Extreme


    As has been mentioned several times earlier in this much-too-long thread, that is not supported by Apple: http://support.apple.com/kb/HT2038

    They have tried to help some folks with this, but will remind you that it's not supported.
  • Pondini Level 8 Level 8 (38,720 points)
    Michael Steen wrote:
    . . .
    Error message: "Time Machine could not complete the backup. The backup disk image "/Volumes/TimeCapsule-1/..." could not be accessed (error 109)."

    Can't repair permissions for some reason. Can't mount the sparsebundle. Tried changing disk name from Time Capsule to TC as per this support doc (https://support.apple.com/kb/HT1170) but to no avail.


    Try changing your System Name, too. For both of them, omit any spaces, punctuation, or unusual characters (use numbers and letters only). For some reason, that sometimes helps.

    You may have to erase the TC and let TM start over. Use the +*Airport Utility+* app, in your Applications/Utilities folder. Select Base Station > Manual Set-Up from the Menubar, then Disks in the tool Bar, then Erase.

    If all else fails, there may be something wrong with the TC or the disk inside it.
  • Michael Steen Level 1 Level 1 (5 points)
    Pondini wrote:

    You may have to erase the TC and let TM start over.


    Many thanks for the advice. Actually, I took a deep breath earlier and deleted the sparsebundle for my iMac and started a new backup. It's wireless so will take a while. Didn't want to go for the nuclear option yet of a full erase of the TC as it was still happily backing up my wife's MacBook and that would just have doubled the time needed for a new initial backup.

    I do wish they could get this right though. The point of a backup is that I expect it to be there if the primary drive goes down. With Time Machine and Time Capsule it too often feels like I worry about the backup going bad, which is the wrong way round. (Though, granted, any drive can fail at any time -- but what seems to be failing here is not the drive but the protocols to suspend backups when the computer goes to sleep but TM is still doing an incrememental backup.)
  • mikeraburn Level 1 Level 1 (0 points)
    Pondini wrote:


    As has been mentioned several times earlier in this much-too-long thread, that is not supported by Apple: http://support.apple.com/kb/HT2038


    I have read that bulletin, but it must be out-of-date since it states that the Airport disk cannot be used by TM, which used to be the case, but is no longer the case. You can now use an Aiport connected disk to backup both in Leopard and in Snow Leopard.

    And this thread is overly long because the problem is not resolved yet. No amount of renaming or blaming hardware is going to address this issue. Read my setup again. It's working fine in Leopard, just not in SL. This is an issue with the OS.
  • Pondini Level 8 Level 8 (38,720 points)
    mikeraburn wrote:
    . . .
    I have read that bulletin, but it must be out-of-date


    It's dated July 15, 2009.

    Yes, it often works, in both Leopard and Snow Leopard. I'm doing it myself, on Snow Leopard.

    But it is still unsupported.
  • Danire Level 1 Level 1 (5 points)
    Pondini wrote:
    mikeraburn wrote:
    . . .
    I have read that bulletin, but it must be out-of-date


    It's dated July 15, 2009.

    Yes, it often works, in both Leopard and Snow Leopard. I'm doing it myself, on Snow Leopard.

    But it is still unsupported.


    Sorry, but the argument that it is unsupported doesn't hold any water here. Read the above posts from people using a Time Capsule and Time Machine and getting the 109 error. Backing up with Time Machine to a Time Capsule is unsupported?? I think not. This is a SL bug.

    I wouldn't suggest using Time Machine under SL even it appears to be working again. Backups are too important. Use SuperDuper, CCC, or ChronoSync until Apple gets their act together and gets this fixed. And even then, use redundant backups.
  • Pondini Level 8 Level 8 (38,720 points)
    Danire wrote:
    Pondini wrote:
    mikeraburn wrote:
    . . .
    I have read that bulletin, but it must be out-of-date


    It's dated July 15, 2009.

    Yes, it often works, in both Leopard and Snow Leopard. I'm doing it myself, on Snow Leopard.

    But it is still unsupported.


    Sorry, but the argument that it is unsupported doesn't hold any water here. Read the above posts from people using a Time Capsule and Time Machine and getting the 109 error. Backing up with Time Machine to a Time Capsule is unsupported?? I think not. This is a SL bug.


    I was responding to the AEBS issue, but it's clear that NO argument or statement from Apple holds water once you've made up your mind to ignore them.

    If you're having this problem, have you contacted Apple? If you're so sure it's an SL bug, why not?
  • janne salovaara Level 1 Level 1 (10 points)
    Count me in to this unfortunate list.

    But in my case the weird thing is this;
    I and my wife have the exact same setup both MacBookPros bought almost the same time with 10.5.8 installed and now at the same date updated to 10.6 and 10.6.1.
    We both use the same wifi and same 1TB lacie USB connected to APE. Her backups still work and the bundle on the disk is mountable.
    After I restarted my MBP couple of times today to get some other FW disks to appear on the desktop, my timemachine doesn't work. Trying to mount the bundle manually doesn't seem to do anything. During the timemachine back up it always gives the 109 error.
    APPLE.. come on!
  • Pondini Level 8 Level 8 (38,720 points)
    janne salovaara wrote:
    Count me in to this unfortunate list.

    But in my case the weird thing is this;
    I and my wife have the exact same setup both MacBookPros bought almost the same time with 10.5.8 installed and now at the same date updated to 10.6 and 10.6.1.
    We both use the same wifi and same 1TB lacie USB connected to APE. Her backups still work and the bundle on the disk is mountable.
    After I restarted my MBP couple of times today to get some other FW disks to appear on the desktop, my timemachine doesn't work. Trying to mount the bundle manually doesn't seem to do anything. During the timemachine back up it always gives the 109 error.
    APPLE.. come on!


    You are +*NOT TALKING TO APPLE HERE.+*

    This is a user-to-user forum. Since you haven't found a fix earlier in this thread, get all your particulars (serial numbers, etc.) and Call AppleCare: (800-275-2273)
Previous 1 2 3 4 5 6 Next