Hi all,

I know, there's been a lot of discussion on inactivity timeouts, but I
haven't found a hint that covers our problem:

>From time to time, one particular save set fails due to inactivity timeout;
in addition, the save.exe-process hangs and we can only kill it by
rebooting the machine.

Our environment is networker 6.1.1, server is solaris 8, client is a w2k-
mscs-cluster with open file manager 8.0 running.

Symptoms are:
- It is always the same save set that fails and the save set is located on
its own group of hard disks
- Increasing the inactivity timeout is useless; a manual save on the client
shows that the process seems to stop working after a few minutes
- Another save set on the same clusternode at the same time works fine
- The backup level is irrelevant; the error occured with incremental
backups as well as with level 5 backups
- While the abandoned save.exe process still hangs, every attempt to do
another save will fail; if the hanging process is killed (after a reboot),
backup may work for a few days until the error occurs again
- The last time the error occurred a scandisk on the volume reported errors

Now I have 3 questions:

- What do you think of the idea, the hard disks the save set is located on,
are the problem and are there any suggestions for testing this hypothesis?
- Are there any suggestions how we could kill the hanging save.exe-
processes on the client? We can't kill them by task manager nor by tools
like pskill nor does stopping the networker services help (and we don't
want to boot the server everytime the problem occurred)
- Has anyone any idea, please?

Thanks in advance,
Ingo

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=