bjhowd Posted July 13, 2010 Report Share Posted July 13, 2010 Running Retrospect 7.6 and have seen this twice now in the past two weeks. Most of what I could find on the internet is reboot the client and it will take care of the error. I have had this happen on the same server being backed up twice. It's an MS Exchange 2007 Cluster and the server is one of our Mailbox servers. I can move the cluster group and reboot the server and then move the cluster group back and the next backup seems to work. There has to be a better fix than this. I don't see this as a long term solution. What is causing this error and how can I fix it permanently. What is a reserved client anyway :question: Quote Link to comment Share on other sites More sharing options...
Daniels Posted July 13, 2010 Report Share Posted July 13, 2010 A reserved client means that another process is using the client and Retrospect can not access the client. I see this occasionally when my two Retrospect systems overlap on a shared client. I would make sure that nothing is accessing the client during the backups and see if the error goes away. If there are no other backup systems going I would also make sure that you schedule defrags, chkdsks, etc. for after the backup is complete. Quote Link to comment Share on other sites More sharing options...
bjhowd Posted July 15, 2010 Author Report Share Posted July 15, 2010 OK, it hasn't happened again this week, but good to know that there may be another process that is happening at the same time. I inherited this network so I am still checking things out. Thanks for your suggestions. Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted July 19, 2010 Report Share Posted July 19, 2010 (edited) I see this all the time on a few of our linux clients (Ubuntu). Every week I restart the rcl application again which clears the fault. Seems to go into this state pretty much after every backup though - which is annoying. Only see this on Linux clients (which are in a VM ESXi environment). Reatarting the service on a Windows machine should being the RS Client back to life in your instance.. Rich Edited July 19, 2010 by Guest Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted July 19, 2010 Report Share Posted July 19, 2010 (edited) ******@****ubuntusvr03:~$ /etc/init.d/rcl status Server "Ubuntu Server 3": Version 7.6.100 reserved by ****BACKUP01 for Daily General Servers > NAS back up according to normal schedule currently on readonly is off exclude is off 1 connections, 1 authenticated After a quick service restart... *******@****ubuntusvr03:~$ /etc/init.d/rcl stop Server "Ubuntu Server 3": Client stopped *******@****ubuntusvr03:~$ sudo /etc/init.d/rcl start [sudo] password for *******: *******@****ubuntusvr03:~$ /etc/init.d/rcl status Server "Ubuntu Server 3": Version 7.6.100 back up according to normal schedule currently on readonly is off exclude is off 0 connections, 0 authenticated *******@****ubuntusvr03:~$ RS logs how this: Can't access backup client Ubuntu Server 3, error -505 ( backup client reserved) Edited July 19, 2010 by Guest 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.