Automated Backups leave dead process, dead retrospect

[lohman]

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.

 

Problem

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.

[Mayoff]

Dantz is looking at ways to deal with this type of issue in our next version. The following may be helpful:

 

http://www.dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&id=27323