Networker

Re: [Networker] License question?

2009-10-28 12:13:24
Subject: Re: [Networker] License question?
From: George Sinclair <George.Sinclair AT NOAA DOT GOV>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 28 Oct 2009 12:08:05 -0400
Greggs, Dana wrote:
They only way to free up a license is to delete the client resource that is 
using that license. To verify run nsrlic -v pre and post deletion. This is a 
documented fact by EMC/Networker support. You can grant other hosts permissions 
for recovery right before you attempt to do the recovery. Just recreate the 
client. Recreating or for that matter creating a client does take up a license 
until you successfully back the client up. So if you recreate it but don't 
attempt to back it up it won't use a license.

OK, I ran that command, and, yes, I can see that now. There are a number of older clients that are still reported and are no longer being backed up, but they're also listed as NSR client resources and their index directories still exist, so that makes sense.

My problem is that when I recreate a client that no longer exists and for which there is no longer a DNS entry , I receive:

"Name client_name should be a valid host name"

I end up having to add a temporary entry to the /etc/hosts on the server to re-create it under NetWorker, and then I can remove the /etc/hosts entry but still keep the NSR client resource listed, and at that point, it's only being used to give other clients permission to recover its older data. Nice to know that that won't use up a license, though.

George


Thanks,

Dana

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of George Sinclair
Sent: Sunday, October 25, 2009 5:57 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: License question?

If you keep an NSR client resource listed, even though the client no longer exists, does this still use up a license?

The situation is that when we get rid of a machine, I like to still keep one NSR client resource listed for that host so that I can give permission (Remote access field) to some other machine to recover the former host's data if need be. I keep it around for a while. If I don't do this, it's a little tricky to add it when it's no longer on the network other than playing games with /etc/hosts, etc.



--
George Sinclair
Voice: (301) 713-3284 x210
- The preceding message is personal and does not reflect any official or unofficial position of the United States Department of Commerce -
- Any opinions expressed in this message are NOT those of the US Govt. -

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>