Client licenses are now stored in Retrospect's License Manager. If you had
old-style Retrospect Clients with activator codes, then the License Manager
automatically knows how many client licenses (i.e., a 10-pack) you already
have. When you forget a client computer, the License Manager makes
I am testing a Snap Server loaned by Quantum next week.
I would appreciate anyone with experience of backing these up using Retrospect
emailing me their observations. I will summarise later to this list. Specifically I'd
like to know:
* what machine the Snap is mounted on for backup
* OS of
Thanx for your reply!
The passwords are not written on a pice of paper next to the server...
When it comes to speed, one thing hit me, I use the internal SCSI-1 socket.
Maybe a SCSI-2 card wold speed up performance.
Thank you for your advice. They are really appreachiated.
thanx,
/ jakob
With all this talk of compression, speed, different drives, etc.,
would it be possible for someone at Dantz to set up a database that
Retrospect users could contribute to with the purpose of documenting
the different systems and their performance?
At a minimum, it could include backup
Phillip and Rhona said:
We are also running an Appleshare server and Retrospect on the same machine -
...
This configuration has been very stable for us.
I can think of a number of extremely good reasons not to run Retrospect on a
fileserver:
1 - you can't work on fine-tuning the setup
I ran a script earlier today as I had to pause.
I thought everything was in order but now, just before leaving for home, I
noticed the drive is acting very strange.
Led #2 on my VXA drive is blinking but it never stops. Blinking means that
the tape is loading but does that load take like 30
I've done some reconfiguring of our backups, and I'm getting an error
message that I can't find listed anywhere.
The error number is -33 (directory full). It also says it can't save
the snapshot. I've got tons of disk space (this is a HD file), so I
don't think that's the issue, unless
A blinking LED may indicate trouble in a drive as well. Check
your documentation. It should tell you exactly what the blinking
light means. Usually if it is blinking that long, it is not a
good sign.
brian
--- Original Message ---
jakob krabbe [EMAIL PROTECTED] Wrote on
Thu, 13 Jul 2000
there is a limit to the number of nested directories an files you can
have...and it depends on your operating system. Apple's TIL has info on the
max number of directories in a tree...I can't remember off the top of my
head.
HTH
- Original Message -
From: "Julia Frizzell" [EMAIL
Julia,
This can be a problem with file backup sets. As you know, a file backup set
is basically just a Macintosh file with all of your files condensed into it.
As such, it has a data fork and a resource fork. The resource fork stores
the catalog of the data, including a record of every single
if your HD file is near 2 GB in size, that's your problem. The limit is 2Gb
for storage set files, per Retrospect's manual.
Cesar
At 01:20 PM 7/13/00 -0400, you wrote:
I've done some reconfiguring of our backups, and I'm getting an error
message that I can't find listed anywhere.
The error
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
A drive can go bad at any time for any reason. You are not alone
in this. Hardware fails. If you are having trouble with it, get
it fixed and move on.
Brian
--- Original Message ---
jakob krabbe [EMAIL PROTECTED] Wrote on
Thu, 13 Jul 2000 20:02:42 +0200
--
At 10:21
13 matches
Mail list logo
