Jump to content


  • Posts

  • Joined

  • Last visited

ibeatty's Achievements


Newbie (1/14)



  1. Greetings. Alas, I also have suddenly started seeing the dreaded elem.c-923 error. I've been running Retrospect without problems for months and months, and I didn't make any changes near the time that this started. All of a sudden, I started finding that when I check my backup server in the morning, Retrospect will have died with a last gasp of "elem.c-923!" The log doesn't show anything useful. It has the last successfully completed backup, then a blank line, then the "Internal consistency check failed" entry with no timestamp. So I can't tell if it's associated with the start of backing up another client, or something that happens while scanning, or what. Details: I'm running Retrospect 6.1.126 on Mac OS X 10.4.3 on a 400 MHz G3 iMac ("smoke" translucent body) with 384 MB RAM. It's acting as a dedicated network backup server, backing up via firewire to a Granite Digital hot-swappable drive enclosure into which I place IDE drives. Retrospect has 20 network clients registered, though four of them aren't turned on very often. Most of the clients are desktops backed up by a script that runs overnight but not during the day; a few are laptops backed up by a script that runs 24/7; and one is a server backed up during a specific interval in the early morning, after the desktop script is done. I alternate between two backup sets, each one on a different 250 GB IDE drive that gets inserted into the drive enclosure. I've had the elem.c-923 with both backup sets. Suggestions? Wisdom? Thanks!! :ian
  2. Absolutely bloody brilliant. That was it exactly. I'd forgotten all about the Jaguar firewall. Thanks^9. Cheers, ..Ian
  3. It is not visible there; I "forgot" it after upgrading to the new OS and client versions. (Thanks for the suggestion, though.) ..Ian
  4. Greetings. I've got Retrospect Workgroup 5.0.205 running on a Mac OS X 10.1.5 server. I just installed Retrospect Client 5.0.536 on two OS X machines. It seems to work fine on the one running 10.1.5. On the 10.2 (Jaguar) machine, however, there is a problem. The machine is visible in the "Network" panel of the server, as one of a few OS X machines accessible. When I click on the Jaguar machine in that list to configure it, however, I get an error dialog with "Can't log in, error 541 (client not installed or not running)". As far as I can tell, the client is in fact running. Process Viewer lists a running process named "pitond". When I launch the Retrospect Client app, the on/off switch is in the "on" position. The client is an otherwise perfect network citizen: it's pingable, and it backed up just fine with an earlier version of the Retrospect Client before I upgraded to 10.2. Anybody got any good ideas? I was under the impression 5.0.536 was supposed to work with Jaguar... Thanks, ..Ian
  • Create New...