As noted in a previous article I was tasked by a client with figuring out why their Retrospect Backup software for Windows was not working properly. Since I was not familiar with Retrospect I had to troubleshoot from the beginning. I started troubleshooting on the Windows 2003 R2 server running Retrospect and was able to easily see the log files showing the errors backing up one of the companies Exchange servers. When I attempted to manually backup a single mailbox on the Microsoft Exchange server I was receiving the same errors. Below I describe the Retrospect backup error and then explain step by step how I was able to resolve the error.
Retrospect Backup Error On Windows Server 2003 R2:
Retrospect Backup Error Text: Sorry can’t list volumes on Exchange Mailboxes on exchange.example.com – Error -505 (backup client reserved).
Resolve Retrospect Error 505 Backup Client Reserved Error:
Luckily the error ended up being fairly easy to resolve and in my opinion the actual error message was useful and was led me to the actual problem. From the error message I assumed that the Retrospect Client on the Exchange server was either locked up or refusing connections for some other reason and turns out that is exactly what the issue was. To resolve the issue login to the server that is running the Retrospect Client and type “services.msc” in the Start >> Run window to launch the Windows Services configuration window as shown in the below example image.
Windows Services Configuration Window:
Even though the Retrospect Client appears to be running without issue as displayed in the example image above you should go ahead and restart it. I believe the issue is that the Retrospect backup process either was interrupted or something else caused the Retrospect Client process to become corrupted, locked up, or similar. To restart the Retrospect Client right click on the highlighted line in the above example image and select Stop from the pop up menu. Once the process has stopped right click on the same item but this time select Start from the pop up menu. All of these steps are shown in the example images below.
Stop Retrospect Client Process On Windows Via Services Configuration Windows:
Start Retrospect Client Process On Windows Via Services Configuration Windows:
Once the Retrospect Client process has been stopped and then started on the problem server you can log back into the primary Retrospect Backup server to see if you can now successfully complete a backup process. In my scenario I was now able to run backups without issue as shown in the below example image.
Retrospect Backup Process Running Manually Without Error:
Thats it. If more than one Retrospect Client had the “Backup Client Reserved” error follow the same steps above on each server and likely the issue will be resolved.