Let me preface this by saying that I am not an expert in this but it
sounds like something that happened to us also when we switched our old
machines to G4s also (same error 519). I tried several things but my
first thought though is because you said it worked through AppleTalk,
you might have to reinstall the Retrospect client software on the G4 and
when you go through the installation, it gives you the option of
selecting which protocol to use for that machine (either AppleTalk or
TCP/IP but not both). I had the wrong protocol on the G4s that didn't
backup. At the same time, I also through away some related preference
files and started fresh and it worked.
Anyhow, that's my two cents worth so good luck!
Michelle
--
Michelle Fleitz
University Publications
American University
(202) 885-5947
"Peters J B (Brooks) CRBE" wrote:
>
> Although I've had GREAT fortune with Retrospect through the years, I've recently run
>into a problem that has me stymied.
>
> I've just begun upgrading several client computers from older CPUs to G4s. While
>the rest of the 3 dozen systems on several scripted backups continue to perform
>normally, the G4 I started using as my desktop computer could not complete a backup
>without encountering a Type 519 error after about 60-80 MB has been copied to tape.
>What makes this a little strange is that once the error has been encountered, I find
>that Open Transport is no longer working for either TCP/IP (the protocol in use for
>Retrospect) or AppleTalk. The only remedy is to restart the system.
>
> I've replicated this failure on an out-of-the-box G4 on which only a small suite of
>COTS (e.g., Office 98, Outlook 8.2.2) had been installed. I tried using the
>Extensions Manager to select "Mac OS All" plus Retrospect Client, but the same
>failure occurred. For lack of any other ideas, I tried changing the protocol to
>AppleTalk and "Voila!" the backups run to complete ... both systems.
>
> I've read the Dantz Tech Note covering Type 519 errors, but nothing seems to apply.
>I'll proceed with some of the advice even though I can't think of why it should
>matter. In the meantime I want to ask the list if this sounds like anything you've
>seen before or if you have anything to suggest based on the problem description.
>
> To the best of my knowledge, all software is at an appropriate revision: Retrospect
>4.3 (server and clients) and Mac OS 9.0.4. Since several G3s on the same physical
>network wire operate w/o a problem, I assume the network is physically sound. If
>that's not a proper assumption, I can isolate the backup server and the clients to
>test them again using the TCP/IP protocol.
>
> Thanks for any comments or suggestions.
>
> Brooks Peters
> ---
> NAVSEA - NSWC, CarderockDiv
> Bethesda MD
>
> --
> ----------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives: <http://list.working-dogs.com/lists/retro-talk/>
>
> For urgent issues, please contact Dantz technical support directly at
> [EMAIL PROTECTED] or 925.253.3050.
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://list.working-dogs.com/lists/retro-talk/>
For urgent issues, please contact Dantz technical support directly at
[EMAIL PROTECTED] or 925.253.3050.
