Backup Central

I've set up a couple of Windows dedicated storage nodes off my Linux
Networker server that will share drives. Everything seems to be set up,
except I get endless messages of the format:

Jan 4 12:01:18 cranes logger: NetWorker media: (notice) check storage
node: node1.foo.com (Host name verification failed - unknown host: W.X.Y.Z)
Jan 4 12:01:18 cranes logger: NetWorker media: (info) restarting nsrmmd
#2 on node1.foo.com in 2 minute(s)

The W.X.Y.Z is the IP address of the Networker server. Both sides seem
to be able to resolve names and addresses fine, and I can find no
reference to this error. Is anyone familiar with it?

-Brian

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Hi,

If you use DNS server, please try to insert IP/name for storage node,
backup server a client to hosts file.
/etc/hosts
/windows/system32/drivers/etc/hosts

Petr

Also, verify alias on all servers /client/edit/preference/alliases

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Oh, yes. I've run into this quite a bit in backups of windows clients.
Networker can't recognize a client unless the hostname and ip address match
exactly in both a forward and reverse lookup. If your machine uses dns to
do lookups (in nsswitch.conf), use nslookup to check the ip and host. do
the ip more than once since it might round-robin thru a few options.
basically if you nslookup W.X.Y.Z and don't get back "node1.foo.com" then
it's failed to resolve.

Because we have dhcp and dns integrated in our environment and it seems to
be impossible to get it to keep the reverses clean in dns, I gave up and
switched my networker server to only look at /etc/hosts for lookups. That
solved the problem.



-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU] On
Behalf Of Brian O'Neill
Sent: Tuesday, January 04, 2005 11:09 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: Storage nodes: "Host name verification failed"

I've set up a couple of Windows dedicated storage nodes off my Linux
Networker server that will share drives. Everything seems to be set up,
except I get endless messages of the format:

Jan 4 12:01:18 cranes logger: NetWorker media: (notice) check storage
node: node1.foo.com (Host name verification failed - unknown host: W.X.Y.Z)
Jan 4 12:01:18 cranes logger: NetWorker media: (info) restarting nsrmmd
#2 on node1.foo.com in 2 minute(s)

The W.X.Y.Z is the IP address of the Networker server. Both sides seem
to be able to resolve names and addresses fine, and I can find no
reference to this error. Is anyone familiar with it?

-Brian

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu


This communication may contain privileged and/or confidential
information. It is intended solely for the use of the addressee. If you are
not the intended recipient, you are strictly prohibited from disclosing,
copying, distributing or using any of this information. If you received this
communication in error, please contact the sender immediately and destroy
the material in its entirety, whether electronic or hard copy. Confidential,
proprietary or time-sensitive communications should not be transmitted via
the Internet, as there can be no assurance of actual or timely delivery,
receipt and/or confidentiality. This is not an offer, or solicitation of any
offer to buy or sell any security, investment or other product.

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Forward/reverse lookups seem fine - I had checked that first. I don't
have access to the windows nodes so I can't verify that end, but the did
state that the server does resolve properly from that end.

Actually one line I left out from the logs:

Tue 17:34:03 rd=node2.foo.com:\\.\Tape0 enabled; nsrmmd not available

Not sure if that makes a difference. I've tried restarting the server,
and I've made sure "user=Administrators,host=node1.foo.com", etc. is in
the administrators list.

Dell, Mary wrote:

Oh, yes. I've run into this quite a bit in backups of windows clients.
Networker can't recognize a client unless the hostname and ip address
match exactly in both a forward and reverse lookup. If your machine
uses dns to do lookups (in nsswitch.conf), use nslookup to check the ip
and host. do the ip more than once since it might round-robin thru a
few options. basically if you nslookup W.X.Y.Z and don't get back
"node1.foo.com" then it's failed to resolve.

Because we have dhcp and dns integrated in our environment and it seems
to be impossible to get it to keep the reverses clean in dns, I gave up
and switched my networker server to only look at /etc/hosts for
lookups. That solved the problem.



-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Tuesday, January 04, 2005 11:09 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: Storage nodes: "Host name verification failed"

I've set up a couple of Windows dedicated storage nodes off my Linux
Networker server that will share drives. Everything seems to be set up,
except I get endless messages of the format:

Jan 4 12:01:18 cranes logger: NetWorker media: (notice) check storage
node: node1.foo.com (Host name verification failed - unknown host: W.X.Y.Z)
Jan 4 12:01:18 cranes logger: NetWorker media: (info) restarting nsrmmd
#2 on node1.foo.com in 2 minute(s)

The W.X.Y.Z is the IP address of the Networker server. Both sides seem
to be able to resolve names and addresses fine, and I can find no
reference to this error. Is anyone familiar with it?

-Brian

--
Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu


/ This communication may contain privileged and/or confidential
information. It is intended solely for the use of the addressee. If you
are not the intended recipient, you are strictly prohibited from
disclosing, copying, distributing or using any of this information. If
you received this communication in error, please contact the sender
immediately and destroy the material in its entirety, whether electronic
or hard copy. Confidential, proprietary or time-sensitive communications
should not be transmitted via the Internet, as there can be no assurance
of actual or timely delivery, receipt and/or confidentiality. This is
not an offer, or solicitation of any offer to buy or sell any security,
investment or other product./


Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Problems solved, at least this one. They decided to inform me today that
they are doing split-brain DNS between their AD systems and everything
else - so the server wasn't known by the name I knew it as. Once they
updated both sides to use the name name, and I reconfigured Networker,
everything started working in that regard.

I have other config questions, but will pose them separately...

Brian O'Neill wrote:
Forward/reverse lookups seem fine - I had checked that first. I don't
have access to the windows nodes so I can't verify that end, but the did
state that the server does resolve properly from that end.

Actually one line I left out from the logs:

Tue 17:34:03 rd=node2.foo.com:\\.\Tape0 enabled; nsrmmd not available

Not sure if that makes a difference. I've tried restarting the server,
and I've made sure "user=Administrators,host=node1.foo.com", etc. is in
the administrators list.

Dell, Mary wrote:


Oh, yes. I've run into this quite a bit in backups of windows clients.
Networker can't recognize a client unless the hostname and ip address
match exactly in both a forward and reverse lookup. If your machine
uses dns to do lookups (in nsswitch.conf), use nslookup to check the ip
and host. do the ip more than once since it might round-robin thru a
few options. basically if you nslookup W.X.Y.Z and don't get back
"node1.foo.com" then it's failed to resolve.

Because we have dhcp and dns integrated in our environment and it seems
to be impossible to get it to keep the reverses clean in dns, I gave up
and switched my networker server to only look at /etc/hosts for
lookups. That solved the problem.



-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU]
On Behalf Of Brian O'Neill
Sent: Tuesday, January 04, 2005 11:09 AM
To: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Subject: Storage nodes: "Host name verification failed"

I've set up a couple of Windows dedicated storage nodes off my Linux
Networker server that will share drives. Everything seems to be set up,
except I get endless messages of the format:

Jan 4 12:01:18 cranes logger: NetWorker media: (notice) check storage
node: node1.foo.com (Host name verification failed - unknown host:
W.X.Y.Z)
Jan 4 12:01:18 cranes logger: NetWorker media: (info) restarting nsrmmd
#2 on node1.foo.com in 2 minute(s)

The W.X.Y.Z is the IP address of the Networker server. Both sides seem
to be able to resolve names and addresses fine, and I can find no
reference to this error. Is anyone familiar with it?

-Brian

--
Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu


/ This communication may contain privileged and/or confidential
information. It is intended solely for the use of the addressee. If you
are not the intended recipient, you are strictly prohibited from
disclosing, copying, distributing or using any of this information. If
you received this communication in error, please contact the sender
immediately and destroy the material in its entirety, whether electronic
or hard copy. Confidential, proprietary or time-sensitive communications
should not be transmitted via the Internet, as there can be no assurance
of actual or timely delivery, receipt and/or confidentiality. This is
not an offer, or solicitation of any offer to buy or sell any security,
investment or other product./


--
Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu

Note: To sign off this list, send a "signoff networker" command via email
should be sent to stan < at > temple.edu