Agent trouble E8522 1

[realcaddy]

6 NT4server
1 with arcserve 2000 (only Backup server)
5 NT4 server with clientagent for NT installed
all server with a 2nd nic connected to the backupmachine
one server stop working after backup ~17GB (~ 3hours)with error 8522 failed to receive data from clientagent.

any ideas

Thanks for all answers

guido

 

[ARCserveGuru]

I am thinking there may be some connectivity issues, or the timeout of the agent is too quick. How is your netowkr connectivity? Can you do a continous ping with big packets without a timeout? Is the client agent service still running on the remote computers or does it bomb out? Does this happen with all the computers or just one? And what happens if you try the job through the network only, not the clients?

guru

 

[realcaddy]

Hi guru,

Thanks for quick answer.
Sorry for my very very simple english!

Now

I tested the connectivity with Ping -I 1024 IPadress -t for a few minutes (3-5 min) without any problems.

The agent service is allready runing. First the service runs with systemaccount (all other agent too), i changed this night to a domainadmin account (only the server with problems) and it runs fine. Was this my Problem, not enough accessrights?

The other client agents do the Job fine.

I will wait for 2-3 nights to see it will run or it will crash again.

regards from Germany

guido

 

[ARCserveGuru]

Regards from australia...

this could of been the problem, its hard to tell. We'll have to see how the backups go, and if the problem persists we'll get back right on it to try to find you a solution.

guru

 

[realcaddy]

hi guru,

after the serviceaccout has changed (see above)the backup runs fine on this machine, but may i have change the serviceaccount of each other clientagent too although the backup run well?

regards guido

 

[ARCserveGuru]

No, by service account, it is the arcserve service3 account. The machine running arcserve should have this service account only. When inputting security within arcserve for the backup of client agents use the ARCserve system account as well (as this account should be a domain admin with all the rights and as such should not have a problem logging in to these computers on the same domain.)

good luck

g

 

[realcaddy]

Hi guru,

yesterday i told you the backup is running, this night it stop again with the same error (grrrrr!). Now, I`ll try to look for the differences between the one server and the other servers.
I´ll check for drivers, firmware etc. so it takes a littlebit time. I think i have to do the job from the start and go step by step til all adjustments the same.

guido

 

[ARCserveGuru]

Hi guido,
I am thinking it is not an authentication issue as ARCserve usually just says in the activity log if it couldn't log on. Perhaps you should try re-installing the client agent. By the way, I am not sure if I mentioned this before but did you make sure that the client agent and ARCserve service packs were at the same levels?

Thanks, and good luck again.

g

 

[realcaddy]

hi guru,

i think i´ve solved the problem. i have uninstalled any copy of client agent, installed NT4SP6a again to have a basic installation of NT and installed the client agent.

The server backup´s now.

I have another question to you.

How can i restore a serverconfiguration like Disaster Recovery via Bootdisk AND client agent?

The tapemachine (HP Ultrium) is not local!
You remember 5 server (PDC, CAD and Office), 1 backup-server

I want to restore each server in a short time-window (1 or 2 hours

very kind regards

guido

 

[tbeeber]

E8522 is usually a timeout in communication between the server and the agent.

I had that problem on one server, and finally tracked it down to the switch being set at 100/full and the NIC at 100/half. The high number of collisions would occasionally (but not always) cause a time out.

Hope that helps.

 

[realcaddy]

Hi tbeeber,

thank´s, i have configured my Hardware (Nic/Switch) as follows, and of course, i think it´s OK:

Nic is set to 100/Full and the switch runs in automatic mode

i configure this because my client-nic´s are differend, so i have minimized the collisions because the switch handle this situation well.

guido

 

[tbeeber]

GuidoO,

Be careful with setting the switch to Auto. I have seen that cause lots of problems with throughput. I've seen it really kill throughput, especially on an full backup.

The Auto Setting is known to work poorly with NT, I don't know if W2K is any better. In the situation I described above, The switch was set 100/F, the NIC Auto. The NIC resolved to 100/H, which is clearly wrong. I've seen other problems when the NIC is set to 100/F and the switch set to auto.

I guess it can depend on the model/firmware of the switch you are using, I imagine some work better than others, but my general rule is set both sides to the speed you intend to use. It may be more trouble keeping track of the different ports, but it also takes the guesswork out of it.

It's your call, run a few experiments with different settings if you can. That's the only way to prove any potential solution.

Good Luck.

 

[realcaddy]

Thank´s for warnig

we had tested many configurations and we never lost data. so i think we have had much luck (lucky!?!?!, my simple bad english!!, i have to go to School again!!)

we have a cabletron emme switch and this thing is very easy and flexible.

i am testing foeward and answer again

guido

 

[tduplantis]

You cannot have the switch in Auto and the nics set to 100/full. This will cause you many problems. Either set the switch to 100/full and nics to 100/full, or both Auto.

Trust me, I have isolated many problems to mismatched settings on speed and duplex.

 

[realcaddy]

hi tduplantis,

i am back from hollyday tha last 3 weeks. today i was looking at tek-tips the first time and i see yous answer, thanks. but i switch the cabletron switech to "auto" mode because i think the cabletron is much inteligent as a nic so the cabletron handle the networkspeed well. isnt it?

I´ve tested various settings between nic´s and switches. the
result always wasn´t pleasing. last week a co-worker changed many components (computer, SCSI-cards, nic´s, servicepacks and so on) so i have to test and configure again!

i will follow your counsel and tell the result

guido

 

[csconner]

Very interesting thread... I've experienced similar issues. I will review our settings, off the top of my head I think are nic's a generall set to AUTO. I will have to check the switch settings with the network team.

Just to ensure I have my facts straight, the preferred config is to specify the same config on each end? Ex: 100/F on switch port and 100/F on NIC. or 100/H on each?

Thanks,

This has been a great find.. I'm glad I stumbled across TEK-TIPS.... csconner
Backups, Arcserve, anti-virus, W2K, WinNT

 

[rmv]

The preferred method is to set 100/F on the Nic and on the Switch port.

 

[csconner]

Ok great, I will proceed to check this out and adjust as necessary. csconner
Backups, Arcserve, anti-virus, W2K, WinNT

 

[Guest_imported]

Hello ... I've written a doc for 8522 errors

http://support.ca.com/techbases/as2000/as2k-18190.html

Good luck!