At 4:16 PM -0700 23/8/00, Irena Solomon wrote:
Because the Retrospect application and preferences are associated with a
particular user account, Retrospect is unable to function in unattended mode
if a user is not logged in.
This is disappointing. Is it also the case with Retrospect on NT? How
I am trying to run Retrospect (v4.3 now) on a 5200 or 6200 backing up to a La Cie DVD
RAM drive on the SCSI chain. I am backing up clients across the network (ASIP server
The problem is that Retrospect randomly freezes during the backup - it may be at 5mb
or 200Mb. I have tried
Not a solution, but something the 5200 and 6200 have in common that
the 6100 does not... IDE.
Also, the 5200 and 6200 don't have on-motherboard Ethernet. It's a
card for those, right?
Something to look at anyway. Maybe try a SCSI boot drive and
disconnect the IDE to see if that is the
The problem is that Retrospect randomly freezes during the backup - it may
be at 5mb or 200Mb. I have tried several different (5200/6200) machines
with similar results. At present I am using a 6100 without problems, but
cannot continue as the 6100 is needed as a workstation.
Has anyone else
To prevent intruders from disturbing the backup server while it's logged in,
use the BlackWatch screen saver http://penumbra.apple.com/blackwatch.html
to password protect your computer.
BTW, there's a posting on the BlackWatch web site that says:
(8/23/00) A patch for Retrospect (versions
Is there a way to get the Retrospect server to recognize that in a Dual Boot
configuration, each Retrospect client is NOT a *different* client?
I don't have a problem with burning two client licenses, I just want to have
my backup run exactly the same in Win98 and Win2K, whatever OS I happen to
On dual-boot Windows systems, you have to install the Windows client
software twiceonce for each operating system. You may install the client
either into the same directory under each operating system or into a
different directory for each operating system; neither choice has an impact
You're probably receiving error -1017 when running automatically because the
Retrospect Launcher service (the service that allows Retrospect to
autolaunch) is configured to log in as a user that does not have access to
this network volume (I'm assuming this is a Microsoft Networking volume).
Error 102 occurs when the Macintosh's CPU loses contact with the backup
device. The most common cause is improper SCSI termination, but it can also
be caused by other issues on the bus. I would recommend going through some
basic SCSI troubleshooting to isolate the problem:
* Run a
I had been using a APS HyperDAT Pro IV ( a Ultra Wide SCSI device with a
SONY DT-1000 mechanism) with retrospect 5.11 on an NT 4.0 SP6 machine for
about 9 months time with no problems at all.
Unfortunately the drive "died" chewing a tape in the process. APS is
replacing the drive under warranty,
Mail list logo