sent on
12/5/2000:
To: [EMAIL PROTECTED]
From: Nicholas Froome [EMAIL PROTECTED]
Subject: Network Attached Storage
Cc:
Bcc:
X-Attachments:
Message-Id: a04310101b5418047178f@[213.1.5.73]
Support
We are considering specifying a Quantum Snap Network Attached Storage device for a
Macintosh-based LAN
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
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'm setting up Retrospect 4.2 on a Mac to backup to a USB-attached CDRW drive with a
Mitsumi mechanism. It appears the mechanism might not be supported by Retrospect as it
does not work. I can burn and erase CDs using Toast so the drive functions OK.
My question is not "what drives does
Irena said:
Here's a little background on how the Retrospect client deals with network
connectivity, so we can better understands why this is happening and how it
might be addressed.
The Retrospect client does in fact initiate a check of the network once an
hour. It sends a request to Open
I'm running it on a beige G3 300MHz desktop. I wouldn't trust a Power
Computing system as a backup server...those are the Packard-Bell of the Mac
clone world.
Actually, most of the motherboards are the same as the Apple equivalents. They
changed other things like floppy drives and CD-ROM
what's the suggested route when not using FM Server? I use a standard copy of
FileMaker sitting on my ASIP server to run a set of database files which five or so
users make use of. Should I be tinkering with Applescripts or somesuch to close the
database files prior to back up?
Yes
--
...
5. Retrospect log reports "519" error for the G4 backup. From reading through the
archives, I gather that I should be looking for flaws in the network hardware, but I
don't really know where to start. Everything else about these servers is runnning
just fine.
This ties in with our
Ok, explain to me...I took a 220MB system file and compressed it down to 28MB.
And to recover any one file would require the whole archive to be decompressed..
Compressing a finite amount of data is one thing. Compressing a potentially infinite
amount of data on the fly, to multiple media,
Mark
can you help resolve a retrospect crash: Retrospect is version 4.3b1 on a
Mac G4 running OS9. Client is Win98 with Retrospect client v5.1, I am
running a backup server script.
The error is:
System clock seems to have changed, expected dd/mm/2000, hh:mm:ss
dates times and
Adrian
We are having problems backing up G4s over the network. Basically, they
...
Disable the OT AutoPush extension and try again - worked for us!
Have you got TCP/IP set as active and "Load only when needed" unchecked - I thought
so..
Unfortunately, we don't have the OT AutoPush
Mmmm. OK, check the connection speed and duplex setting to the hub/switch in Apple
System Profiler.
Hmm, You know, this one got me. I was not aware of any program that would get speed
and duplex on a Mac.
I just checked Apple System Profiler (version 2.4.4) and it don't show me. Maybe
Before the guys at Dantz get back from the holiday, I'll let you in on a
little secret - 519 errors are some of the most common. They are not caused
by Retrospect, just found by it.
Retrospect is very demanding. It requires that everything be right in your
machine and network setup (Imagine
Keith
Secondly, I'm looking to buy a Mac-compatible CD-RW drive for use with Retrospect
4.3. I've looked at the hardware compatibility list, but the problem I'm having is
that a lot of these drives have been superceded by newer models.
So, can anyone recommend a recently purchased
Chad
I have a client who is running Retrospect 4.1i and they recently installed a
new firewire drive that they partitioned into about 6 separate partitions to
organize their data. The strange thing is, that when you open up Retrospect
and go to Configure/Devices, all of those partitions are
Rob
A client whose imac I recently added the Retro client to has complained of
instability since it was added. He has the configuration above. I am
thinking of upgrading him to OS 9.04 anyway but is there any known conflict
with OS 8.1 or IP net router?
I have never known of any version of the
RE: Holding disk
This is something that can be done now; just run one backup to the holding disk, then
another from that to tape.
If this two-step process was managed by Retrospect (rather than being done with two
scripts) it would still have to copy and verify on each pass so there
Julia
Currently, we are using one DDS-3 tape drive for our entire local base of about 70
users
I am also interested in doing a remote backup of our NYC office. They have static
IPs, and could possibly be added to our backup sets.
So, should I keep the same tape system (DDS-3) and get a
I can't speak for everyone but I hope you keep this discussion on the list. If
it does happen to go off-line, I would greatly appreciate a copy of the final
thoughts.
I agree. IMHO the biggest problem with tape drives is not the purchase cost or the
tape costs, but the sheer level of grief
Just to update everyone, we have found that switching the clients to
AppleTalk rather than TCP/IP has eliminated all the errors we were
experiencing (As suggested by Brooks Peters in the thread "G4
Client's OT Wiped Out by Backup via TCP/IP"). The backup is not as
quite as fast (say 40
20 matches
Mail list logo
