Networker

Re: [Networker] Problems with Modules for Microsoft Applications

2010-06-10 07:08:11
Subject: Re: [Networker] Problems with Modules for Microsoft Applications
From: Eric Fabulus <efabulus AT HOTMAIL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 10 Jun 2010 13:05:16 +0200
Resolve fqdn is not enough for networker. Problem is often reverse lookup
zone. Try to put both ips (server and client) in hosts files and add the ip
as aliases in the client properties

Kind regards

-----Message d'origine-----
De : EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] De 
la
part de Daniel Matei
Envoyé : jeudi 10 juin 2010 12:00
À : NETWORKER AT LISTSERV.TEMPLE DOT EDU
Objet : [Networker] Problems with Modules for Microsoft Applications

                               Hello,

                I am currently trying to test a new backup solution
(NetWorker) in our firm. We currently have ArcServe and we want to change to
NetWorker.
                I had created a test environment with mostly all the things
we use in production (Different versions of  Windows Servers, SharePoint,
MSSQL and Exchange). The problem is that, all though I had installed
NetWorker 7.6 build 142 and I can backup systems using the backup client
supplied with the NetWorkder setup I cannot use the Modules for Microsoft
Applications on the servers that use applications (MSSQL for instance but
not only that).
So I decided to install the NMM  on an freshly Windows 2003 R2 SP2 and see
if it works without the other applications (MSSQL/Exchange) but I couldn't
make it work. What happens is this: I install the agent on the target
machine (which is version 2.2.1 Build: 95). I am typing in the FQDN name of
the networker server (it does resolve correctly) and I finnish the install.
Then I switch to the NetWorker Administration console and I am looking in
the Configuration under "Local Hosts" under the networker server name. There
I can see the name of the newly added client (and also the older ones
installed with normal agent and not NMM). So I go to the "Clients" under the
configurations and try to add the client there under the Client Backup
Configuration menu. I type in the FQDN name (I'm making sure that the
NetWorker server can resolve the name and click next. Here it says to
Specify the Backup Configuration Type (and it tells me that the client
operating system is "Windows NT Server on Intel" and that the NetWorker
version is: rb_nmm22_sp1 Build 95 and that the available applications is
only the filesystem (which is correct because it's a fresly install of
windows but the same happend on the one that had MSSQL in it.) All I can do
here is click Next and it should take me to the "Select the Client
Properties". But it doesn't happen because I get an (not so detailed) error
that states  "Unable to connect to server" and the wizard exits.
I get no logs in Event Viewer.
Again: Both client and server can resolve eachother's ip from FQDN.
                Any ideas?

                Hope you've understood something from my not so good english
and also from my a bit randomly explanation.

                PS: NetWorker server is installed in windows.


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

<Prev in Thread] Current Thread [Next in Thread>