We've already been there, done that.... It still fails.....
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Andrew Quintana
Sent: Tuesday, July 24, 2007 1:24 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Do Clients have to be in DNS to work ?
All clients have to be able to do a forward and reverse lookup of the
master server and necessary storage nodes and vice versa. This does not
mean you have to have them all in DNS, adding the entries to the
relevant host files would do it just as well.
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Goslin, Paul
Sent: Tuesday, July 24, 2007 1:10 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Do Clients have to be in DNS to work ?
I'm having a problem getting two new Windows clients to backup/probe
(probe results below). Is it a requirement that all Networker clients be
defined in DNS to some capacity ? These two clients are not in our DNS,
they are located in our DMZ and we are reaching them via their IP
addresses only. Our firewall rules for Networker clients allow
everything needed for backups to work with all DMZ clients, but those
are also in our DNS, unlike these two. Will we have to add these 2
clients to our DNS also to get them to even probe successfully ?
Regards
Paul
---------------------------------- Probe Results --------------
C:\Documents and Settings\user>savegrp -p -vv CorpGenTemp
07/24/07 12:22:20 savegrp: Diagnostic: Reverse DNS lookup failed for
host 192.16 8.1.172, address 192.168.1.172
192.168.1.172:All level=incr
192.168.1.170:All level=incr
07/24/07 12:22:20 savegrp: Run up to 12 clients in parallel
07/24/07 12:22:20 savegrp: 192.168.1.172:probe started
savefs -s backupserver.domain.com -c 192.168.1.172 -g CorpGenTemp -p -o
VSS:*= off -l full -R -v
07/24/07 12:22:20 savegrp: 192.168.1.170:probe started
savefs -s backupserver.domain.com -c 192.168.1.170 -g CorpGenTemp -p -o
VSS:*=off -l full -R -v
07/24/07 12:25:09 savegrp: command 'savefs -s backupserver.domain.com -c
192.168.1.170 -g CorpGenTemp -p -o VSS:*=off -l full -R -v ' for client
192.168.1.170 exited with return code 1.
07/24/07 12:25:09 savegrp: 192.168.1.170:probe succeeded.
* 192.168.1.170:All rcmd 192.168.1.170, user root: `savefs -s
backupserver.domain.com -c 192.168.1.170 -g CorpGenTemp -p -o VSS:*=off
-l full -R -v'
* 192.168.1.170:All 07/24/07 12:24:48 nsrexec: nsrexecd on 192.168.1.170
is unavailable. Using rsh instead.
192.168.1.170: No route to host
* 192.168.1.170:All 07/24/07 12:25:09 nsrexec: SYSTEM error: No route to
host
07/24/07 12:25:13 savegrp: command 'savefs -s backupserver.domain.com -c
192.168.1.172 -g CorpGenTemp -p -o VSS:*=off -l full -R -v ' for client
192.168.1.172
exited with return code 1.
07/24/07 12:25:13 savegrp: 192.168.1.172:probe succeeded.
* 192.168.1.172:All rcmd 192.168.1.172, user root: `savefs -s
backupserver.domain.com -c 192.168.1.172 -g CorpGenTemp -p -o VSS:*=off
-l full -R -v'
* 192.168.1.172:All 07/24/07 12:24:52 nsrexec: nsrexecd on 192.168.1.172
is unavailable. Using rsh instead.
* 192.168.1.172:All 07/24/07 12:22:24 nsrexec: Diagnostic: Reverse DNS
lookup failed for host 192.168.1.172, address 192.168.1.172
192.168.1.172: No route to host
* 192.168.1.172:All 07/24/07 12:25:13 nsrexec: SYSTEM error: No route to
host
--- Probe Summary ---
192.168.1.170:All level=full, dn=-1, mx=0,
vers=unknown, p=1
192.168.1.170:All level=full, pool=CorpGenOffsite, save as of Tue
Jul 24 1
2:25:13 GMT-0400 PM 2
192.168.1.170:index level=full, dn=-1, mx=0,
vers=unknown, p=1
192.168.1.170:index level=full, pool=CorpGenOffsite, save as of Tue
Jul 24 1
2:25:13 GMT-0400 PM 2
192.168.1.172:All level=full, dn=-1, mx=0,
vers=unknown, p=1
192.168.1.172:All level=full, pool=CorpGenOffsite, save as of Tue
Jul 24 1
2:25:13 GMT-0400 PM 2
192.168.1.172:index level=full, dn=-1, mx=0,
vers=unknown, p=1
192.168.1.172:index level=full, pool=CorpGenOffsite, save as of Tue
Jul 24 1
2:25:13 GMT-0400 PM 2
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
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
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
|