Strange problem.....

[LeDam]

Everyday, when we make a backup of one of our win2000 server, we have a "no output" error. We have never seen that before!!! After looking at the log file, we think the backup are made but it retry.... why we don't know :

here is the log file :

03/21/02 02:31:18 AM nsrd: hn031:SYSTEM FILES:\ saving to pool 'LBKnormalfiles' (000237)
03/21/02 02:31:18 AM nsrd: hn031:SYSTEM DB:\ saving to pool 'LBKnormalfiles' (000237)
03/21/02 02:31:18 AM nsrd: hn031:C:\ saving to pool 'LBKnormalfiles' (000237)
03/21/02 02:31:19 AM nsrd: hn031:SYSTEM STATE:\ saving to pool 'LBKnormalfiles' (000237)
03/21/02 02:31:24 AM nsrd: hn031:SYSTEM STATE:\ done saving to pool 'LBKnormalfiles' (000237) 10 MB
03/21/02 02:31:33 AM nsrd: hn031:SYSTEM DB:\ done saving to pool 'LBKnormalfiles' (000237) 873 KB
03/21/02 02:31:49 AM nsrd: hn031:E:\ saving to pool 'LBKnormalfiles' (000237)
03/21/02 02:31:49 AM nsrd: hn031:\ saving to pool 'LBKnormalfiles' (000237)
03/21/02 02:32:35 AM nsrd: hn031:E:\ done saving to pool 'LBKnormalfiles' (000237) 143 MB
03/21/02 02:40:16 AM nsrd: hn031:\ done saving to pool 'LBKnormalfiles' (000237) 166 MB
03/21/02 02:41:36 AM nsrd: hn031:SYSTEM FILES:\ done saving to pool 'LBKnormalfiles' (000237) 223 MB
03/21/02 02:44:34 AM nsrd: hn031:C:\ done saving to pool 'LBKnormalfiles' (000237) 415 MB
03/21/02 04:30:56 AM savegrp: hn031:C:\ will retry 1 more time(s)
03/21/02 04:30:56 AM savegrp: hn031:SYSTEM FILES:\ will retry 1 more time(s)
03/21/02 04:31:02 AM nsrd: hn031:C:\ saving to pool 'LBKnormalfiles' (000227)
03/21/02 04:31:02 AM nsrd: hn031:SYSTEM FILES:\ saving to pool 'LBKnormalfiles' (000237)
03/21/02 04:32:13 AM savegrp: hn031:\ will retry 1 more time(s)
03/21/02 04:32:16 AM nsrd: hn031:\ saving to pool 'LBKnormalfiles' (001064)
03/21/02 04:40:25 AM nsrd: hn031:\ done saving to pool 'LBKnormalfiles' (001064) 166 MB
03/21/02 04:40:54 AM nsrd: hn031:SYSTEM FILES:\ done saving to pool 'LBKnormalfiles' (000237) 223 MB
03/21/02 04:44:20 AM nsrd: hn031:C:\ done saving to pool 'LBKnormalfiles' (000227) 415 MB
03/21/02 06:31:06 AM savegrp: hn031:C:\ will retry 0 more time(s)
03/21/02 06:31:06 AM savegrp: hn031:SYSTEM FILES:\ will retry 0 more time(s)
03/21/02 06:32:22 AM savegrp: hn031:\ will retry 0 more time(s)
03/21/02 06:32:24 AM nsrd: hn100:index:hn031 saving to pool 'LBKnormalfiles' (000227)
03/21/02 06:32:35 AM nsrd: hn100:index:hn031 done saving to pool 'LBKnormalfiles' (000227) 23 MB
* hn031:C:\ ! no output
* hn031:SYSTEM FILES:\ ! no output
* hn031:\ ! no output
* hn031:C:\ 1 retry attempted
* hn031:SYSTEM FILES:\ 1 retry attempted
* hn031:\ 1 retry attempted

Can somebody help me?
hn031 is under a firewall but we try with no rules and have the same problem. We have another NT station that has the same probleme sometimes (not everyday) and not under a firewall

 

[cptb]

I think this actually could be the result of different reasons. Network connections and system account has no permissions on the file system for instance. Also try to increase the inactivity timeout. If you're running any pre/post commands remove them for a temporary test backup to see if they could be the problem

 

[edskolnik]

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

 

[soder]

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

 

[edskolnik]

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

 

[soder]

The firewall shouldn't close the port.... telling the firewall not to do so will solve your problem.......