wowmom Posted April 27, 2006 Report Share Posted April 27, 2006 what causes "error 505 (client is reserved)"? why do these erros just come out of no where? how the hell do you fix it? right now i have 3 critical servers that are not getting backed up. the error log indicates "error 505 (client is reserved)" on all three clients. these machines are part of a nightly backup script and have run 'fine' for months. i've had the problem in the past on other clients. i can find no common incident that would seem to casue any problem. it just comes from out of the blue. retrospect server 6.1.126 on mac os x server v10.3.9 mac retrospect client v 6.1.107 Link to comment Share on other sites More sharing options...
jmattingly Posted April 27, 2006 Report Share Posted April 27, 2006 I have the same problem and would like to know the cause... retrospect server 6.5.336 on Win03 client 6.5.136 Link to comment Share on other sites More sharing options...
twickland Posted April 27, 2006 Report Share Posted April 27, 2006 The 505 error indicates that the client believes it is being backed up by another Retrospect application. This error can also be induced if there is a failure during backup of the client. Open the client control panel at the client and see if there is any message displayed that may help your diagnosis. Click Option+"Off" to kill the client process, and then click "On" to restart; see if that re-enables access. (Alternatively, you can reboot the client computer.) Link to comment Share on other sites More sharing options...
waldorfm Posted April 27, 2006 Report Share Posted April 27, 2006 Hi, seems you posted that in the wrong forum - this is Retrospect for MacOSX if I'm not mistaken. Based on my experience, it means that either some or even the same server is currently accessing the client, or the Retrospect client for some reason thinks it is still communicating with a server (hangs). I would check that the client computer has proper network settings, i.e. NIC and Switch port settings are the same (auto. vs. fixed full duplex - use auto on both ends). Did you remote upgrade the client, and or in any case restart the client computer. Link to comment Share on other sites More sharing options...
wowmom Posted April 27, 2006 Author Report Share Posted April 27, 2006 fix it Dantz! Link to comment Share on other sites More sharing options...
CallMeDave Posted April 28, 2006 Report Share Posted April 28, 2006 Quote: fix it Dantz! Fix what? You haven't provided steps to reproduce any sort of software defect, so it's quite possible that you are observing the program working as directed. >i can find no common incident that would seem to casue any >problem. it just comes from out of the blue. It would certainly help readers on the Forum if you would be kind enough to share where you've looked for commonality. For example, what does the Retrospect Client Log indicate in regards to where this client has been accessed before? Is it at all possible that some other copy of Retrospect is connected to these clients when the OS X Server machine attempts a backup? Dave Link to comment Share on other sites More sharing options...
milstone Posted February 13, 2008 Report Share Posted February 13, 2008 I have the same problem. Client Status is: in use by "root" for "Immediate Backup" Turning the client off then on corrects the immediate problem, as does rebooting, but the problem recurs at irregular intervals. I'm not sure how to set the network settings referred to by Waldorfm. This occurs on client Macs running either OS 9.2.2, 10.3.9 or 10.4.11 and client versions 6.0.108. The Retrospect server is an intel mac mini running OS 10.4.11 and Retrospect 5.1.175. I know our Retrospect versions are out of synch but we have had problems in the past when we tried to run Retrospect 6 on the server and haven't been able to devote the time required to resolve this issue. Things were working for quite awhile but the reserved client issue is increasingly problematic. A real solution would be great. Dave Link to comment Share on other sites More sharing options...
rhwalker Posted February 13, 2008 Report Share Posted February 13, 2008 Quote: This occurs on client Macs running either OS 9.2.2, 10.3.9 or 10.4.11 and client versions 6.0.108. The Retrospect server is an intel mac mini running OS 10.4.11 and Retrospect 5.1.175. I know our Retrospect versions are out of synch but we have had problems in the past when we tried to run Retrospect 6 on the server and haven't been able to devote the time required to resolve this issue. Things were working for quite awhile but the reserved client issue is increasingly problematic. A real solution would be great. Any "real solution" would involve updating your versions of Retrospect, and you are just going to have to "devote the time" to do that. We have never seen what you say you are seeing, and we have a couple of MacOS 9.2.2 PPC computers (for our bookkeeping, which runs one program not available on Mac OS X) running Retrospect Client 5.1.180, a bunch of iMac computers running MacOS 10.4.11 and Retrospect Client 6.1.130, and our Xserve G5 running MacOS Server 10.4.8 and Retrospect 6.1.138 with RDU 6.1.11.101. I suggest that you "devote the time" to update your versions of Retrospect first; the problems are not going to magically heal themselves until you do at least that. Many bugs have been fixed in the interim since the versions that you are running. Russ Link to comment Share on other sites More sharing options...
milstone Posted February 13, 2008 Report Share Posted February 13, 2008 Thanks for your reply. I appreciate your suggestions. We are looking for a solution for the existing software configuration. If there is none then that is the answer. As I alluded to, we long ago tried more recent versions of Retrospect (including 6.1.126 for which we have licenses) and returned to 5.1.175 for various reasons of compatibility and performance. Given this experience I am concerned that updating may not solve our current problem and may introduce additional issues as well. I don't disagree with updating for compatibility in general and we often do this (and we tried this route for Retrospect), but our bias is that faced with a specific problem such as currently understanding the source of the problem is more likely to result in a stable solution. The solution may not involve Retrospect directly and may persist after upgrading as implied by Waldorfm's suggestion that network settings might be the cause. I will look again at using the current version of Retrospect (that I believe we already have) but I am not hopeful. I agree that time spent on this issue would probably help. However, we are a 4 person operation without significant formal IT experience or support. Anything we can learn from other users' experience is greatly appreciated. Dave Link to comment Share on other sites More sharing options...
CallMeDave Posted February 13, 2008 Report Share Posted February 13, 2008 Quote: The solution may not involve Retrospect directly and may persist after upgrading as implied by Waldorfm's suggestion that network settings might be the cause. Well, I'm hard pressed to assign too much validity to that users post(s). Those suggestions seemed somewhat random. Information from Retrospect's Operations Log might help to understand what is going on between Retrospect and the client(s). Please provide more details. Dave Link to comment Share on other sites More sharing options...
milstone Posted March 4, 2008 Report Share Posted March 4, 2008 It seems that using Software Update can cause this problem apparently by leaving the user as "root", which renders the Retrospect Client software inaccessible. Clicking "off" then "on" resets Retrospect Client and backup is then successful. The log says: "Can't access on , error 505 (client is reserved)." Other clients are successfully backed during the same script run. Dave Link to comment Share on other sites More sharing options...
CallMeDave Posted March 4, 2008 Report Share Posted March 4, 2008 It seems that using Software Update can cause this problem apparently by leaving the user as "root", which renders the Retrospect Client software inaccessible. Clicking "off" then "on" resets Retrospect Client and backup is then successful. Sorry, I have no idea what this might mean. What does "leaving the user as root" mean? If you're having a reserve issue, command+click on the "off" radio button, then clicking on the"on" button, will surely clear it up. This is unlikely to have anything to do with Apple's Software Update mechanism. Link to comment Share on other sites More sharing options...
file82 Posted March 6, 2008 Report Share Posted March 6, 2008 Base on my experience, doing apple software update( doing actual update or checking if any update available) may cause problem on retrospect backup, especailly on backup server. So I unchecked the auto update checking to minimize the chance the backup error. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.