Retrospect Client not running retroeventhandler.bat

[jabelli]

I performed my first ever client backup yesterday, and the script never ran on the client.

 

the file is C:\Program Files\Retrospect\Retrospect Client\retroeventhandler.bat

 

I know it's a valid batch file because not only have I tested running it, it is virtually the same as the one on the server, which is functioning correctly.

[Mayoff]

What are you trying to do with this event hander?

[Mayoff]

What version of the client?

[jabelli]

Client is the same as the server, 7.6.

 

Right now it's just trying to log to a text file, but nothing is happening.

[jabelli]

Which events are supposed to be supported by the client? I should have gotten a log entry no matter what was called, but it sure isn't being called for StartApp or EndApp, and didn't get called this morning when the client was backed up.

 

[Mayoff]

StartApp would be for starting the Retrospect application not for starting a backup. The Sample batch file clearly says this.

 

REM Sample Retrospect Event Handler
REM 
REM     The Retrospect application will call this batch file with the first
REM argument as the subroutine name (e.g. "EndSource").
REM     Procedures supported by Retrospect 5.1:
REM StartApp -- Retrospect has been launched
REM EndApp -- Retrospect is quiting
REM StartBackupServer - The backup server is starting
REM StopBackupServer - The backup server is stopping
REM StartScript - A script is begining
REM EndScript - A script is stopping
REM StartSource - A volume is about to be backed up
REM EndSource - A volume has been backed up

 

The client probably will only work with:

 

REM StartSource - A volume is about to be backed up

REM EndSource - A volume has been backed up

 

Edited August 19, 2008 by Guest

[jabelli]

OK. I will see what happens tonight.

 

I am using the following batch file, which should at the very least make an entry in the log file

 

@echo off
if not %_tccver==_tccver goto tccstarthere
"C:\Program Files\JPSoft\TCMD9\tcc.exe" /c %0 %*
exit /b
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: JP Software RetroEventHandler client batch file         ::
:: Be sure to adjust the above command line to your system ::
::   return code 0 == no error                             ::
::               1 == invalid procedure                    ::
::               2 == invalid number of parameters         ::
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:tccstarthere
setlocal
echo %_date %_time - %* >>C:\RetrospectEventHandlerLog.txt
if %# LT 2 quit 2
switch %1
case StartSource
 if %# != 6 quit 2
 set scriptName=%2
 set volName=%3
 set sourcePath=%4 
 set clientName=%5 
 set interventionFile=%6

case EndSource
 if %# != 18 quit 2
 set scriptName=%2
 set sourceName=%3
 set sourcePath=%4
 set clientName=%5
 set kbBackedUp=%6
 set numFiles=%7
 set duration=%8
 set sourceStart=%9
 set sourceEnd=%10
 set scriptStart=%11
 set backupSet=%12
 set backupAction=%13
 set parentVol=%14
 set numErrs=%15
 set fatalErrCode=%16
 set fatalErrMsg=%17
 set lastVol=%18

default
 quit 1

endswitch
quit 0

 

Eh, don't know why my code isn't monospaced.

There is a free version of JP Software's command processor you can test this with at their website (download TCC LE and modify the command line above)

Edited August 19, 2008 by Guest
code tags are funky

[Mayoff]

I don't think the client will accept most of those commands. I believe the script/volume start/stop might be the only commands it will understand.

 

The event handler on the client is designed to trigger things like the closing of a program before a script. The client will probably not understand things like number of files copied, backup action, fatal errors, et.

[jabelli]

Well, we'll see what happens. At the very least, I will get the parameters that are actually passed in the log file. If there's no log file tomorrow, the it's not running.

[jabelli]

OK it ran this time, maybe there was some permissions issue. And yes, only StartSource and EndSource ran.