This script is designed for users of Retrospect® who want to log their backups with monoLogTM, and/or work with Kick-off!TM and Rebound!® during backup operations.
This script provides the following functionality:
monoLog is a comprehensive logging system, which works with supported applications to record important events reported by those applications. In addition to logging, monoLog can respond to messages it receives, based on the priority level of the messages. You can have monoLog notify you via e-mail or pager when important event occur, and/or have monoLog execute scripts. Many computers running monoLog can also "report in" to a single administrative workstation, giving admins an overview of their entire office at a glance.
Kick-off! and Rebound! are powerful system monitoring and crash recovery tools. They watch your computer at all times, and can automatically restart it if applications or the system itself crash.
When Retrospect runs a backup, it keeps your computer very busy. At certain times in the backup process (for example, during catalog compression), Retrospect does not give time for any other task to run. If this happens for a long period of time, Rebound! or Kick-off! will think the computer has crashed, and will restart it. This will of course cause your backup to fail.
RetroLog allows Retrospect to tell Rebound/Kick-off! when it initiates a backup, so Rebound!/Kick-off! will not restart the computer during the backup process.
To install the script, simply drag the script application named "Retrospect Event Handler" into your Retrospect preferences folder, found in the system's "Preferences" folder.
Note: If you are already using a Retrospect Event Handler script, you will have to combine the scripts. This should only be attempted by experienced scripters. Information on combining scripts can be found below.
When Retrospect runs, it sends messages to the "Retrospect Event Handler" script at various times during the backup process.
When a backup begins, the script tells Rebound!/Kick-off! to greatly lengthen the value of the "Restart if system doesn't respond" slider, and uncheck the "Monitor timers in supported applications" box.
At key points in the backup, the script adds log entries to monoLog describing the progress of the backup.
When a backup finishes, the script restores the crash detection settings to their original values.
IMPORTANT: If you edit this script, you may have to change some of the "raw" event codes used in the AdjustConfiguration and RestoreConfiguration routines. Due to an apparent bug in AppleScript, these raw events may appear as "«class xxxx»". If this occurs, change them to "«property xxxx»", or the script will not compile correctly.
There are four occurrences of these in AdjustConfiguration, and two in RestoreConfiguration. Be sure to change all occurrences in these routines, and no others!
The properties you can modify are found near the top of the script:
The easiest way to do this in most cases is to simply copy most of your script's properties and routines into RetroLog. At the bottom of the RetroLog script are several Retrospect event handlers, whose names will match the analogous handlers in your script. For the most part, you can simply copy the relevant contents of your handlers into the corresponding handlers in RetroLog. (Although be careful not to include both sets of "return" statements.)
IMPORTANT: Whenever you modify your script, you may have to fix the "raw" event codes, as described in "Customizing the script" above.
In all other respects, you should follow the Retrospect Event Handler instructions provided by Dantz.
Sophisticated Circuits, Inc.
PO Box 727
Bothell, WA 98041-0727
Dantz Development Corporation
4 Orinda Way, Bldg. C
Orinda, CA 94563