We use DNS for everything.  If you want a new server
to work correctly, then the production side needs to
be in DNS- just make the backup DNS part of the
process for whoever does the production net.

As for Auto vs Hardcoded- we have issues on 100Mb
going to half-duplex when those clients when they are
set to Auto, so those have to be hard-coded.  For Gig
clients, Auto works fine.  People like to have one
rule though- so we tell them "hard-code" just to make
sure it always works.
But again- this process is the same for both
production and backup networks, so it makes it much
easier for the sysadmins to keep straight.  

Tom
--- "Adams, Dwayne" <AdamsDC at medsch.ucsf.edu> wrote:

> Hello,
> 
>  
> 
> I have managed a few backup environments and always
> put the backup
> servers in the hosts file of the clients and the
> clients in the backup
> server's hosts file.  I always like to control name
> resolution myself.
> Do most backup administrator do that or am I a relic
> from the past?
> Also, do most backup admins use AUTO negotiate or
> set the switch port
> and the host to FULL DUPLEX? My practices are being
> questioned and I
> would like to check to see if what I am doing is in
> line with what most
> backup admins are doing.
> 
>  
> 
>  
> 
> Thanks in advance,
> 
>  
> 
> Dwayne Adams
> 
> > _______________________________________________
> Veritas-bu maillist  - 
> Veritas-bu at mailman.eng.auburn.edu
>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 



       
____________________________________________________________________________________
We won't tell. Get more on shows you hate to love 
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265