We have this problem too, since upgrading to 7.3 (mainly with windows
clients).
The biggest gripe is that I have found no way of killing the
individual client saves from the server.
Under earlier versions, (on a Unix server), each saveset is
controlled by
a child process (nsrexec) of the savegrp process. You could kill these
processes and have the group continue on. This is particularly
important
if the backup server is part of the group, as it will still backup the
servers index and bootstrap. With 7.3, I can only abort the group
which stops any remaining savesets from starting.
Also, I have found that the new scheduler does not obey the
parallelism rules. The number of index saves can exceed the
group parallelism (by a very large number!!).
On 28/03/2006, at 6:05 PM, Oscar Olsson wrote:
We have noticed an increased degree of savesets that hang a group,
and never start, thus they will never time out either, and the
group will be flagged as running forever until its manually aborted.
Is this a known problem? If yes, does anyone have a LGTpa number
for this problem?
//Oscar
To sign off this list, send email to listserv AT listserv.temple DOT edu
and type "signoff networker" in the
body of the email. Please write to networker-
request AT listserv.temple DOT edu if you have any problems
wit this list. You can access the archives at http://
listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
