Jump to content

jabelli

Members
  • Content count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jabelli

  • Rank
    Newbie
  1. The client was installed under a domain admin account and is running as the system account. I should have mentioned that the client has just had windows installed. I believe the 15th was the first backup performed since Windows was installed.
  2. The server is Windows 2003 Standard. Retrospect is 7.6.123 with driver update and hotfix 7.6.2.101. No other add-ons are installed. The client is Windows 7 Ultimate x86 with Retrospect client 7.6.106. The retrospect client history shows the last backup on 4/15. However, both the log file generated by the client event handler and the server history log show that the client was backed up.
  3. jabelli

    notify if no backup in 7 days

    He probably has the same problem I do. It's falsely claiming that it hasn't been backed up when indeed it has. I'm just about to make a post about it.
  4. jabelli

    Vista , 7.6 and Activity Monitor

    Killing the task is an extremely messy way to solve the problem, and could cause you other problems. If it's physically possible, log in at the console to see what Retrospect is doing. Otherwise, follow the document Mayoff posted above.
  5. jabelli

    Vista , 7.6 and Activity Monitor

    As I stated above, Retrospect had been listening on 1937, and Activity Monitor was incrementing its port, trying to find Retrospect. I'm pretty sure that Retrospect only listens during scheduled operations, so if you're looking for open ports when just running Retrospect, you're not going to find anything. This was with a new install.
  6. OK it ran this time, maybe there was some permissions issue. And yes, only StartSource and EndSource ran.
  7. 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.
  8. 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)
  9. 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.
  10. 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.
  11. 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.
  12. jabelli

    Vista , 7.6 and Activity Monitor

    Well? Any progress? Now the exchange server has ejected the tape, and I don't know if there was an error or it's just looking for a second tape. EDIT: This a different server than the one discussed previously, with the same problem.
  13. jabelli

    Vista , 7.6 and Activity Monitor

    I am having this same problem on Windows Server 2003. I have tracked down the problem. Retrospect.exe is listening on port 1937. Retromonitor.exe is trying to connect to port 2200. Then it adds one and tries to connect to 2201, and so on. However, it seems to be remembering the last port number it tried (somewhere) and starts on that port number the next time it is started. So, in about 3 days it will either crash completely and never start again (when it rolls over to 65536) or will roll over and start at the beginning. Where is the last port used stored, so that I may change it until you fix this? EDIT: This is a new install.
×