Attemting a remote kill on remote save

[Pener9]

Master server is running on Solaris 8 w/ ver. 6.0.1. Client (Alecto)is running Win2k sp2 w/ ver. 6.0.1. Client is a storage node with a StorageTek L20 locally attached. There is a 512 frame relay pipe between these two boxes. Two hops.

I am stuck.

Thank you for any help.

P.

--- Unsuccessful Save Sets ---

* alecto.ad.beepco.com:C:\ 2 retries attempted
* alecto.ad.beepco.com:C:\ 01/21/02 02:13:13 nsrexec: Attempting a kill on remote save
* alecto.ad.beepco.com:C:\ 01/21/02 02:18:14 nsrexec: Attempting a kill on remote save
* alecto.ad.beepco.com:C:\ write: Broken pipe
* alecto.ad.beepco.com:C:\ aborted due to inactivity
* alecto.ad.beepco.com:E:\ 2 retries attempted
* alecto.ad.beepco.com:E:\ 01/21/02 02:31:16 nsrexec: Attempting a kill on remote save
* alecto.ad.beepco.com:E:\ 01/21/02 02:36:16 nsrexec: Attempting a kill on remote save
* alecto.ad.beepco.com:E:\ write: Broken pipe
* alecto.ad.beepco.com:E:\ aborted due to inactivity
* alecto.ad.beepco.com:F:\ 2 retries attempted
* alecto.ad.beepco.com:F:\ 01/21/02 02:36:19 nsrexec: Attempting a kill on remote save
* alecto.ad.beepco.com:F:\ aborted due to inactivity
* alecto.ad.beepco.com:SYSTEM STATE:\ 2 retries attempted
* alecto.ad.beepco.com:SYSTEM STATE:\ 01/21/02 02:13:14 nsrexec: Attempting a kill on remote save
* alecto.ad.beepco.com:SYSTEM STATE:\ 01/21/02 02:18:14 nsrexec: Attempting a kill on remote save
* alecto.ad.beepco.com:SYSTEM STATE:\ write: Broken pipe
* alecto.ad.beepco.com:SYSTEM STATE:\ aborted due to inactivity
* alecto.ad.beepco.com:SYSTEM DB:\ 2 retries attempted
* alecto.ad.beepco.com:SYSTEM DB:\ 01/21/02 02:13:14 nsrexec: Attempting a kill on remote save
* alecto.ad.beepco.com:SYSTEM DB:\ 01/21/02 02:18:14 nsrexec: Attempting a kill on remote save
* alecto.ad.beepco.com:SYSTEM DB:\ write: Broken pipe
* alecto.ad.beepco.com:SYSTEM DB:\ aborted due to inactivity

--- Successful Save Sets ---

* alecto.ad.beepco.com:SYSTEM FILES:\ 1 retry attempted
alecto.ad.beepco.com: SYSTEM FILES:\ level=skip, 0 KB 00:00:44 0 files
* alecto.ad.beepco.com:SYSTEM FILES:\ 01/21/02 01:29:09 nsrexec: Attempting a kill on remote save
* alecto.ad.beepco.com:SYSTEM FILES:\ write: Bad file number
* alecto.ad.beepco.com:SYSTEM FILES:\ aborted due to inactivity
backup: index:alecto.ad.beepco.com level=9, 0 KB 00:08:26 0 files

 

[bommer]

Make sure the NIC in the client has the same settings as whatever port its plugged into. In our data center all ports are locked at 100mB full duplex, so Network settings on the NIC also have to be at 100 full or we get the "inactivity timeout" messages.

 

[jkalbus]

This looks to me like a DNS problem - make sure that the FQDN and the short name are known to both Networker Server and Client and make sure the Client is answering with the name you configured.
I had the problem that we had two clients which were actually one physical machine and backing up of one worked perfectly well, while the other got timeouts and "aborted due to inactivity".

Johanes