Paul Richardson Posted May 19, 2012 Report Share Posted May 19, 2012 I'm getting a heap of errors like the following: 19.05.2012 00:06:57: Connected to Vertrieb * Resolved container Vertrieb to 1 volumes: Macintosh HD on Vertrieb Can't access volume Macintosh HD on Vertrieb, error -1101 ( file/directory not found) Everything is running on OS X 10.6.x What exactly is (or is not happening) here and what can I do about it? I'd be very grateful for any help or ideas Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted May 19, 2012 Report Share Posted May 19, 2012 Is that for every source volume on every client? Or just this one? Quote Link to comment Share on other sites More sharing options...
Paul Richardson Posted May 20, 2012 Author Report Share Posted May 20, 2012 Is that for every source volume on every client? Or just this one? It applies to about 8 out 10 clients. Each has one source volume selected. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted May 20, 2012 Report Share Posted May 20, 2012 It applies to about 8 out 10 clients. Each has one source volume selected. OK, is it still the same (identical) source volume? Or has it been renamed? Or has it been replaced or reformatted and just happens to have the same name? Quote Link to comment Share on other sites More sharing options...
Paul Richardson Posted May 21, 2012 Author Report Share Posted May 21, 2012 OK, is it still the same (identical) source volume? Or has it been renamed? Or has it been replaced or reformatted and just happens to have the same name? It's the same volume. The Retrospect installation is only a week old. It's the first time in over a year that Retrospect has known anything about any of the volumes. The backup ran once and then I started getting bombarded with error -1101. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted May 21, 2012 Report Share Posted May 21, 2012 Strange. I would try to forget the client(s) and add them again. Quote Link to comment Share on other sites More sharing options...
Paul Richardson Posted May 22, 2012 Author Report Share Posted May 22, 2012 Strange. I would try to forget the client(s) and add them again. Yesterday afternoon I refreshed all the volumes, and forgot and re-added one client. The proactive script ran all night, and from 11 clients, 1 was backed up, (not the one that was forgotten). Retrospect spent the night logging error -1101 for the other 10 clients. Today I will systematically forget all clients. But I'm not confident it will help, as I've more or less already tried that. I'll let you know. Quote Link to comment Share on other sites More sharing options...
Paul Richardson Posted May 29, 2012 Author Report Share Posted May 29, 2012 As a last desperate act I did the following: 1. remove all client sources and relevant scripts from Retrospect and stop the engine. 2. Uninstall all clients and restart the machines 3. restart the engine 3. Install the latest version of the client and prepare for first access 4. add all clients individually 5. make a new script Having done that, everything has been running smoothly for a couple of days now. Quote Link to comment Share on other sites More sharing options...
Paul Richardson Posted June 2, 2012 Author Report Share Posted June 2, 2012 Having done that, everything has been running smoothly for a couple of days now. Well, I spoke too soon. As of last night it's back to square one. error -1101 on all clients. This time I'm inclined to just give up on Retrospect (again!) and get my money back. Quote Link to comment Share on other sites More sharing options...
tgfn Posted June 11, 2012 Report Share Posted June 11, 2012 isn`t that the "sitting at the logging window issue"? in any case, i have a few of this 1101 errors on a few machines as well, they always sit at the loging window and the issue can be solved by restarting the computers via remote desktop or ssh or by walking to the computer Quote Link to comment Share on other sites More sharing options...
Daniels Posted June 12, 2012 Report Share Posted June 12, 2012 Also make sure not to put the hard drives to sleep as I have found the Wake on LAN feature to not work correctly. Quote Link to comment Share on other sites More sharing options...
mastercam Posted June 18, 2012 Report Share Posted June 18, 2012 Also make sure not to put the hard drives to sleep as I have found the Wake on LAN feature to not work correctly. It doesn't work at all. I'm in the process of looking into this error. The thread has been helpful, thanks! 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.