adrian_fry Posted March 19, 2012 Report Share Posted March 19, 2012 Hi, Does anyone know what error -1017 means - I'm backing up a mounted network share, which stopped half-way through an unattended backup. Cheers Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted March 19, 2012 Report Share Posted March 19, 2012 Look in the log. The error should be described there in plain text. Quote Link to comment Share on other sites More sharing options...
adrian_fry Posted March 19, 2012 Author Report Share Posted March 19, 2012 Hi, I did, it said network share unavailable, however, the share was mounted on my Mac the whole time and the server log says no downtime - it's as if Retrospect 'forgot' it was there somehow! Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted March 19, 2012 Report Share Posted March 19, 2012 Please post the full log from the backup. Was the share mounted with full permissions? Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted March 21, 2012 Report Share Posted March 21, 2012 the share was mounted on my Mac the whole time And that's likely the problem. Did you "Add" the network volume to Retrospect's "Sources" list from the giant candy "+" icon? Was the network volume mounted on your Mac at that time? Mac OS X will not allow any filesystem to be mounted with the same name at the same time by different users. The Retrospect engine runs as User 0, while your Finder session is likely a different user ID (generally 501 for the first local user). The first user to mount the volume gets its normal name ("foo") while the next user gets "foo-1". The Finder will hide this, but you can see it in Terminal. Go to Sources and select the share point, then look at the Overview section below, at the Path field. What do you see? Now open Terminal and issue the "mount" command. You should see your network volume there. Do you see it twice? Do you see the modified name OS X has created for the second one? Retrospect will look for volumes on the path you initially set for it. If this path changes (due to user action) the volume won't be found. This issue, in one form or another, has been the most frequently answered question on this (and the previous) Forum since version 5.0.20x shipped back in 2010 or so. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.