Time Machine AFP Error connecting to another mac

Discussion in 'Mac OS X Lion (10.7)' started by parkds, Nov 3, 2011.

  1. parkds macrumors 6502

    Jan 23, 2003
    Hi there,
    I know there are tons of issues with NAS drives using AFP for Time Machine. But almost every mention I can find of the issue involves 3rd party devices. I am actually trying to connect to an internal drive of another Mac on my network. I am able to set up the networked HD via AFP, but when I start the Time Machine backup I get the dreaded "The network backup disk does not support the required AFP features" error.

    Hopefully someone can help me a bit to sort this out. I have a MacBook Pro that had been connecting to a Mac Mini Server (running Snow Leopard Server 10.6.8). One of the two internal drives on the Mac Mini was set up as the Time Machine drive for the MacBook Pro. I recently updated my MacBook Pro to Lion (10.7.2) and am no longer able to use the drive for Time Machine. I am able to browse the Hard Drive over the network, connect to the computer via AFP, and add the drive to Time Machine, but when I try to backup the error appears.

    Any help would be greatly appreciated!

  2. Makosuke macrumors 603

    Aug 15, 2001
    The Cool Part of CA, USA
    I was doing exactly that with a non-server Mini (and non-server MacOS) from two different Macs successfully under 10.6, and it's working fine for me with all three on 10.7 as well.

    Which means one of two things: Either 10.7 doesn't like to back up to a non-10.7 shared volume (it might take advantage of some new AFP feature), or something changed setting-wise that's screwing up your backup.

    It's rather time consuming, but if you wanted to test the 10.7 hypothesis, you could try installing Lion on your Mini on a secondary partition as a test (you should get up to 5 installs from the App Store purchase, so it's a free option so long as you don't pay for Lion Server). I'm assuming here that you either need some 10.6/10.6 Server features that Lion doesn't offer, or are reluctant to pay for the 10.7 server upgrade, so this would only be a test, and not a conclusive one--could still be a setting or wonky pref somewhere.

    Otherwise, I'd double-check permissions, and maybe try setting up a temporary backup share and seeing if I could get a Lion system to back up to it, which might be hard if you don't have another Mac around to test with, since it would mess up your current versioned backup in the event you did get it working (or maybe not--it might be hosed anyway after the Lion upgrade).

Share This Page