Networker

Re: [Networker] Round Robin DNS issue

2010-10-14 19:06:50
Subject: Re: [Networker] Round Robin DNS issue
From: "Browning, David" <DBrown AT LSUHSC DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 14 Oct 2010 18:05:32 -0500
Man, that's what I love about this list - someone always knows the
answer.  

Simply adding the save command, with the -c clientname did it.  

Now, I just have to dig around the documentation and see WHY it worked. 

Thanks, Tim. 

David M. Browning Jr.
IT Project Coordinator Enterprise Backups and Help Desk 
 

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Tim Mooney
Sent: Thursday, October 14, 2010 5:37 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Round Robin DNS issue

In regard to: [Networker] Round Robin DNS issue, Browning, David said
(at...:

> I was wondering if anyone has run across this issue, and has a
solution
> to it.
>
> Our email group installed the BES server in a 2 server setup, where
DNS
> points to servers in an alternating fashion (round robin DNS, a
> recommendation from RIM).   Server1 and Server2 contain mostly the
same
> data, but are not identical, but point to the same name - XXXXXBES.
>
> In other words, when a device requests XXXXXBES, it points to either
> Server1 or Server2.   The problem comes in backing up both servers.
> When I try to backup Server1 or Server2, it comes back that "XXXXXBES"
> is not properly configured on the server.  In the past, we've simply
> given that alias to a server, but I've never given 1 alias to 2
> different servers.   And when I tested that configuration, it worked,
> but definitely causes problems with the index.

I don't think you've provided enough information about how things are
configured to be able to give you any definitive answers, but there's at
least one thing you can try.

First, how exactly are the clients defined in NetWorker?  Is XXXXXBES
a CNAME for some real name, and the clients are configured using the
real
fqdn for each server, with XXXBES as an alias for each?

One thing you might try is using

        Backup command:   save -c client1

for client #1, and

        Backup command:   save -c client2

for client #2, assuming that you actually have some way to distinguish
the clients.  "Backup command" is in the "Apps & Modules" area of the
GUI.
Note that whatever you use as an argument to "-c" needs to exactly match
whatever name you've given each client within NetWorker, which should
cause NetWorker to add the index entries to the correct index directory.

Tim
-- 
Tim Mooney
Tim.Mooney AT ndsu DOT edu
Enterprise Computing & Infrastructure                  701-231-1076
(Voice)
Room 242-J6, IACC Building                             701-231-8541
(Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER