AREA: Server Rack/Back-up Systems
FORUM: Legato: NetWorker back-up
SUBJECT:;! no output error
HANDLE: LeDam
POSTED ON: Apr 16
QUESTION:
I have a strange problem since some days ago :
Our server call HS1.crelan.be (10.1.1.2). It's working under windows 2000
Our mailsweeper under firewall HN031.lbk.be (172.1.13.24). Also working
with windows 2000
Backup are launch at 2h30. Here are message that has benn display in log :
03/27/02 02:30:42 AM nsrd: hn031:C:\ saving to pool 'LBKnormalfiles'
(001261) 03/27/02 02:30:49 AM nsrd: hn031:SYSTEM FILES:\ saving to
pool 'LBKnormalfiles' (001261) 03/27/02 02:32:33 AM nsrd: hn031:SYSTEM
FILES:\ done saving to pool 'LBKnormalfiles' (001261) 223 MB 03/27/02
02:33:58 AM nsrd: hn031:C:\ done saving to pool 'LBKnormalfiles' (001261)
415 MB ..... 03/27/02 04:31:11 AM savegrp: hn031:C:\ will retry 1 more time
(s) 03/27/02 04:31:11 AM savegrp: hn031:SYSTEM FILES:\ will retry 1 more
time(s) 03/27/02 04:33:17 AM nsrd: hn031:C:\ done saving to
pool 'LBKnormalfiles' (001261) 415 MB 03/27/02 04:40:33 AM nsrd:
hn031:SYSTEM FILES:\ done saving to pool 'LBKnormalfiles' (001261) 223
MB .... 03/27/02 06:31:53 AM savegrp: hn031:C:\ will retry 0 more time(s)
03/27/02 06:31:53 AM savegrp: hn031:SYSTEM FILES:\ will retry 0 more time
(s) 03/27/02 06:32:45 AM nsrd: hn100:index:hn031 saving to
pool 'LBKnormalfiles' (001261) 03/27/02 06:32:58 AM nsrd: hn100:index:hn031
done saving to pool 'LBKnormalfiles' (001261) 47 MB
* hn031:C:\ ! no output
* hn031:SYSTEM FILES:\ ! no output
Backup are OK, i use mminfo to verify but it's a problem because we have
several clients starting at 4h30!! It's very strange because the timeout is
240 min... So why retry it 2hour after???? Is it a legato problem or is it
because it's backup under a firewall??? Please help... thanks for all....
-------------------------------------------------------------------
HANDLE: edskolnik
POSTED ON: Sep 13, 2002
REPLY:
Has Legato support helped you because they ahven't come up with anything
for me . Issue # 3026233
I also get the following on the client...
rror: nsrexecd: failed to write nulhandshake on 240 error code 154
Ed Skolnik
-------------------------------------------------------------------
HANDLE: soder
POSTED ON: Sep 14, 2002
REPLY:
Well.... this is a known issue. NetWorker is opening a port in the firewall
during the start of the backup and is supposed to get some inforamtion from
the client behind the firewall after the backup has been preformed (index
and stuff).
The firewall isn't glad about this and is closing this port(after a while)
so the backupserver can't get this information. That's why you got this
error "no output".
On a Solaris machine you got a "TCP timeout" value to tune and you might
have something simmilar in Windows.....
-------------------------------------------------------------------
HANDLE: edskolnik
POSTED ON: Sep 16, 2002
REPLY:
If the firewall is closing the port after a while , what does this have to
do with changing the TCP timeout on the backup server? If it's closed ..
doesn't it stay closed?
Ed
-------------------------------------------------------------------
HANDLE: edskolnik
POSTED ON: Sep 16, 2002
REPLY:
*********** UPdate *****************
If the firewall is closing the port after a while , what does this have to
do with changing the TCP timeout on the backup server? Also How do you
see what the time out value is on Sun, then now do you change it?
If it's closed .. doesn't it stay closed?
-------------------------------------------------------------------
HANDLE: edskolnik
POSTED ON: Sep 23, 2002
REPLY:
***** Hello anyone out there care to comment! *******
-------------------------------------------------------------------
HANDLE: edskolnik
POSTED ON: Sep 24, 2002
REPLY:
FR: isivapal
3026233 Error: nsrexecd: failed to write nulhandshake on 240 error code 154
LGTpa43607
Engineering is still analysing some issues and had given us their
recommendations but we have further questions on some of their
recommendation. In fact I have a conference call with the engineer on this
in 20 mins.
Here is part of the dialogue from the engineer:
o The * <client>:<filesystem> ! no output messages appear
to originate from savegrp.exe when it attempts to read the
log created by nsrexec while executing the client save. The
message can be generated when either the log is zero length
or when no saveset completion message is found in the log
(successful to not). The "no output" message is documented
in savegrp(1m).
o The client log files (nsr\tmp\sg.<group>.<client>.XXXXXX)
are normally deleted but can be retained if the debug level
is greater than 1 (eg. -D2). This would require running
savegrp manually.
I will let you know once we have clarified a few more points with the
engineer. Thanks Indy
--
Note: To sign off this list, send a "signoff" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
