Backup Central

Hello all

Experiencing strange behaviour on one Windows 2008 client.

NWserver/client version 7.6.2

If the client is restarted the backups start to fail with "client is not properly configured on the NetWorker Server"

We then have to delte the client in NMC and recreate it.
The backups then run fine untill the next time the client is rebooted, when the error reappears.

Notes:
Ping works both ways
Nslookup works both ways with short name and FQDN
Rpcinfo -p works both ways
Client is configured with FQDN


Thanks you
Regards
Eivind



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

Wow!

That sounds remarkably like a problem I have been chasing with EMC for a year now.

If it is the same problem, you will find that if you just go into NMC and remove the aliases for the client (let NMC repopulate them), the client will remarkably start working again.

Though, in my case, I have 4-6 clients that I have to do this for every time I restart the NetWorker server (and have had ever since I upgraded a year ago to 7.5.4.3) - It has persisted against all the best EMC support people who are completely baffled about what is corrupted deep down in the recesses someplace. I am currently running 7.6.2.5 on the server and the clients and it still persists for this same set of clients every time I restart the server.

Frank

Sent from a medium size mobile device

On Oct 26, 2011, at 8:04, Eivind Antonsen <ean < at > EXELLO.NO> wrote:

Hello all

Experiencing strange behaviour on one Windows 2008 client.

NWserver/client version 7.6.2

If the client is restarted the backups start to fail with "client is not properly configured on the NetWorker Server"

We then have to delte the client in NMC and recreate it.
The backups then run fine untill the next time the client is rebooted, when the error reappears.


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

I see this problem whenever another CNAME is added to a client's DNS entry after the client resource is added to NetWorker. An easy way to deal with that problem is to simply add the new alias name onto the aliases list of the relevant client entry. Deleting and creating the client entry solves the problem because it then picks up the additional CNAME alias from DNS, but it is overkill in my opinion.

On 10 26, 2011, at 8:04 AM, Eivind Antonsen wrote:

Hello all

Experiencing strange behaviour on one Windows 2008 client.

NWserver/client version 7.6.2

If the client is restarted the backups start to fail with "client is not properly configured on the NetWorker Server"

We then have to delte the client in NMC and recreate it.
The backups then run fine untill the next time the client is rebooted, when the error reappears.

Notes:
Ping works both ways
Nslookup works both ways with short name and FQDN
Rpcinfo -p works both ways
Client is configured with FQDN


Thanks you
Regards
Eivind



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

In regard to: Re: [Networker] client is not properly configured on the...:

Though, in my case, I have 4-6 clients that I have to do this for every
time I restart the NetWorker server (and have had ever since I upgraded
a year ago to 7.5.4.3) - It has persisted against all the best EMC
support people who are completely baffled about what is corrupted deep
down in the recesses someplace. I am currently running 7.6.2.5 on the
server and the clients and it still persists for this same set of
clients every time I restart the server.

By any chance, have you tried removing the nsrladb on one of the
*clients*? The information should be regenerated, though you may need to
delete the peer information for that particular client on the server.

Tim
--
Tim Mooney Tim.Mooney < at > ndsu.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


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

On 10/26/11 2:18 PM, Tim Mooney wrote:
In regard to: Re: [Networker] client is not properly configured on the...:

Though, in my case, I have 4-6 clients that I have to do this for every
time I restart the NetWorker server (and have had ever since I upgraded
a year ago to 7.5.4.3) - It has persisted against all the best EMC
support people who are completely baffled about what is corrupted deep
down in the recesses someplace. I am currently running 7.6.2.5 on the
server and the clients and it still persists for this same set of
clients every time I restart the server.

By any chance, have you tried removing the nsrladb on one of the
*clients*? The information should be regenerated, though you may need to
delete the peer information for that particular client on the server.



Yes, we've removed the entire /nsr/res directory on the client, deleted the client index and
client definition on the server and two restarts later the problem is back. The only way we
have found so far to completely get rid of this problem is to delete everything on the server
(/nsr/res, /nsr/mm, and /nsr/index) and start over. We are convinced at this point that there
is something wrong deep inside the server someplace.

However, we also believe (at least I think we do) that this is most likely a very unlikely set
of circumstances unique to our installation, given that we've been using NetWorker since 1994
and have migrated the /nsr directory from AIX, to Solaris, to Linux in that time frame - ie, a
lot of conversions - I have no idea what version of NW we started with in 1994, but I do know
this problem appeared in the middle of 7.5 (an upgrade from one cum fix level to another is
when it came to light in November 2010).

I absolutely do not intend this to be a complaint - EMC has worked diligently trying to figure
this out with me.

Frank


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

onsdag 26 oktober 2011 15:04:23 skrev du:
Hello all

Experiencing strange behaviour on one Windows 2008 client.

NWserver/client version 7.6.2

If the client is restarted the backups start to fail with "client is not
properly configured on the NetWorker Server"

You didn't give us the full story...

NW will say client xxxx is not properly configured. Pay attention to the xxxx
part...

Best
Dag


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