|
[Networker] How to avoid license conflict between two servers?
2010-02-24 20:59:54
Hi,
We have a new test server operating under 30 day eval. Getting ready to
put this into production soon. Still testing. We will be recovering the
media database and resource database from our older current server (DR
recover) in order to test some recoveries of older data and to run some
queries against the media database to verify that it looks the same as
on the older server.
The old server is still handling nightly backups until the testing has
been completed on the new machine, however. Both servers have different
host names, but the same client id (I made sure of that).
I'm concerned about the possibility that both servers could get shut
down when the test server sees that it now has licenses assigned to the
old server (as a result of recovering the old server's resource
database). But I don't want to have to recreate all the NSR resources
from scratch, though, and I don't really want to have to shut down the
old server during our tests.
Questions:
1. Do we have to do the host transfer/affidavit immediately and get new
keys even though we're not ready to go live just yet?
2. Can I avoid the license conflict issue by removing all the files on
the new test server under /nsr/res/nsrdb that contain any enabler codes
from the old server?
e.g.
# cd /nsr/res/nsrdb
# ls
00/ 01/ 02/ 03/ 04/ 05/ 06/ 07/ 08/ 09/
# grep a_given_enabler_code */*
I can run nsradmin on the older server and report all the NSR resources
of type license and then grep for 'enabler code' to generate a list of them.
3. On the older server, I notice that one file under 02 seems to have
all the enabler codes listed in it in two column list with each column
in double quotes, featuring a code and date. The second column appears
to be the enabler code. Not sure what the first column is?
Should this file that lists all these also be removed on the test server?
4. If I remove these files, will the new test server still be able to
run in eval mode?
5. What happens if the servers detect a collision and shut themselves
down? Is it simple enough to keep one or the other down and simply
restart the other and all is well?
6. Thought I'd read that once you recover the old media database and res
databases and restart the server that it will see that this was for a
different server (same client id, though) and then change the expiration
date to only 10 days, even if you had more time left prior? That true?
What if you only have, say, 8 days left before you do the DR restore.
Would it give you 8 or 10, whichever is bigger, or would it go dead at
that point since 8 is less than 10?
--
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>
|
- [Networker] How to avoid license conflict between two servers?,
George Sinclair <=
|
|
|
