Jump to content

jscud

Members
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jscud

  • Rank
    Newbie
  1. A little more in case this helps anyone else: The thing I was missing was that I needed to add the share in the 'sources' pane. This never occurred to me since for me it's not a source, but a target. Anyway. Once I did, I was able to at least see it in the media pane, though I continue to have problems (currently discussing with Retrospect Support). (Un?)fortunately I had already done your mount_afp hack when I had the 'sources' a-ha, so I don't actually know if it would have worked absent the mount_afp.
  2. I've tried your recipe and it hasn't solved my problem. Of course, my problem is only related, not the same -- you want to back up shares. I'm backing up TO a share and want to teach Retrospect that I've moved the media set to a different share. I think I'll try opening a support case and see if I can get anything that way. By the way, I found that I needed to invoke mount_afp with the -i option. At least, that was the most convenient way to get my password in, rather than figuring out the right combination of quoting and escaping to sneak my special characters past the command line.
  3. No. I understand it and have the necessary skills, but not the time or patience at the moment. I expect I'll try it when I get a round tuit -- thanks! Yes, 10.8.4.
  4. I think I am seeing it, though I'm new enough to Retro (or at least, this version after a long hiatus) that I'm still trying to suss out whether that's really the case. In my case, I had my media set members sitting on one AFP share. I moved them to another (larger) share and am having no success at all in teaching Retro that they've moved. Indeed, I can't even find a way to tell Retro that there is a new share at all. The interface for managing members and their locations is already obscure enough that I thought maybe I just hadn't figured out the correct incantation, but now that I've read this thread I suspect the problem is simply that Retro has a bug preventing it from even seeing the new share, which stymies any further progress.
×