Darned Eudora IMAP client that every so often decides to check the
server (for no apparent reason)--see my correction below.
The easiest way to prevent Retrospect from using temp system memory is to
assign it more than 8,192 K in the Finder.
Eric Ullman
Dantz Development
I don't think that is
And in case you're wondering who turned on that 'temp memory' setting when
you didn't even know it existed - Apparently the 'temp memory' setting was
recommended a couple of versions ago; since then it has become preferable to
leave it off. If you upgraded your copy of Retrospect from an earlier
I've been backing up ASIP 6.2/OS 8.6 via remote client 4.2 for over a year
without a problem.
Just to clarify - you are running the retrospect client on your ASIP server,
and the Retrospect app on a dedicated machine, correct? Running the
retrospect app on your ASIP server is a bad idea.
What
I have the Retrospect app on our other Mac server which has the same
setting up just a different RAID. I have to do this until I get this
solved, or I would have two computers crashing after each backup. I have
switch the app and the remote client on the two server and I get the
same problem on
pardon for butting in,
We are also running an Appleshare server and Retrospect on the same machine - the
advantage to this is the higher datarate from backing up local drives than backing up
over the network.
Apppleshare 5.0.3, Retrospect 4.2 on a Powermac 8500/150 w/256 Meg. RAM; Micronet
