[Veritas-bu] Client Hostnames
2006-09-27 15:40:33
Subject: |
[Veritas-bu] Client Hostnames |
From: |
dcarlisle at paychex.com (Carlisle, D Renee) |
Date: |
Wed, 27 Sep 2006 15:40:33 -0400 |
We do the same thing. Each server, including the master and media servers have
two nics, each with their own name in dns. One caveat, especially with user
directed or database backups, have REQUIRED_INTERFACE set on your clients and
set it to the name of the nic on your backup network. If you don't, the
clients may send information out on the public interface and the media server
will respond on whichever network it received the request. I would also make
sure your nic cards are configured to use a set speed with full duplex enabled.
You could run into performance issues if you use auto-negotiate. We have
always been told the FQDN are best practice, and that is what we use.
Rene? Carlisle
Jer 29:11-13
________________________________
From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces
at mailman.eng.auburn.edu] On Behalf Of Hindle, Greg
Sent: Wednesday, September 27, 2006 3:02 PM
To: Hillman, Eric; veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Client Hostnames
We use fully QDN's here. We add 2 nics to each client one with its public name
and the other with a private name with NBU at the end. This NBU interface is
configured in the same vlan as our netbackup servers. Both names are in DNS.
Greg
________________________________
From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces
at mailman.eng.auburn.edu] On Behalf Of Hillman, Eric
Sent: Wednesday, September 27, 2006 2:38 PM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] Client Hostnames
We have public and backup networks. All clients have a public network which is
typically 100Mb and some clients (larger clients) have a backup network which
is typically GbE. This seems to be pretty typical in larger organizations.
Given the above scenarios, my question is... in Netbackup what do you name your
clients with backup nic's?
Option #1: Add a dns entry of the client name with a "-backup" suffix and
assign it's backup ip. Do the same with the Master/Media server and add their
-backup hostnames as additional servers from within the netbackup client
software
Option #2: Instead of using dns, simply add the -backup hostname client alias
to the local hosts file on the Netbackup Master/Media servers and assign the
backup ip. Do the same with the Master/Media server and add their -backup
hostnames as additional servers from within the netbackup client software
Option #3: Simply override the actual client's hostname IP with it's backup ip
by adding it to the local hosts file on the Netbackup Master/Media server. Do
the same with the Master/Media server in the client's hosts file and leave the
non -backup hostnames as servers in the netbackup client software. This
alternate method would overwrite the DNS record of the actual client and
Master/Media hostnames with the hosts backup IP.
Also, is it best practice to use FQDN's, or no?
Thanks
-Eric
THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED,
CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader
of this message is not the intended recipient, you are hereby notified that any
dissemination, distribution, copying or use of this message and any attachment
is strictly prohibited. If you have received this message in error, please
notify us immediately by replying to the message and permanently delete it from
your computer and destroy any printout thereof.
>>> This e-mail and any attachments are confidential, may contain legal,
>>> professional or other privileged information, and are intended solely for
>>> the addressee. If you are not the intended recipient, do not use the
>>> information in this e-mail in any way, delete this e-mail and notify the
>>> sender. CEG-IP1
-----------------------------------------
The information contained in this message may be privileged,
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or any employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution, or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately
by replying to the message and deleting it from your computer.
Thank you. Paychex, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060927/dbbc9af8/attachment.html
|
|
|