Error 519 every single day

[scotty321]

Hello there,

 

We have Retrospect 8.0.736 running on an Intel iMac machine running Mac OS X 10.5.7, and we have 10 client machines (all Intel iMacs running Mac OS X 10.5.7) running Retrospect Client 6.3.019.

 

Every single night at 10pm, Retrospect 8 on the server tries to backup all 10 clients machines onto an external hard drive.

 

Every single night, ONE of the 10 client machines fails with an error 519 message (network communication error). If we restart that client machine the following morning, then it is totally fine for that night's backup.

 

BUT THEN -- the error 519 message MOVES ONTO a different machine for that night!

 

So, in other words, every single day, A DIFFERENT MACHINE ON THE NETWORK isn't backed up due to an error 519 message!

 

The error 519 message floats from machine to machine, and when we restart the machine that has the error 519 message, it's okay for a while until Retrospect thinks that it is that machine's turn for the error 519 machine.

 

Here's a visual way of looking at it:

 

NIGHT 1-- Client computer 1 has an error 519. We restart client computer 1, and it's fine on night 2.

NIGHT 2 -- Client computer 2 has an error 519. We restart client computer 2, and it's fine on night 3.

NIGHT 3 -- Client computer 3 has an error 519. We restart client computer 3, and it's fine on night 4.

NIGHT 4 -- Client computer 4 has an error 519. We restart client computer 4, and it's fine on night 5.

NIGHT 5 -- Client computer 5 has an error 519. We restart client computer 5, and it's fine on night 6.

etc.

etc.

etc.

etc.

 

Can anybody please help by shedding some guidance on this? There seems to be a bug in either Retrospect 8 on the server, or Retrospect Client 6 on the client computers that is causing this problem.

 

Thanks,

Scott

[Mayoff]

Sounds like random 519 errors, which is not too strange.

 

http://kb.dantz.com/article.asp?article=6308&p=2

[scotty321]

Thanks so much for this link, Robin. This is a very informative article.

 

However, we never received error 519's before upgrading to Retrospect 8, and then they started happening daily. So this seems to be some sort of a Retrospect 8 issue.

 

Nonetheless, I will still check the different parts of our network to see if I can find any problems with our network.

 

Thanks.

[impala]

what happens if you restart them all in one day? Do they all work that night?

 

I've found it helps to schedule my windows clients to restart their retrospect client service every day. The service restarts even if the computer does not. This should be possible on MacOS, but I haven't had the need to find out how to do it.

[scotty321]

Thanks for your message. Yes, it seems that if we restart all of them in one day, then they all work that night. Does that mean that we need to restart these computers every single day, just to get Retrospect 8 to work properly?

 

Also, it seems like only 5 of our 10 computers experience this problem. The other 5 are totally okay. But all 10 are on the same exact switch.

[CallMeDave]

Impala wrote:

>The service restarts even if the computer does not. This should be possible on MacOS,

 

 

scotty321 asked:

>Does that mean that we need to restart these computers every single day, just to get Retrospect 8 to work properly?

 

 

Impala was specific in suggesting that restarting the unix process (retroclient) might be a solution for your problem; he never failed to recognize that restarting the entire computer OS would be an extreme solution.

 

retroclient could be started/stopped (or loaded/unloaded via launchd) with a simple cron script. But it would make sense to test to see if just restarting retroclient effects your communication issue.

 

only 5 of our 10 computers experience this problem. The other 5 are totally okay

 

Which does put a dent in the "this seems to be some sort of a Retrospect 8 issue" theory; if it were a software issue wouldn't you see it on all the machines?