Jump to content
Sign in to follow this  

Automated Backups leave dead process, dead retrospect

Recommended Posts

This problem existed in 5.6 (there's a forum thread on it) and persists in 6.0; and it's a show stopper for the multiserver product.



1) Setup a script to run over the weekend

2) Come in on Monday and term serv in to the server

3) There's a restrospect.exe running that can not be killed.

4) Retrospect says, "Only one user at a time can run Retrospect".


Retrospect is setup to quit (not reboot) once the backups finish.


This is a MAJOR problem Dantz. The Retrospect tool should say "Retrospect is already in use, would you like to kill the other process and run locally?" or something to that affect in the very least. Ultimately it should not be leaving that process hanging around.


This issue completely stops my ability to use this product as the backups are running on a server that "can not reboot", which means I can't get into Retrospect.

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
Sign in to follow this