kevinf94 Posted January 26, 2007 Report Share Posted January 26, 2007 I have been getting some user's showing up with Net Retry errors during a backup. What pisses me off about Retrospect is the software doesn't move on from the affected client to the next one on the script. Last weekend Retrospect continued to try to connect to a user for 12+ hours which completely screwed up my Recycled weekend back-up. Does Retro have a built-in time-out where if it can't connect to a certain client, it gives up and moves on when it comes to Net Retry issues? Link to comment Share on other sites More sharing options...
rhwalker Posted January 26, 2007 Report Share Posted January 26, 2007 What version of Retrospect do you have, and what client? Facts would be helpful. Some of the causes/bugs on this were claimed to be fixed in a recent release, but some have reported problems. I have seen such a case with the Mac OS Classic client if I shut down the client at exactly the right moment while backup is occurring. I'm of the opinion that some of the recent releases fixed some of the places but not all where this could occur. Answer to your question about built-in timeout: Yes, there is one in some of the places but apparently not all. Your first step would be to get up to current rev level so you at least have the timeouts that are there. Russ Link to comment Share on other sites More sharing options...
kevinf94 Posted January 26, 2007 Author Report Share Posted January 26, 2007 Sorry for not stating what equipment/version I'm running. Got Retro Workgroup 6.1.126 running on a PowerMac G5 Dual 2GHz with 5GB of RAM. Majority of client workstations are running Retro Client 6.1.130. Link to comment Share on other sites More sharing options...
rhwalker Posted January 26, 2007 Report Share Posted January 26, 2007 Ok, then you are up to date and you are hitting one of the bug areas. Are any of the clients Intel Macs? Russ Link to comment Share on other sites More sharing options...
kevinf94 Posted January 26, 2007 Author Report Share Posted January 26, 2007 yeah, some of them are Intel. i've seen the Net Retry errors before on laptops that were set-up with Portable Home Directories. some of our PHD laptop would have their auto-sync stall and that seemed to affect Retro where Net Retry errors would spring up. but Retro seemed to kick out of the client and give a "network communication error" in the log. now it seems to just keep trying and trying and trying. and, you're right, these seem to be on the Intel machines that Retro won't let go. hope it doesn't happen this weekend. Link to comment Share on other sites More sharing options...
caddisfly Posted January 30, 2007 Report Share Posted January 30, 2007 I am getting "net retry" error on one client in particular....as original poster noted, this hangs the entire script until it is canceled. any work arounds? v6.1.126 Retrospect Server on a Xserve dual G5; the client is Windows v5.1 --- I will try an updated client... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.