Backup Central

This is unusual. I had to recreate my NMC installation recently. So I
created a new VM, installed NMC, all works well. During the installation
of NMC, it created a client and a saveset to save the DB (savepsm". Yet
when I go to change the group it's in (from "Default"), I get an error
that the client's name is not a valid host name, and I can't move it. So I
figured I would delete it, and re-create it. And I get the same error when
trying to re-create the client.

The client properly exist in DNS, both forward and reverse; I verified
that from both the VM and my NW server. I can ping it from the server, and
vice versa. The VM is in even the "servers" file of the server, and the NW
server is in the "servers" file of the VM.

So what could be causing this? I thought this error would be caused by
fault DNS, but a nslookup works properly on both machines, and I have full
connectivity, and no firewall issues (I know, because I created other
clients on the NMC running on this VM yesterday)


--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone < at > pha.phila.gov>


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Well, I was able to resolve it, in an equally odd way. I added my NW
server to another NMC I run (at one of my remote sites). I then created
the client from there. And *then* I was able to move it to the group I
wanted.

Strange, but if everything worked sanely and the way it was supposed to,
I'd probably be out of a job. LOL

--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone < at > pha.phila.gov>


EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU> wrote on
01/25/2012 12:27:20 PM:

From: Michael Leone <Michael.Leone < at > PHA.PHILA.GOV>
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Date: 01/25/2012 12:30 PM
Subject: [Networker] odd "Not a valid hotname" error
Sent by: EMC NetWorker discussion <NETWORKER < at > LISTSERV.TEMPLE.EDU>

This is unusual. I had to recreate my NMC installation recently. So I
created a new VM, installed NMC, all works well. During the installation

of NMC, it created a client and a saveset to save the DB (savepsm". Yet
when I go to change the group it's in (from "Default"), I get an error
that the client's name is not a valid host name, and I can't move it. So
I
figured I would delete it, and re-create it. And I get the same error
when
trying to re-create the client.

The client properly exist in DNS, both forward and reverse; I verified
that from both the VM and my NW server. I can ping it from the server,
and
vice versa. The VM is in even the "servers" file of the server, and the
NW
server is in the "servers" file of the VM.

So what could be causing this? I thought this error would be caused by
fault DNS, but a nslookup works properly on both machines, and I have
full
connectivity, and no firewall issues (I know, because I created other
clients on the NMC running on this VM yesterday)


--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone < at > pha.phila.gov>


and type "signoff networker" in the body of the email. Please write
to networker-request < at > listserv.temple.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


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER