Jeffops Posted January 6, 2009 Report Share Posted January 6, 2009 We have a Retrospect 7.6 system running on Windows 2003 with LTO 4 backup tape. Most of our computers are Macs with a few Windows system. Generally have had few problems on the PCs and regular Macs, but the Retrospect Client seems to have trouble with our XServes running Leopard. Several times now I have begun large archives only to have them fail because the client stops working. Checking the client on the Xserve I find that it has stopped working, but is using 100% of one CPU. Force quitting from the Activity Monitor is the only way to kill it. The server uses a link aggregated Ethernet connection. We use the current client 6.2.234 - anyone else seen this issue? 2 Quote Link to comment Share on other sites More sharing options...
estaban Posted January 18, 2009 Report Share Posted January 18, 2009 I have a similar problem with an XServe running Leopard as the Server. I can't back up anything - local or remote with that same client version, without the server CPU getting hammered and the jobs just grind to a halt. Quote Link to comment Share on other sites More sharing options...
Jeffops Posted January 20, 2009 Author Report Share Posted January 20, 2009 I hate to say "glad to hear it", but it is good that at least one other person is seeing this issue. Now if we could only get someone to notice our posts and offer a solution. Dantz? Emc? Insignia? Bueller? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted January 20, 2009 Report Share Posted January 20, 2009 Have you tried an uninstall and reinstall of the client? Quote Link to comment Share on other sites More sharing options...
Jeffops Posted January 20, 2009 Author Report Share Posted January 20, 2009 Yes I have uninstalled and reinstalled several times. Same behavior. I'll try it again and see what happens. Quote Link to comment Share on other sites More sharing options...
Jeffops Posted January 26, 2009 Author Report Share Posted January 26, 2009 Reinstalled client and it worked fine Thursday and Friday. Did an archive of over 1 TB without exception. Today (Monday) I checked the server Activity Monitor and sure enough, "Retrospect Client" was not responding and "retroclient" was using 100% of 1 CPU. Had to force quit both processes. I'm going to try something. The "Retrospect Client" app was open over the weekend. I will leave "retroclient" process running but leave the app closed. We'll see if this makes a difference. Quote Link to comment Share on other sites More sharing options...
Jeffops Posted February 6, 2009 Author Report Share Posted February 6, 2009 So I left the Retrospect Client app closed for days and the system worked as expected. Then I left the Retrospect Client app running - that did the trick. After a day I came back and the "retroclient" process was using 100% of a cpu and the Retrospect Client app was not responding. Force quit both and then relaunched the app to start the process again. Then quit the app. So far so good. So it seems the application shouldn't be left open while the "retroclient" process is running. 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.