We have one Windows 2003 Server client whose backups only succeed once
or twice a week (other identical machine have no problems). It is
running Win2003 Server R2 Enterprise edition with SP1. It has dual gig
NIC cards (broadcom BCM5708C) mapped to two IP addresses, which both
forward & reverse lookup with no problems. It is hosting MS Virtual
servers. Backups usually fail with 'connection refused' errors. I can
login to the client and use the 'save' command to get successful backups
with no problems whatsoever. Our server is 7.2.2 and the client version
is also 7.2. A probe of the client from the server yields the following:
----------------------------------------------------------------
C:\Documents and Settings\user>savegrp -p -vv -c clientx testgroup
clientx:All level=full
06/05/07 15:38:09 savegrp: Run up to 12 clients in parallel
06/05/07 15:38:09 savegrp: clientx:probe
started
savefs -s buserver.xxx.com -c clientx -g testgroup -p -o VSS:*=off -l
full -R -v
06/05/07 15:41:36 savegrp: command 'savefs -s buserver.xxx.com -c
clientx -g testgroup -p -o VSS:*=off -l full -R -v ' for client clientx
exited with return code 1.
06/05/07 15:41:36 savegrp: clientx:probe succeeded.
* clientx:All rcmd clientx, user root: `savefs -s buserver.xxx.com -c
clientx -g testgroup -p -o VSS:*=off -l full -R -v'
* clientx:All 06/05/07 15:40:37 nsrexec: nsrexecd on clientx is
unavailable. Using rsh instead.
* clientx:All 06/05/07 15:41:15 nsrexec: connect to address 10.1.1.196:
(null): Connection refused
* clientx:All 06/05/07 15:41:15 nsrexec: Trying 10.1.1.197...
clientx.xxx.com: Connection timed out
* clientx:All Network connection could not be established with client
'clientx'
--- Probe Summary ---
clientx:All level=full, dn=-1, mx=0, vers=unknown,
p=1
clientx:All level=full, pool=poolx, save as of Tue Jun 05
3:41:36 GMT-0400 M 20
clientx:index level=full, dn=-1, mx=0, vers=unknown,
p=1
clientx:index level=full, pool=poolx, save as of Tue Jun 05
3:41:36 GMT-0400 M 20
-----------------------------------------------------
Any ideas as to what is causing these failure or where we can look for a
solution ???
Regards,
Paul Goslin
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 with 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
|
