Have you had a look at the length of folder/filenames?
I know there is an issue with restoring files with a length of >256
characters.
I haven't seen it slowing/stopping the backup process but it might be
something to consider.
Although, your process of adding d:\subdir1, d:\subdir2... Should not have
fixed this issues.
Something to look at in the mean time though.
dgk
-----Original Message-----
From: Robert Maiello [mailto:robert.maiello AT MEDEC DOT COM]
Sent: Saturday, 15 February 2003 6:34 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] AW: [Networker] Inactivity Timeout on particular
Save Set
I have an open case with Legato on a issue like this right now. Mine looks
like this;
- inactivity timeout on the d:\ only... other drives always work
- the save.exe on the client dies..roughly 428MB into the drive (about 9GB).
- we get an inactivity timeout (and waiting) for each retry on the client
- each retry leaves behind a hung nsrindexd process on the server for the
client.
- If there is a hung save.exe (usually it dies) it cannot be killed, the
client must be rebooted.
Its not a corrupt file index on the server because we removed and recreated
the index.
If it is an actual inactivity timeout because it can't transverse the file
system in enought time Networker is not cleaning up after itself. We
increased the inactivity timeout to 6 hours to no avail.
Here's what did work (as a temporary workaround). We've broken out the
drive into it's top level directories for savesets ..ie d:\subdir1,
d:\subdir2 ... The intent was to find a particular saveset/subdir that hangs
...some file is suspected.. What we've found so far is that now the
backups work (although the incremental on lot of these subdirs is 0KB). Not
a solution to the problem though..
In short, something on our d:\ drive is causing the process to die, but not
when we have the drive broken out into subdirs.
Robert Maiello
Thomson Healthcare
On Thu, 13 Feb 2003 09:57:05 -0500, Ingo Roschmann <ingo AT VISIONET DOT DE>
wrote:
>The save set _is_ large (70GB, many files), but:
>
>I don't think it is a problem of traversing the file system as
>- the error occurs only from time to time (say, every two weeks)
>- the save process on the client stops responding very early (after a few
> ten seconds) and then does not use any cpu power any more
>- the error also occurs when performing a full backup (whereas I must
> admit, that this did not happen spontaneously up to now, only when a
> hanging save process already existed on the client)
>- I already tried with an inactivity timeout of 12 hours, same results
>
>Details on the backup client follow, all I can say now, is, that the
>machine isn't slow; OS is Win2000; Networker version is 6.1.1 (server and
>client)
>
>Ingo
>
>
>On Thu, 13 Feb 2003 09:23:46 -0500, Stan Horwitz <stan AT TEMPLE DOT EDU>
>wrote:
>
>>On Thu, 13 Feb 2003, Ingo Roschmann wrote:
>>>
>>> I have checked the file indexes, no errors
>>> I have tried a manual full backup of the save set and when it stopped
>>> responding I tried it another time: the verbous output of those two
saves
>>> ends at exactly the same position, whereas an incremental backup does
>_not_
>>> stop at that particular file, but later it also stops responding; so I
>>> don't think there are "evil files" or something
>>
>>What type of computer and operating system is this backup client? Is the
>>save set very large in terms of the number of files in it? Does the save
>>set have a long directory tree? Perhaps you need to increase your
>>inactivity timeout setting to allow more time for that save sets file
>>system to be traversed by the NetWorker client, esp. if the computer
>>that houses this save set is slow.
>>
>>--
>>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.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
InterScan_Disclaimer.txt
Description: Text document
|
