Re: [Veritas-bu] question on client names
Resolving search lists doesn't mean they have to be configured correctly "everywhere". Just for the server and the client involved in the current problem. That is to say while it needs to be configured "everywhere" to make each client work when their turn comes in the schedule it is a red herring to suggest that you need to concern yourself with that "everywhere" when troubleshooting a specific issue. If there's been an "everywhere" change it will become apparent due to the fact that most of the clients will fail. That kind of global failure due to bad planning can occur regardless of which method you use. (e.g. What happens if all your FQDNs are suddently invalid due to a domain name change?) In a related point: If you use short names and search lists then you don't have to go edit all your policies with new domain names if they change (and on occasion they do especially in mergers/acquisitions). You just have to edit the resolv.conf on each of the servers and clients. That can be easily scripted (as in fact it was here recently when we swapped out decommissioned named servers for new ones). In the very few cases where I've thought difference between searched name and FQDN might be a problem I've addressed it by adding entry to master/media server hosts file and the specific client. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts Sent: Monday, March 16, 2009 3:07 PM To: Stafford, Geoff Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] question on client names On Mon, Mar 16, 2009 at 12:28 PM, Stafford, Geoff wrote: The need to use FQDNs is, imho, a sign that you don't trust your DNS. I trust the DNS - I have extensive DNS experience and our company would be down without a fully functioning DNS infrastructure. Ours works. FQDNs are a PITA if you ask me and I would rather take the time to make something as mission critical as DNS work right instead of hiding the real problem. FQDNs make it absolutely clear what's going on. Remember, you can't do a backup using a short form name anyway - internally, you're resolving to a fqdn whether you like it or not. You're not only relying on FQDNs, but you're also relying on the search lists configured properly everywhere. You can take all the short cuts you want, but not taking the short cuts saves you headaches later, as MANY people have found out. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] question on client names
On Mon, Mar 16, 2009 at 12:28 PM, Stafford, Geoff < gstaff...@barclaycardus.com> wrote: > The need to use FQDNs is, imho, a sign that you don’t trust your DNS. > I trust the DNS - I have extensive DNS experience and our company would be down without a fully functioning DNS infrastructure. Ours works. > FQDNs are a PITA if you ask me and I would rather take the time to make > something as mission critical as DNS work right instead of hiding the real > problem. > FQDNs make it absolutely clear what's going on. Remember, you can't do a backup using a short form name anyway - internally, you're resolving to a fqdn whether you like it or not. You're not only relying on FQDNs, but you're also relying on the search lists configured properly everywhere. You can take all the short cuts you want, but not taking the short cuts saves you headaches later, as MANY people have found out. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] question on client names
The problem is, if you have multiple sites, DNS is limited (at least in Linux/glibc) to 6 sub domains, after that, you're going to have problems. Better off with FQDN IMO. search Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it contains only the local domain name. This may be changed by listing the desired domain search path follow- ing the search keyword with spaces or tabs separating the names. Resolver queries having fewer than ndots dots (default is 1) in them will be attempted using each component of the search path in turn until a match is found. For environments with multiple subdomains please read options ndots:n below to avoid man-in- the-middle attacks and unnecessary traffic for the root-dns- servers. Note that this process may be slow and will generate a lot of network traffic if the servers for the listed domains are not local, and that queries will time out if no server is avail- able for one of the domains. The search list is currently limited to six domains with a total of 256 characters. Justin. On Mon, 16 Mar 2009, Stafford, Geoff wrote: > The need to use FQDNs is, imho, a sign that you don't trust your DNS. > FQDNs are a PITA if you ask me and I would rather take the time to make > something as mission critical as DNS work right instead of hiding the > real problem. To each his own, I've been on contracts before where the > problem was systemic and that was the only way to get backups working > without significant changes in procedures across the company but if your > admins and network guys are doing their job you shouldn't have to. > > > > I guess my comment is just that 'you shouldn't have to use FQDN's' and > if you don't have to I wouldn't. To each his own. > > > > > > > > Date: Sun, 15 Mar 2009 13:48:49 -0500 > > From: Ed Wilts > > Subject: Re: [Veritas-bu] question on client names > > To: judy_hinchcli...@administaff.com > > Cc: VERITAS-BU@mailman.eng.auburn.edu > > Message-ID: > > <995e39b60903151148taacbbadv84f17f6c60a84...@mail.gmail.com> > > Content-Type: text/plain; charset="iso-8859-1" > > > > On Fri, Mar 13, 2009 at 2:06 PM, > wrote: > > > >> > >> > >> So I was just wondering. When you add servers to netbackup do you use > > >> short name or FQDN. > >> > > > > Always, always use FQDNs. Short names are simply evil. > > > > .../Ed > > > > Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE > > ewi...@ewilts.org > > -- next part -- > > An HTML attachment was scrubbed... > > URL: > http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20090315/ > cd9e3a4b/attachment-0001.html > > > > > > Barclays www.barclaycardus.com > > This e-mail and any files transmitted with it may contain confidential and/or > proprietary information. It is intended solely for the use of the individual > or entity who is the intended recipient. Unauthorized use of this information > is prohibited. If you have received this in error, please contact the sender > by replying to this message and delete this material from any system it may > be on. > > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] question on client names
I have been of the same opinion. But with the new domains, I cannot install across the domains, so I have to do some special stuff to get the netbackup files up on the domain to upgrade those servers. This is where I am having the issue, so when I do the upgrade I need to be able to say these 4 servers are on a different domain and know that I have to do special steps. From: Stafford, Geoff [mailto:gstaff...@barclaycardus.com] Sent: Monday, March 16, 2009 12:28 PM To: Judy Hinchcliffe; ewi...@ewilts.org Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] question on client names The need to use FQDNs is, imho, a sign that you don't trust your DNS. FQDNs are a PITA if you ask me and I would rather take the time to make something as mission critical as DNS work right instead of hiding the real problem. To each his own, I've been on contracts before where the problem was systemic and that was the only way to get backups working without significant changes in procedures across the company but if your admins and network guys are doing their job you shouldn't have to. I guess my comment is just that 'you shouldn't have to use FQDN's' and if you don't have to I wouldn't. To each his own. Date: Sun, 15 Mar 2009 13:48:49 -0500 From: Ed Wilts Subject: Re: [Veritas-bu] question on client names To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@mailman.eng.auburn.edu Message-ID: <995e39b60903151148taacbbadv84f17f6c60a84...@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" On Fri, Mar 13, 2009 at 2:06 PM, wrote: > > > So I was just wondering. When you add servers to netbackup do you use > short name or FQDN. > Always, always use FQDNs. Short names are simply evil. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org -- next part -- An HTML attachment was scrubbed... URL: http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20090315/ cd9e3a4b/attachment-0001.html ___ Barclays www.barclaycardus.com ___ This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] question on client names
We have only used short names for all our backups. Geoff's comments are
right on.. Our DNS works fine. The main thing is to be
sure that forward and reverse look-ups work. Netbackup is very fussy
about that.
--
Carl Stehman
Distributed Services
Pepcoholdings, Inc.
701 Ninth St NW
Washington DC 20068
202-331-6619
"Stafford, Geoff"
Sent by: veritas-bu-boun...@mailman.eng.auburn.edu
03/16/2009 01:45 PM
To
judy_hinchcli...@administaff.com, ewi...@ewilts.org
cc
VERITAS-BU@mailman.eng.auburn.edu
Subject
Re: [Veritas-bu] question on client names
The need to use FQDNs is, imho, a sign that you don?t trust your DNS.
FQDNs are a PITA if you ask me and I would rather take the time to make
something as mission critical as DNS work right instead of hiding the real
problem. To each his own, I?ve been on contracts before where the problem
was systemic and that was the only way to get backups working without
significant changes in procedures across the company but if your admins
and network guys are doing their job you shouldn?t have to.
I guess my comment is just that ?you shouldn?t have to use FQDN?s? and if
you don?t have to I wouldn?t. To each his own.
Date: Sun, 15 Mar 2009 13:48:49 -0500
From: Ed Wilts
Subject: Re: [Veritas-bu] question on client names
To: judy_hinchcli...@administaff.com
Cc: VERITAS-BU@mailman.eng.auburn.edu
Message-ID:
<995e39b60903151148taacbbadv84f17f6c60a84...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
On Fri, Mar 13, 2009 at 2:06 PM, wrote:
>
>
> So I was just wondering. When you add servers to netbackup do you use
> short name or FQDN.
>
Always, always use FQDNs. Short names are simply evil.
.../Ed
Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
ewi...@ewilts.org
-- next part --
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20090315/cd9e3a4b/attachment-0001.html
___
Barclays
www.barclaycardus.com
___
This e-mail and any files transmitted with it may contain confidential
and/or proprietary information. It is intended solely for the use of the
individual or entity who is the intended recipient. Unauthorized use of
this information is prohibited. If you have received this in error, please
contact the sender by replying to this message and delete this material
from any system it may be on.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is
intended solely for the use of the person(s) to which it is addressed. If
you are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby notified
that any dissemination, distribution or copying of this Email is strictly
prohibited. If you have received this message in error, please immediately
notify the sender and permanently delete this Email and any copies. PHI
policies expressly prohibit employees from making defamatory or offensive
statements and infringing any copyright or any other legal right by Email
communication. PHI will not accept any liability in respect of such
communications.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] question on client names
The need to use FQDNs is, imho, a sign that you don't trust your DNS. FQDNs are a PITA if you ask me and I would rather take the time to make something as mission critical as DNS work right instead of hiding the real problem. To each his own, I've been on contracts before where the problem was systemic and that was the only way to get backups working without significant changes in procedures across the company but if your admins and network guys are doing their job you shouldn't have to. I guess my comment is just that 'you shouldn't have to use FQDN's' and if you don't have to I wouldn't. To each his own. Date: Sun, 15 Mar 2009 13:48:49 -0500 From: Ed Wilts Subject: Re: [Veritas-bu] question on client names To: judy_hinchcli...@administaff.com Cc: VERITAS-BU@mailman.eng.auburn.edu Message-ID: <995e39b60903151148taacbbadv84f17f6c60a84...@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" On Fri, Mar 13, 2009 at 2:06 PM, wrote: > > > So I was just wondering. When you add servers to netbackup do you use > short name or FQDN. > Always, always use FQDNs. Short names are simply evil. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org -- next part -- An HTML attachment was scrubbed... URL: http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20090315/ cd9e3a4b/attachment-0001.html Barclays www.barclaycardus.com This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] question on client names
On Fri, Mar 13, 2009 at 2:06 PM, wrote: > > > So I was just wondering. When you add servers to netbackup do you use > short name or FQDN. > Always, always use FQDNs. Short names are simply evil. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] question on client names
We use short names. Also we actually have a separate VLAN for backups so for most hosts we put in a b short name in the master's host file. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of judy_hinchcli...@administaff.com Sent: Friday, March 13, 2009 3:06 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] question on client names At the start we added client names to netbackup as just the short name Now they have been added different domains so now I got server that are a little scattered When I go to do updates I have to do each domain as a group. Not knowing what domain a server is in have to do some commands and make a list. So I was just wondering. When you add servers to netbackup do you use short name or FQDN. If short how do you handle installs on the different domains? Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
