Here's an oddity. I used to get a lot of 519 errors when I had DAT
tape changers, but since switching to DLT I hardly have any problems
and the problems I do have are directly related to the end users
machine.
I ran DLT on a mixed 10BaseT with Hubs and switches for about 6
months before I
We are having problems backing up G4s over the network. Basically, they get
part way through the backup and then Retrospect looses the connection. The
problem seems to be at the G4 end as once this has happened they have lost
network connectivity until the next restart (sleep and waking seems
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
On 2/20/2001 6:45 AM, "Nicholas Froome" wrote:
We have 519's like a rash when backing up over a mixed 10/100 network using
3Com SuperStack 10/100 autoswitching hubs. Backup server is a beige G3 266
tower with a DDS-2 DAT drive.
Take a look at the autosensing on the Macs. There is an update
Back in November I started a thread on problems we were having
getting G4s to backup over our 10Mb Ethernet network...
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
On Tue, 28 Nov 2000, David Ross wrote:
If you look at how ethernet works, most of time anything you do will
mask errors. EtherNet has error recovery built in. So an undemanding
transfer, such as a Finder copy, will tend to get through, errors or
not. It's those programs that really hammer
So Retrospect reports errors that it finds in the network setup that
doesn't affect ANYTHING else? If these errors existed then why does
nothing else complain?
Yet.
I copy large files from one machine to another, but that never fails
Yet.
That's taking a rather simplistic approach
At 6:53 AM -0600 24/11/00, Don Foy wrote:
I want
everything perfect for a backup, since a less than perfect backup is
absolutely useless. That one byte it missed and didn't tell me about may
have been in the middle of a file that could cost me several thousands
dollars.
I agree, but in that
At 12:52 PM -0600 24/11/00, Pam Lefkowitz wrote:
So Retrospect reports errors that it finds in the network setup that
doesn't affect ANYTHING else? If these errors existed then why does
nothing else complain?
Yet.
I copy large files from one machine to another, but that never fails
Yet.
Hi Ken,
The members of this list who are suggesting that your 519 errors are due to
something other than a problem with Retrospect are not doing so because they
"blindly follow the dogma that Retrospect is perfect," it's because they
have found it themselves to be true...for some of them, even
to let the backups go a little
longer, but supposedly the G4 is failing again to get backed up.
Has anyone tried putting a new NIC into a G4 instead of using the on
board ethernet as a way to resolve this problem?
Todd Reed
On 11/24/00, Glenn L. Austin emailed about "Re: G4s and erro
At 9:02 AM -0800 26/11/00, Eric Ullman wrote:
he was
fairly certain that the problem was a bug in Retrospect.
I hope you understand that is NOT what I have been suggesting.
I need to finish rebuilding my network then I can give it a good
testing with a variety of backup servers, MacOS9 (X
I'm having the same type of problem with a lone G4 on a small
network. The other systems there, a blue G3, a beige tower G3 plus a
clone and a 6100, all seem to get backed up without fail.
[snip]
Just another data point:
We have 7 G4's here (early PCI to newest AGP) on our network here on
Adrian.
The termination problem was on the client, which is an ASIP server. It just
took out that particular client. However, if there is a termination problem
on the Retrospect 'server' then I guess you could see 519 errors.
It sounds like you need to talk with the folks at Retrospect in
on 11/23/00 2:09 PM, Ken Gillett at [EMAIL PROTECTED] wrote:
So Retrospect reports errors that it finds in the network setup that
doesn't affect ANYTHING else? If these errors existed then why does
nothing else complain? I'm sure that it does hit the network hard,
but IMO it should be
So Retrospect reports errors that it finds in the network setup that
doesn't affect ANYTHING else? If these errors existed then why does
nothing else complain? I'm sure that it does hit the network hard,
but IMO it should be written to cope with that. It should not the
task of the customer
So Retrospect reports errors that it finds in the network setup that
doesn't affect ANYTHING else? If these errors existed then why does
nothing else complain?
Yet.
I copy large files from one machine to another, but that never fails
Yet.
If it is a SCSI problem, then shouldn't
At 8:00 PM -0800 11/22/00, retro-talk wrote:
We are having problems backing up G4s over the network.
Basically, they get part way through the backup and then Retrospect
looses the connection. The problem seems to be at the G4 end as once
this has happened they have lost network
At 4:02 PM + 22/11/00, Nicholas Froome wrote:
We are having problems backing up G4s over the network.
Basically, they get part way through the backup and then Retrospect
looses the connection. The problem seems to be at the G4 end as
once this has happened they have lost network
on 11/23/00 6:50 AM, Ken Gillett at [EMAIL PROTECTED] wrote:
Just what is the 519 error, what actually occurs that causes
Retrospect to report it and how come it requires a restart of the Mac
in order to get its network running again?
Before the guys at Dantz get back from the holiday, I'll
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
If you are having 519 errors, there is a problem in your setup, either
hardware, software or network. You most likely either have a SCSI problem
(which was the case the last time I had a 519, termination problems),
Don, what were the other symptoms when you had the termination
problem? Did it
At 10:34 AM -0600 23/11/00, Don Foy wrote:
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
We are having problems backing up G4s over the network.
Basically, they get part way through the backup and then Retrospect
looses the connection. The problem seems to be at the G4 end as
once this has happened they have lost network connectivity until
the next restart (sleep and waking
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
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
I'm a different person than who brought up the initial issue. I was
asking this for my information. Thanks!
The Macs I have are older and they do not have the 10/100 built in.
Beige G3/300 and a 9600/G4-450.
Mmmm. OK, check the connection speed and duplex setting to the
hub/switch in
matt barkdull wrote:
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
29 matches
Mail list logo
