Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by twickland

  1. I recently updated to release 236, running on OS 9.2.2. The good news is that this release may finally have solved the communication problems we've been having with our OS X clients. There has been one peculiarity, however. When quitting Retrospect, if I have the program check media (DAT tape) at quit, the entire quit process seems to proceed normally, except that I then get a Finder message saying that Retrospect unexpectedly quit with a Type 2 error. This is true even if, after checking media, I click "Don't Quit," go back to the Directory, and then finally quit without rechecking media. If I quit without checking the tape, no error message is generated. When the Type 2 error message is generated, it's non-fatal and there seem to be no residual problems. Retrospect will autolaunch and automatically shut down the computer as normal, even if the computer is not restarted after the error. Has anyone else experienced this issue?
  2. We are experiencing the same problem here with an OS X (10.1.3) workstation client. Actually, we're experiencing a whole constellation of problems discussed in other threads. These are: 1) Retrospect Client spontaneously turns itself off. This appears to be initiated by the pitond process quitting. There seems to be no obvious pattern to this, but pitond won't stay running for more than a couple of hours. If Retrospect attempts access, we either get error 541, client not running, or error -1028, client not visible on network. 2) If we can manage to keep the client running until the backup of the client begins, the backup consistently fails after a few hundred MB have been backed up. The log indicates error 515, piton protocol violation. 3) If we attempt to reaccess, we then get error 505, client reserved. The client status on the client machine shows "In use by [backup script name]," and the pitond process is occupying 89-99% of processor cycles. The client status from the backup computer displays "Busy." It's remained in this state for 12+ hours, and I suspect it would stay that way forever unless pitond is killed. This is our only OS X client at the moment, and the reason we updated to 5.0 from 4.3. We have tried the known "fixes:" making sure that ethernet is listed first in the OS X network ports; turning off speed threshold in the backup script; reinstalling the client. We have not yet been able to back up this machine since switching to OS X. It backed up fine when booted in 9.2.2. (The Retrospect Client control panel is disabled in Classic, so presumably there's no possibility of a conflict there.) The OS X client is in a different subnet from the backup computer, which is running Retrospect Server 5.0.205 under 9.2.2. All of our clients have either a fixed address or a DHCP reservation, except for the ones in the backup computer's subnet. All regular MacOS and Windows clients have backed up flawlessly since we switched to 5.0. This is very frustrating, and is the worst problem we've experienced with Retrospect in 10 years of use.