merrisr Posted June 9, 2003 Report Share Posted June 9, 2003 I am running Retrospect 6.5 multiserver, backing up approximately 30 clients, c. 25 Windows and c. 5 linux. I have had a number of Retrospect server crashes, after which some of the clients cannot be accessed. The error is error -505 (backup client reserved). The User's Guide states to resolve this by rebooting both systems, but some of the client systems involved are 24/7 or close to it, so I cannot always reboot them when I need to do so. This is a big problem. There are a ton of posts and resources for dealing with this issue in OS/X, and I can easily resolve it in linux by killing the client processes and manually restarting, but I cannot resolve it for my windows clients without rebooting. I have restarted the services, etc., but no luck without rebooting. Does anyone know of a workaround short of rebooting the entire system? If not, this poses a big problem to utilization of Retrospect in a high-availability environment. Thanks, Rhian Merris merrisr@saic.com Link to comment Share on other sites More sharing options...
Mayoff Posted June 9, 2003 Report Share Posted June 9, 2003 This error will often happen after a network connection failure. You may see some additional errors in the operations log, like an error 519. You can go to the services control panel and stop the client service (RetroClient), and then start the client service again. Link to comment Share on other sites More sharing options...
merrisr Posted June 9, 2003 Author Report Share Posted June 9, 2003 But that doesn't clear it up in the Windows boxes - can't seem to clear it without rebooting the client completely. Link to comment Share on other sites More sharing options...
Mayoff Posted June 9, 2003 Report Share Posted June 9, 2003 How long have you left the client idle after this happens? The client should timeout after a few minutes (sometimes longer). Is the backup failing during copy? What type of feature is it? You can also try one of these commands to stop the client http://www.dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&id=27852 Link to comment Share on other sites More sharing options...
merrisr Posted June 9, 2003 Author Report Share Posted June 9, 2003 Thanks for the quick responses and the link. Those command-line options should be helpful. So, great news - I tried Sysinternals' freeware pstools (pskill and psexec) and killed the retroclient process remotely, then restarted it and that worked! I'm not sure why just restarting the service didn't work, but maybe that had to do with leaving it idle. Did you mean to leave it idle after stopping and before restarting? If so, I didn't really do that, so maybe that made a difference. Thanks! I'll post more if I discover anything else relevant, but I'm in much better shape if I can at least kill and restart the client. Rhian Merris merrisr@saic.com Link to comment Share on other sites More sharing options...
Mayoff Posted June 9, 2003 Report Share Posted June 9, 2003 If you leave alone after the original error, the 505 should timeout on it's own. No need to kill the process. Link to comment Share on other sites More sharing options...
merrisr Posted June 9, 2003 Author Report Share Posted June 9, 2003 Ah, no, I left it alone for over a week and it didn't time out. But, killing it with pskill and restarting it with psexec has done the trick on all three systems I tried, so I'm good. Thanks, Rhian Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.