rcolley Posted August 27, 2002 Report Share Posted August 27, 2002 We are running 6 retrospect 5.0.205 backup servers backing up between 50 to 150 clients each. Over the last few weeks we have been getting an increasing number of net retries. For some clients this times out and execution is stopped. Unfortunately for other clients the time out does not occur and the client sits there preventing further backups occurring. This annoyingly often happens when unattended and puts our substantial backup way behind. We never got anywhere near the number of net retries with Retro 4.3. I am serouusly wondering if we should downgrade to 4.3 as our backups are suffering. Any help would be greatly appreciated. Rob Link to comment Share on other sites More sharing options...
Guest Posted August 27, 2002 Report Share Posted August 27, 2002 Dantz is aware of and actively investigating this issue. In some cases, we have seen instances where the net retry error hangs the backup. Link to comment Share on other sites More sharing options...
Chik Posted August 27, 2002 Report Share Posted August 27, 2002 We are having this exact problem as well. For the last two weekends are backups are halted by this error. Some users have not been backed up in over a week as a result. This has happened on two different servers with 150 people on each. Please stop my hair from turning gray by coming up with a solution! -Chik Link to comment Share on other sites More sharing options...
shadowspawn Posted August 28, 2002 Report Share Posted August 28, 2002 Are you running the server on Mac OS 9 or Mac OS X? I have encountered the same problems on Mac OS X, and am unsure whether they also apply to hosting on Mac OS 9. You may be able to troubleshoot your network to reduce the number of Net Retries, which will improve the situation until Dantz are able to fix the problem. I followed the 519 troubleshooting guide and got the Net Retry down to an occasional problem rather than the complete show-stopper it was for me the first few weeks after I upgraded (in April). On a related note, there are two other situations I have encountered where Retrospect stalls on a client indefinitely: if the client crashes; and sometimes when (incorrectly) backing up a mounted disk image on a Mac OS X client. Other people have reported similar stalls when a portable is (abruptly) disconnected during a backup. You can't downgrade to 4.3 if you want to backup Mac OS X clients, but otherwise from my personal experience Retrospect 4.3 is much more reliable at unattended backups than the current version of Retrospect 5. Link to comment Share on other sites More sharing options...
rcolley Posted August 28, 2002 Author Report Share Posted August 28, 2002 Thanks for your comments we are running OS X, on all but one server which we had to switch back to OS 9 because it had a problem backing up an ASIP server. The Retrospect 5- OS 9 machine does get more net retries than when it was running 4.3 but these don't seem to hang the backup in the way that occurs on the OS X retrospect 5 servers cheers Rob Link to comment Share on other sites More sharing options...
oybobby Posted October 23, 2002 Report Share Posted October 23, 2002 Hello, I have similar problems with "Net Retry" killing backups before they can start. Since there may be other issues, here's how I got here: The drive on my PB G4 died. No sweat, right? Retrospect would save the day. And it mostly did. I put in a new drive, partitioned it with Disk Utility, and did a restore of the two partitions, seemingly without problems. But here are a few that I've found so far: First, as I found in the forum earlier today, Retrospect chowned my Keychain file to root. Bad Retrospect. I sudo chowned it back to me and it's fine now. Will this keep breaking? Next, it didn't copy /var/tmp which resulted in my not being able to run the script to update the locate.app database /libexec/locate.updatedb>. I had to do a sudo mkdir /var/tmp to restore functionality. And last (so far) but certainly not least, I can't run backups from the restored disks. I get the Net Retry hang thang. I tried changing the Source in my backup script to no avail. It correctly is looking for my DHCP-served IP address (192.168.0.4). I'm running OS X 10.2.1, Server 5.0.236 and Client 5.0.540. What's a poor boy to do? Thanks. Regards, Maurice Link to comment Share on other sites More sharing options...
shadowspawn Posted October 23, 2002 Report Share Posted October 23, 2002 > And last (so far) but certainly not least, I can't run backups > from the restored disks. I get the Net Retry hang thang. Two suggestions: 1) Uninstall the Retrospect client, and reinstall the client. There is a documented issue with Mac OS X 10.2 with one particular file internal to the client which means the client is not completely restored and must be manually reinstalled. 2) If this does not immediately fix the problem, run something to verify your hard disk. I think your issue is the dud client, but I had the same symptoms on a disk which failed validation although otherwise appeared fine. Link to comment Share on other sites More sharing options...
oybobby Posted October 24, 2002 Report Share Posted October 24, 2002 Thanks, John, for your informative suggestions, the first of which (thankfully) was spot on and all I needed to get me back on the air. By the way, you mentioned "a documented issue with Mac OS X 10.2" in your reply. What is the issue and where is it documented? Thanks again. Regards, Maurice Link to comment Share on other sites More sharing options...
shadowspawn Posted October 24, 2002 Report Share Posted October 24, 2002 > By the way, you mentioned "a documented issue with Mac OS X 10.2" in > your reply. What is the issue and where is it documented? The explanation below is from the "Retrospect 5.0 Updated for Jaguar" announcement in this forum, there is further information in the ReadMe and presumably also in the KnowledgeBase. The last line is the one you needed to spot in the large amount of information available. :-) -- 4. Error -40 on clients running Mac OS X 10.2.x. Retrospect generates an error: "Can't read file retropds.22, error -40 (file positioning error)" resulting in the "retro22.pds" file not being backed up. This file is necessary for the Retrospect client software to operate correctly. Dantz is working with Apple to solve this problem. In the meantime, the Retrospect client software should be reinstalled manually following a Mac OS X 10.2.x system restore. Link to comment Share on other sites More sharing options...
oybobby Posted October 25, 2002 Report Share Posted October 25, 2002 Thanks again, John, for your help. I actually read that note, but since it said it concerned "Error -40" which I did not experience (nor was any mention made of "retropds" or anything like that), I was chasing around for resolution to the "error 519" message I kept getting. The technote for error 519 made no mention of retropds or reinstalling the client. Frustrating, to say the least. Thanks again, John. Regards, Maurice Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.