mbernhardt Posted November 21, 2013 Report Share Posted November 21, 2013 I'm running Retrospect 10.5.0.145 and have a single remote Mac client running the same version. This problem has been going on with earlier versions also though: The server can't communicate ith the client, saying that it's "busy or unavailable." Messing with the client does not help. This happens every few weeks- or at least I notice it every few weeks, since I don't check the backup log every day (I back up every day). I finally discovered that the way to bring it back on line is to re-add it on the server. I don't even have to delete it first. Has anyone else experienced this, and what's the solution? 1 Quote Link to comment Share on other sites More sharing options...
Daniels Posted November 21, 2013 Report Share Posted November 21, 2013 I have had this happen. The best trick I have found to fix this is to turn the client off and turn it back on. You do this on the client by holding the command key down while setting the client to "Off" and you should see the status as "Turned Off". If you do not hold the command key it will only say "Not running" in the status box. I am using the latest PowerPC client so the interface might be different in 10.5 Quote Link to comment Share on other sites More sharing options...
Don Lee Posted November 21, 2013 Report Share Posted November 21, 2013 I saw this for the first time yesterday, when I upgraded the client from 10.2 to 10.5. I could not get the engine to "see" the client, either in the browse window, nor to do operations. (like backup or browse volumes) I tried re-installing the 10.5 client, and it didn't help. When I directly added the client (yes, without deleting it) on the server, it worked again. Interestingly, the "sources" window on the server never changed from the green badge, and "refresh" did not change its volumes to the "~" symbol, so in some sense, it looks like the server could still "talk to" the client. The client also seemed to think it was "connected" to the server, judging from the display in the retro client pref panel. Server/engine running on Mac OS X 10.6.8, client is running Mac OS X 10.8.4. I don't remember how the client was originally added. Quote Link to comment Share on other sites More sharing options...
swalker Posted November 21, 2013 Report Share Posted November 21, 2013 I often have to delete and re-add clients at the server (without touching anything on the client) to get them to work again. Quote Link to comment Share on other sites More sharing options...
theboyk Posted November 28, 2013 Report Share Posted November 28, 2013 I have the same problem with Retrospect 9. Good to see this hasn't been fixed in 10 either. Quote Link to comment Share on other sites More sharing options...
splurzgalonk Posted December 10, 2013 Report Share Posted December 10, 2013 Beside removing and adding the client again, you might want to use the "Locate" button. That does the trick for me, although I'm not pleased to have to use tricks in the first place... You might want to contact the support staff with a reference to bug reports filed in the given board. That might help putting some emphasis on those issues. Obviously it is not that obscure a bug. cheers Roland 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.