Jump to content
Sign in to follow this  
powermeck

How to properly terminate Retrospect

Recommended Posts

Recently Retrospect 6.5 MultiServer on NT4 began stalling on me repeatedly. It would not execute scripts anymore, just sit there and stare at me. When I try to quit Retrospect (using the File-Quit command, of course), I would get the sandwatch for hours without any change.

 

Using the Task Manager I then tried to quit all Retrospect instances, but to no avail - they stayed in the task list, running. My only choice is to reboot the server, which takes forever due to all the SCSI-devices attached.

 

Where do I begin?

Share this post


Link to post
Share on other sites

Retrospect may be waiting for information from the backup drive indicating that it is ready. Retrospect cannot quit until the backup hardware has completed operations (rewinding tapes for example).

 

As a test to help isolate the problem, try shutting down and unhook all SCSI devices. Boot and launch Retrospect. Does it quit normally? If so, try setting a script to run a few minutes in the future. Quit Retrospect and make sure it launches and quits normally. Don't worry that your backup drives are not attached. Retrospect should log an error and quit.

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  

×