Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Inactivity

Status
Not open for further replies.

ozi403

Technical User
Apr 29, 2002
54
TR
--- Unsuccessful Save Sets ---

* fsr3401:F:\ 1 retry attempted
* fsr3401:F:\ 10/11/04 19:02:46 nsrexec: Attempting a kill on remote save
* fsr3401:F:\ aborted due to inactivity

* fsr3403:F:\ 1 retry attempted
* fsr3403:F:\ 10/11/04 18:09:57 nsrexec: Attempting a kill on remote save
* fsr3403:F:\ aborted due to inactivity

What are the reasons of this inactivity? Any information?
 
it could be network load, it could be your parallelisms.
More info plz.
 
Per default settings (inactivity timeout for the group) is executed after a save has been startet but no data transfer did happen for 30 minutes. This is obviously "network related" although i remember a but on an older NW version.
However, most likely it is caused by name resolution problems.
 
I ran into the same issue backing up large volumes from a netapp filer with a private gig net. i raised the inactivity timeout to 240 and it runs flawlessly now.
 
This should not be necessary and i suppose a bug if you have to wait for 4 hours just to make the program work.
 
An incremental backup where there are very few files changed on a massive disk could give a timeout.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top