Jump to content

Search the Community

Showing results for tags 'engine'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 13 results

  1. Don Lee

    New Windows user wants advice

    I've been running Retrospect forever. I am quite familiar with its operation on the Mac. I now am looking at a Windows installation and am rather surprised at some of the differences. The biggest one is that on the mac, the "engine" runs whether anyone is logged on or not, but on Windows, it seems that if I log off, Retrospect stops cold. I don't see (so far) a way to leave it running as a service. I also note that the Windows GUI reminds me of the Windows OS GUI, which has a bunch of annoyances, like the fact that the dialog boxes are generally not resizeable, even when it would be really nice. The displays of media sets, history and sources are (I think) less useful and efficient than the GUI on the mac. Is there anyone on the forum with experience with both Mac and Windows products willing to alert me to any land-mines out there? Do I need to just finish reading the documentation? (600-page! Good stuff.) Thanks, -dgl-
  2. I have seen this now several times, but I don't know how to reproduce it. It is with retro v 9.0.2 (107), both engine and console. Setup is the console running on Macbook Pro laptop running 10.5.8, and engine running on Mini with 10.6. The problem is that if I connect to more than one engine, if I leave the console open a while, the console will end up showing the wrong info in the various windows. For instance, if I look at the scripts, it will show scripts for both engines in the same window, as though it has merged the lists. Clicking on one of the scripts will show the wrong source and destination media sets/sources - again, with names that are consistent with being from the "other" (wrong) engine. I have been unwilling to "play with" the console in this state, being unsure what it might actually do to my backup data while obviously confused. I have not run v10 enough to see if this happens there, too.
  3. Hi all, In my workplace, we're currently using Retrospect 11.5.3 to backup all of our systems. We're considering making the jump to RS 12, but I'm concerned by some of the weird quirks I've encountered in 11.5.3 (such as: scheduled backups not running - engine needs a reset, backup clients not found - sources need to be relocated, reserved backup clients - client system needs a reboot, among some others....) and would like to get an idea of whether I should expect things to be better or worse in version 12. So before we go any further in consideration, I'd like to ask forum users about their experience with Retrospect 12. Any input as to what issues I might expect, or expect to be resolved, what works, what doesn't, and anything relating to 11 vs. 12 overall would be greatly appreciated. Thanks, Jeff
  4. Just accepted the offer to update to 11.5.3 and am now regreting it. Launching the application never comes out of "connecting ..." which I discover is because Retrospect Engine will not start. Doing this manually from within the Mountain Lion System Preferences does absolutely nothing. Button lights up blue, accepts the click to start the engine ... nothing happens. Have re-started the system but no improvement. Any ideas how I get past this please ? Thanks Rod
  5. What's new with 11.5.1? Have update notes been posted somewhere? I assume it's bug fixes, but it'd be nice to know what has been fixed. Thanks.
  6. Retro 10.5.0(145) on Mac OS X 10.8.5, Mac mini (summer 2013), 16 GB mem My engine is stuck. I have a pro-active script that says "not active", which runs every 1 day. Active every day between 2:30 AM and 9 AM. It has not actually done anything since Nov 1st, though. I tried duplicating the script, and setting the "active" time to 1:pm to 5 PM on Monday (today) of the duplicate - called junk-script.. junk-script says it is (Not yet determined), and has been that way for a couple of hours. No other activities are active. Looking through the log, it looks like *none* of the proactive scripts are running - since Nov 1st. Is there something I can do to crank up the debugging to tell me what the engine is stuck on? I've had this happen before, and I may not notice it for several days, which is Bad Juju. Thanks,
  7. I hit a hang at some point since the 26th of January. I saw the engine busy doing a scripted verify of all my sets on disk yesterday (It appeared to be running, from the flashing lights on the external disk(s).) Unfortunately, it was still "running" today, with the Retro engine at 100% CPU (one CPU @ 100%), and no lights flashing. There were two scripts showing "busy" in the Retro console. I tried to stop the two activities, and tried to stop the engine the "normal" way through the CP. I had to force quit the engine to free it. I snapped the screen with the two activities, and also the activities after engine restart. Note that the two activities that were "done" have vanished - no evidence that they happened. I include screen snaps of the two activities with both summary and log, and also a screen snap of the console after recovery. THe sample, as taken by the Activity Monitor while the engine was hung. This is a bug. Retro was "stuck" for almost a week. (Retro engine 10.5.145, Mac OS X 10.8.5 - Console retro 10.5.145, on Mac OS X 10.6.8) Sample_RetroEngine.txt
  8. I note that on my server machine, the files in /Library/Application support have what I consider the wrong permissions. Most of the files here are owned by root, but the bundles and their contents are owned by the user who installed the engine. It is a security problem to allow a "normal" user to manipulate these files directly. (first cd "/Library/Application support") virtue:Retrospect sysadmin$ ls -al total 30736 drwxrwxr-x 19 root admin 646 Aug 12 19:52 . drwxr-xr-x 20 root admin 680 Apr 15 11:45 .. -rw-rw-r--@ 1 donlee admin 6148 Oct 6 2011 .DS_Store drwxrwxrwx 3 root admin 102 Apr 3 15:45 Catalogs -rwxr-xr-x 1 root admin 1488072 Aug 12 18:13 Config80.bak -rwxr-xr-x 1 root admin 7731400 Aug 13 02:37 Config80.dat -rwxr-xr-x 1 root admin 86988 Jul 12 17:21 ConfigISA.bak -rwxr-xr-x 1 root admin 86988 Jul 12 17:21 ConfigISA.dat drwxrwxr-x 3 donlee staff 102 Jul 4 10:41 RetrospectEngine.bundle drwxrwxr-x 3 donlee staff 102 Jul 4 10:41 RetrospectInstantScan.bundle drwxr-xr-x 4 root admin 136 Aug 13 02:37 RtrExec.dir drwxr-xr-x 2 root admin 68 Apr 4 13:36 RtrISAExec.dir drwxr-xr-x 3 root admin 102 Apr 3 15:43 RtrSec.dir -rwxr-xr-x 1 root admin 120003 Aug 12 19:52 assert_log.utx -rwxr-xr-x 1 root admin 6171156 Aug 13 02:37 operations_log.utx -rwxrwxr-x 1 root admin 211 Aug 12 19:53 retro.ini -rwxr-xr-x 1 root admin 18466 Jul 12 17:21 retroISA_log.utx -rwxrwxr-x@ 1 root admin 195 Jul 12 17:21 retro_isa.ini -rw-r--r-- 1 root admin 0 Jul 11 05:00 uuid_temp.log virtue:Retrospect sysadmin$ ls -al Retro* RetrospectEngine.bundle: total 0 drwxrwxr-x 3 donlee staff 102 Jul 4 10:41 . drwxrwxr-x 19 root admin 646 Aug 12 19:52 .. drwxrwxr-x 4 donlee staff 136 Jul 4 10:41 Contents RetrospectInstantScan.bundle: total 0 drwxrwxr-x 3 donlee staff 102 Jul 4 10:41 . drwxrwxr-x 19 root admin 646 Aug 12 19:52 .. drwxrwxr-x 4 donlee staff 136 Jul 4 10:41 Contents virtue:Retrospect sysadmin$
  9. As part of of the upgrade process, an opportunity to upgrade the Retrospect Engine is offered. It will always fail since no mention of requiring the engine be stopped is ever mentioned. This requirement was probably forgotten and never written down in the previous upgrade. Upgrades are not a daily occurrence. It should not be necessary to either guess or read through pages and pages of documentation to be reminded of this. I would expect it would take minimal time and testing to simply add text to the UI noting that the engine must be stopped for a sucessful upgrade to occur.
  10. When the 10.0 console is connected to a 9.0 engine, it occasionally offers to upgrade the engine by putting up a dialog box. For some of my installs, the connection is pretty slow, and doing the upgrade would be dicey at best, and in any case, the last thing I want is to "accidentally" hit "return" on one of these dialogs, and start an upgrade process that I may or may not be able to abort before it does something I don't want. I have not experimented with this, for obvious reasons. I don't think the engine should make these offers that can so easily be accepted. At minimum, there should be a way to "turn them off". Some of my installs will be stuck on v9 for some time, and the whining from the console will be an unnecessary annoyance. Yes, the console should be able to upgrade the engines, but the operation is very rare, and should be explicit.
  11. I experienced an annoying bug today while adding a Retrospect client. The client, a Windows 7 machine running client version 7.7.114, was successfully added via direct IP address. I then attempted to change the name to a name containing 31 characters. The name change window accepted the new name, but shortly after I clicked the Change button, the engine crashed. The crash apparently also wiped out the Config80.dat file, because when the engine restarted itself, it had lost a number of configuration changes I had recently made, which suggests it had restarted using Config80.bak. However, Config80.bak apparently was also corrupted in the process, as when I attempted to re-add the client, I got the always-helpful "An error occurred" message. I attempted reverting to ever-earlier backed up copies of Config80.dat (quitting the console and stopping the engine each time, of course), each time experiencing the same engine crashes and Config80 file corruption. It was only after 5 or 6 such attempts that I remembered that we had previously needed to truncate a client name in Retrospect 8. When I shortened the new name to 30 characters, I was finally able to successfully change the name and avoid crashing the engine. Obviously, the Retrospect 9 console either should refuse to accept a longer client name than is acceptable or should handle such an error more gracefully.
  12. Something fails at the completion of the backup on a currently installed Retrospect version. Restarting the Engine has cleared this problem before. What seems to happen is that the running backup never completes- stick in the last step, sending email or the previous step- closing... What information is needed to troubleshoot this problem and how can I get some advice?
  13. I have a Retrospect 9 multi-server install, with a 4 drive library attached over SAS. Last night, backups stopped, and I get an error that the engine is stopped. I've rebooted, and cannot get the engine to restart. Running 10.6.8, 9.0 latest version with plugin for multiple drives. Getting com.retrospectengine Exited with exit code: 255 (com.retrospect.retroengine) Throttling respawn: Will start in 10 seconds #2Comand Line is /LIbrary/Application Support/RetrospectEngine.bundle/Contents/MacOS/RetroEngine Assertion Failure at "elem.cpp-1138" on threadID 0x105355000 Any ideas, I have a call into retrospect, but this is backup server that handles many a servers backup, and last nights backup was missed as a result. Need to backup first thing this am. Please relay any golden suggestions if you have any. Thanks, Dan