5.0 Backup server stuck dialog box on quit

[cogswell]

Hello;

 

 

 

Here's an odd one I've been running into a few times, so I figured I'd post it. I apologize if this has already been dealt with.

 

 

 

Retrospect 5.0.205 workgroup, Retrospect Driver Update, v. 2.7.102, AGP G4/350 (sawtooth), Mac OSX 10.1.5. Tape drive is a Seagate CTL-96G (built-in autooader, one SCSI ID, Retro calls it Driver "Archive Python DDS-DC 5.01", Product Python 28849-XXX, Vendor ARCHIVE) hooked through a Adaptec 2930CU scsi PCI card (Adaptec driver 1.1). Both the card and the drive are 50-pin connectors. I normally don't have any backup problems (except for Retro's ability to correctly find tapes in the autoloader which worked fine in 4.2 that I've detailed before, but this is an unrelated problem I think).

 

 

 

The backup server is running normally, and "idle" (not actively backing up a client). With the "Backup Server" window (with the list of clients) in the foreground, I push command-W to close the window (to stop the backup server). I then get the normal "Really stop execution of Backup Server?" dialog box with the No/Yes buttons. The "Yes" button is pulsing blue for the default. This is all normal, and usually I push the enter key or click "Yes" to stop the server.

 

 

 

Sometimes though, at this point Retrospect is hung up. The button pulses, but won't accept the Enter to acknowledge, and won't respond to clicks on the buttons. I can't move the windows around with the mouse or change the front/back stack order. If I click and hold on the Retrospect icon in the dock I'll get the "Application not responding" message. So far the only way I've found to get out of it is to force quit.

 

 

 

Like I said, it doesn't happen all the time, and so when it does happen I get suprised. Nothing else seems to be out of the ordinary (that I can tell). I have three different scheduled backup server scripts (normal overnight, lunch time for people with laptops who leave, and one special case for a person who usually leaves with his laptop before lunch time) all to the same backup set, and I'm pretty sure this has occurred while any one of them is active (ie - I don't think it's one particular script). The force quit usually goes okay (I rarely try to quit the backup server while an operation is in progress so it's never been writing to the tape when I try) but it's just annoying.

 

 

 

Best regards,

 

Steve