Networker

Re: [Networker] Integration between Data Domain and NetWorker

2011-05-04 17:42:31
Subject: Re: [Networker] Integration between Data Domain and NetWorker
From: Mark Leese <mark.r.leese AT GMAIL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 4 May 2011 22:40:39 +0100
I have had a similar issue.. on the NMC server I had to alias all of the
private interfaces to the public address. At the moment though I am still
having trouble getting the Enhanced Cloning to work between DD's. We have a
backup server and 3 storage node solution. backup server and storage node
connected to a local DD with 2 storage nodes and DD remote. Each backing up
data locally. Only Problem is cloning will only work when the devices are
configured over the public address.. totally negates the private 10Gbe
interfaces.

On 4 May 2011 21:12, Dalvenjah FoxFire <dalvenjah AT dal DOT net> wrote:

> I was wondering about this. It's a bit kludgey, but it sounds like you need
> to add a hosts file entry to your NMC server:
>
> public.ip.of.DDsystem   ddinternal1 
> ddpublichostname.example.comddpublichostname
>
> That should get the NMC to be able to reach the data domain, and satisfy
> the Networker DNS requirements, too.
>
> You might need to restart the GST service on the NMC server to get it to
> use the new hosts file entry.
>
> -dalvenjah
>
> On May 4, 2011, at 11:54 AM, STANLEY R. HORWITZ wrote:
>
> > I am wondering if this issue is the result of the pair of IP addresses
> > between my NetWorker server and DD system being non-routable. If so, is
> > there a way around that without making them routable, or do I just have
> to
> > live with this issue?
> >
> > On 5/4/2011 12:58 PM, "Eric Fabulus" <efabulus AT HOTMAIL DOT COM> wrote:
> >
> >> Hi,
> >> I just want to remember you that as far as EMC Networker is concerned,
> >> PING IS NOT ENOUGH.
> >> This is not because you can ping one each other that Networker will
> think
> >> that the link is correct. Networker need a reverse lookup zone or
> >> something doing the same job. I would think this is network related and
> >> perhaps ask to a network administrator to check dns, firewalls and so
> on.
> >> Kind regards
> >> Eric
> >>
> >>> Date: Wed, 4 May 2011 12:47:29 -0400
> >>> From: stan AT TEMPLE DOT EDU
> >>> Subject: Re: [Networker] Integration between Data Domain and NetWorker
> >>> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> >>>
> >>> Skip,
> >>>
> >>> How do I check that the community string is correct in NMC? SNMP is
> >>> definitely enabled on the DD system.
> >>>
> >>> On 5/4/2011 12:36 PM, "Skip Hanson" <skip.hanson AT EMC DOT COM> wrote:
> >>>
> >>>> Hello. I would make sure the SNMP Community string for the DD system
> is
> >>>> correct in NMC. You can rsh into the DD system to get the list of
> >>> Public
> >>>> community strings. Also make sure SNMP is enabled for the DD system.
> >>>>
> >>>> Cheers,
> >>>> Skip
> >>>>
> >>>> On 5/4/11 8:51 AM, "STANLEY R. HORWITZ" <stan AT TEMPLE DOT EDU> wrote:
> >>>>
> >>>>> I am in the process of testing a brand new NetWorker data zone with a
> >>> new
> >>>>> Data Domain 860, DD Boost, a new Dell server running 64-bit Red Hat
> >>> Linux
> >>>>> and 64-bit NetWorker 7.6 SP2 RA, and two new Spectralogic T50e tape
> >>>>> libraries with LTO-5 tape drives in them.
> >>>>>
> >>>>> One little glitch I am encountering is that in the NetWorker
> >>> Management
> >>>>> Console (which runs on its own server), every time I click on the DD
> >>>>> device resource entry, I get a pop-up window that says:
> >>>>>
> >>>>> "Error gathering SNMP event and usage information for 'ddinternal1'.
> >>>>> Make sure SNMP is enabled on the system and the system is reachable."
> >>>>>
> >>>>> Note that "ddinternal1" is the short name for the network link
> (10GigE
> >>>>> Fiber) between the new NetWorker server and the DD 860. I can ping
> >>> this
> >>>>> name from the server and backups to it work fine. People from EMC are
> >>>>> looking into this situation, but thus far, the problem continues. I
> am
> >>>>> wondering if anyone on this mailing list has encountered this problem
> >>> and
> >>>>> if so, how did you fix it?
> >>>>>
> >>>>> To sign off this list, send email to [email protected]
> >>>>> 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
> >>>
> >>> 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
> >
> > 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
>

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