Jump to content
ddtmm

15.5.0.179 problems

Recommended Posts

I recently upgraded to 15.5.0.179 from 15.1.2.100 (multi server) but noticed that any job that started where the client was not to be found (because that client was turned off), Retrospect would hang up. That is, it would permanently say "Finding Client...". Cancelling the job or even trying to quit Retrospect altogether would not work. Just sits there, and you have to kill the task from Task Manager. Version 15.1.2.100 did not have this problem and reverting back works fine. 

Anyone else experiencing anything like this?

Share this post


Link to post
Share on other sites

Yes, I am seeing similar behavior. I thought it might be a one-off, but I arrived to such a hang up this morning. I've reverted as well. Proactive backups _do_ appear to continue handling missing clients, but if a script iterates through several clients, a missing client hangs the script, and blocks some others.

Edited by rsleegers
correct proactive statement

Share this post


Link to post
Share on other sites

Yes, my server will continue to search indefinitely for a missing client running the matching sever/client version 15.5.0 (179). When you cancel the job it will never quit the job. I then go to File - Quit to restart Restrospect and it will never close. You then have to just go kill the Retrospect process that is not responding.  

Share this post


Link to post
Share on other sites

Retrospect Single Sever on WS2012 R2 and the Retrospect Client is on latest Win10. It hangs on any client it can't find so I makes me think that its something with the server. I'm using the private/public key security to authorize the clients. Maybe this could be something??

Share this post


Link to post
Share on other sites
On 9/27/2018 at 4:45 PM, DavidHertzberg said:

Here's why and how to fie a Support Request for a bug.

I did so, and an agent replied with: "This does look like a new bug that we are investigating.  For now, please keep using the 15.1 version if it is working for you.  We hope to have the problem understood and resolved soon."

Share this post


Link to post
Share on other sites

Me too. Over the weekend I had the same type of freeze\hang with the console stuck at "Finding next-computer-to-backup". I'm running Retrospect for Windows Multi-Server V15.5.0.179 which I upgraded to last week. Before that I was running V15.1.2.100 for a while for no issues. It's on a Windows 2012 R2 server and the only thing that changed was the upgrade of Retrospect.  The backup computer is running Windows 10 Pro 1803 64bit agent version V15.5.0.179.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×