slava Posted February 24, 2003 Report Share Posted February 24, 2003 I am getting the -505 client reserved message!!! I found this: -505 client reserved This error occurs when a client is in use by another backup computer A client may be used by only one backup computer at a time. This can also happen when the backup computer or client computer crashes during an operation. Restart both computers. We have only one backup server. I cannot restart computers (server and client ) every week or so . How can I fix this. Backup server= 9.0 /Retrospect 5.0 Client =xserve thanks Link to comment Share on other sites More sharing options...
amanda2003 Posted July 25, 2003 Report Share Posted July 25, 2003 me too problem seems to be less of an issue as Jaguar Clients climb higher is version number. 10.2.0 lead to many -505 errors each week, while 10.2.6 leads to only 1 a month. Still an issue that Dantz should have fixed with a patch to the client Link to comment Share on other sites More sharing options...
increment Posted November 17, 2003 Report Share Posted November 17, 2003 I'm getting the -505 problem with an X machine here now. It's a basic 10.2.x machine but it's used as a CVS server and can't be restarted very often. What I've found is that I can restart the client from the Terminal. I'm wondering if this is a huge problem for the Retro client? What I did... Basically the only thing that's started at boot time is the pitond process. I was just going to start that, but instead decided to use the helpfull startup script. So, I just did a "sudo /Library/StartupItems/RetroClient". This was after just trying to do a "kill -HUP" on the pitond service, but it doesn't handle that. It died. So I just tried starting it up again. Seems to work great. What issues will I run into with this? Is there any possibility of corruption of the backup? Any other processes that need to run? I really can't keep restarting this machine, but it comes up with the -505 error about every other time it backs up. Since it backs up every night. It's a pretty big problem, but much less of a problem if all I need to do is restart the processes for the client. This is with Windows Multi-Server 6.5.x (newest) and 5.1.109 MacOS X client. Link to comment Share on other sites More sharing options...
natew Posted November 19, 2003 Report Share Posted November 19, 2003 Hi From a Retrospect server standpoint, stopping the service is no different from unplugging the network cable on the machine. Retrospect can handle that kind of thing - it will just give you an error -519 if a backup is underway at the time. I don't see a big problem with this... The 505 error indicates that the client connection didn't teminate completely. Are there any errors in the log regarding the previous backup of that client? Nate Link to comment Share on other sites More sharing options...
hmseiden Posted November 19, 2003 Report Share Posted November 19, 2003 I don't know if this equates to the same cause, but I got a -505 error when a client wasn't visible after a failed backup attempt, then merely turned on Client's Retro (it turned off by itself). Then I deleted the pending back up on the Client. Somehow in a new OS (OS X 10.3) install of Retrospect Backup (Server), the Clients needed to be reset. This applied to both WIN and OS X clients. Now all is well. My system: B&W G3, 400MHz 704MB RAM, ATA+SCSI Backup devices- AIT & FW HD Retro Backup 5.1.175 Clients- WIN XP, MAC OS X Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.