The inactivity timer is a watchdog that is reset by activity of the backup 
stream.
That means, if you set the activity timer to 10 minutes and it takes 15 minutes 
to walk the file system then the timer will fire. But if you receive one block 
every 599 seconds then it won't fire.

It is a useless feature and cause of a lot of problems. Just set it to 0 and 
you will have less problems.

Bye
Ernie

-----Original Message-----
From: Ed Skolnik [mailto:eskolnik AT INTERPUBLIC DOT COM]
Sent: Wednesday, June 18, 2003 5:29 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Can anyone explain how the save group inactivity
time-out works?


Can anyone explain how the save group inactivity time-out works? I am working 
with Legato support on this very question and they are
going to talk with engineering on this matter.



Does the clock start as soon as the save group starts or maybe when the client 
is 1st contacted to generate its work list? When the
timers stop when the 1st save stream is sent?



I am having lots of issues with a peculiar save group of about 47 client 
machines. The clients that fail are different every day.
Since I increased the inactivity time-out value from 30 minutes to 90 minutes I 
only get failures for one client (not the same
client each day).



I will summarize the information I get from here and Legato.




--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=