Dan, name resolution needs to be working on both ends, server
and client. When backup job starts, server connects to the client
and tehn client connects to the server. 
I bet your problem is that mmora1 is not able to resolve name mmora3.

HTH, -Kastus

On Mon, Jul 22, 2002 at 02:06:15PM -0700, Dan Dobbs wrote:
>  Greetings, list.
> 
> Over the weekend, our internal DNS server went down. One of our servers
> didn't get backed up, and I can only guess that it's because the Backup
> Server couldn't resolve the name. 
> 
> Our backup server is MMORA3, and our client is mmora1. 
> 
> Here's the error log:
> 
> Error Log Report for Client mmora1
> 
> 
>  54    mmora1        Unix_Servers     Unix_Serve MMORA3      07/21/2002
> 09:21:45 
>                  (timed out connecting to client)
>  54    mmora1        Unix_Servers     Unix_Serve MMORA3      07/21/2002
> 09:21:46 
>                  (timed out connecting to client)
>  54    mmora1        Unix_Servers     Unix_Serve MMORA3      07/21/2002
> 09:21:47 
>                  (timed out connecting to client)
> <snip>
> _______________________________________________________________________________
>     TIME            SERVER/CLIENT                      TEXT
> 07/21/2002 09:21:44 MMORA3 mmora1  timed out trying to connect to
> mmora1
> 07/21/2002 09:21:45 MMORA3 mmora1  timed out trying to connect to
> mmora1
> 07/21/2002 09:21:45 MMORA3 mmora1  backup of client mmora1 exited with
> status 54
>                     (timed out connecting to client)
> 07/21/2002 09:21:46 MMORA3 mmora1  timed out trying to connect to
> mmora1
> 07/21/2002 09:21:46 MMORA3 mmora1  backup of client mmora1 exited with
> status 54
>                     (timed out connecting to client)
> 07/21/2002 09:21:47 MMORA3 mmora1  timed out trying to connect to
> mmora1
> 07/21/2002 09:21:47 MMORA3 mmora1  backup of client mmora1 exited with
> status 54
>                     (timed out connecting to client)
> 07/21/2002 09:21:49 MMORA3 mmora1  backup of client mmora1 exited with
> status 54
>                     (timed out connecting to client)
> 07/21/2002 09:21:49 MMORA3 mmora1  timed out trying to connect to
> mmora1
> 07/21/2002 09:21:49 MMORA3 mmora1  timed out trying to connect to
> mmora1
> 07/21/2002 09:21:50 MMORA3 mmora1  timed out trying to connect to
> mmora1
> <snip>
> 
> 
> Here's our /etc/hosts file:
> 
> # more /etc/hosts
> #
> # The form for each entry is:
> # <internet address>    <official hostname> <aliases>
> #
> # For example:
> # 192.1.2.34    hpfcrm  loghost
> #
> # See the hosts(4) manual page for more information.
> # Note: The entries cannot be preceded by a space.
> #       The format described in this file is the correct format.
> #       The original Berkeley manual page contains an error in
> #       the format description.
> #
> 10.1.1.22 yoda          yoda.mutualmaterials.com        yoda
> 10.1.1.24 obiwan        obiwan.mutualmaterials.com      obiwan
> 10.1.1.18 mmora1        mmora1.mutualmaterials.com      MMORA1
> 
> Here's an nslookup:
> 
> # nslookup mmora1
> Using /etc/hosts on:  MMORA3
> 
> looking up FILES
> Name:    mmora1
> Address:  10.1.1.18
> Aliases:  mmora1.mutualmaterials.com, MMORA1
> 
> I guess what my question is would be why it didn't back up? It would
> appear that MMORA3 can resolve the name to its /etc/hosts file. What
> else could cause an error 54? And, shouldn't NetBackup be able to use
> the /etc/hosts file to back stuff up in absence of the DNS server
> anyway?
> 
> Thanks!
> 
> -dd
> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-- 
Konstantin 'Kastus' Shchuka
Unix System Administrator
ePocrates Inc.
tel 650.232.4886
fax 650.592.6995