Thanks for the replies. I got a few different methods, and from the replies,
it looks to be a bit tricky if the IP address and hostname are different (which
they are in my case). Anyway, I am holding off on doing it at this point, but
below are all the replies I received.
thanks again,
dan
ORIGINAL --------------------------------------
I need to move my NSR server from a 2100 to a 3000/600, also moving the same
tz877 jukebox, and have a bunch of indexes, etc. Can it be done? If so, how?
Both are V3.2c of DU and V3.2 of NSR. I looked at it, tried to move the index
directory, but saw that the res directory has a bunch of stuff, tried to move
that, etc, but failure every time. None of the nsr daemons will start.
REPLIES ---------------------------------------------
Kurt Carlson <SXKAC_at_orca.alaska.edu>
> I need to move my NSR server from a 2100 to a 3000/600, also moving the same
> tz877 jukebox, and have a bunch of indexes, etc. Can it be done? If so,
how?
if the target system doesn't have any indexes it needs to keep,
just use 'recoverindex' off a tape from the source system on the
target system... same process you would use after a disaster
to build your system from scratch. we've got sample docs
of that process here (having had to do it once after a disaster),
if that would help i can send it.
if the target system does have some indexes to retain it get's
stickier. easiest thing to do would probably be define new
clients and backup them up to build new indexes. there probably
is some means to merge indices from two servers, but i've never
tried that.
> Both are V3.2c of DU and V3.2 of NSR. I looked at it, tried to move the
index
> directory, but saw that the res directory has a bunch of stuff, tried to move
> that, etc, but failure every time. None of the nsr daemons will start.
Attempting this way would require merging both the resources and the media
databases... might be possible (if you find out, please summarize).
kurt carlson, u of alaska
---------------------------
Paul Tutcher <pault_at_mailhub.wpl.com>
You need to copy everything over with uasm... That is the same command =
NSR uses to backup files with... I have moved my NSR to 2 different =
servers the following way...
1) Unload all tapes from the jukebox through NSR
2) Remove the jukebox from NSR (if SCSI addresses with change)
3) Shutdown NSR
4) Use uasm to copy the /nsr directory to the new machine through NFS
5) Bring up NSR
6) Add the jukebox
THE MOST IMPORTANT THING IS NOT TO CHANGE THE IP ADDRESS!! NSR uses the =
IP address of the machine to mark the tapes and indexes... I didn't =
even change the machine name... If you change either you will have to =
edit the nsr.res and nsrjb.res files by hand or things will get really =
screwed up...
--------------------------------
bobj_at_soc.duke.edu (Bob Jackson)
I am running DECnsr on an Ultrix system and using it to backup Ultrix
and Alpha workstations. About 18 months ago I had to reconfigure
things and recall that I had to use the uasm facility to move the
index files around. These files have special properties that are not
properly preserved if you move them around with dump/restore for
example. I used commands of the following form:
uasm -si . | (cd target_dir; uasm -rv)
~~~~~~~~~~
--------------------------------------
"Jeffrey S. Jewett" <spider_at_umd5.umd.edu>
Greetings. I picked this off the Legato User's mailing list (which I
recommend
that you subscribe to - instructions at the end of the article), and it shows
step by step how to de-install and re-install the NetWorker (e.g. DEC NSR)
system. It also refers to the Legato Tech bulletins 121 (Moving a NetWorker
Server) and 138 (Renaming a NetWorker Client or Server).
There may be some slight adjustments necessary to port this to a DEC NSR
environment, but basically it's the way to go.
Jeffrey S. Jewett
Core Computing Services
Rm. 1311, Computer Science Center
University of Maryland, College Park 20742
301-405-3054 Fax: 301-314-9220
------- Forwarded Message
Date: Thu, 18 Apr 1996 10:46:19 +0200
From: Christian Sodemann <chs_at_geografik.dk>
Message-Id: <199604180846.KAA19848_at_geografik.dk>
To: networker_at_iphase.com
Subject: networker - Complete reinstall of OS and Networker
Cc: lzerbi_at_tlvsno.vim.tlt.alcatel.it, jschiv_at_lehman.com,
Knut.Hellebo_at_nho.hydro.com, trumbull_at_sas.com
X-Sun-Charset: US-ASCII
Sender: owner-networker_at_iphase.com
Precedence: bulk
>>>>> Christian Sodemann <chs_at_geografik.dk> posted to the networker list:
Hi all.
Way back in February we were planning a complete reinstall of the OS (Solaris)
and upgrade of Networker. I posted a request and received several good hints
from
Ed Trumbull, Knut Helleboe and Bert Sluys. Legato Technical Bulletins 121 and
138
were also very usefull.
It turned out, that Networker 4.2 wasn't released by Sun. So I decided to
do it in two steps (following the debate about 4.2, I'm glad we postponed
it)...
On top I also changed the (domain) name of the server and a few clients!
This is what you may want to do:
1) Run a full backup (and implicitly 'saveindex -l full').
2) Run:
nsrck -F client
for all clients. This will ensure that the backup is clean.
3) Do an ufsdump of the entire /nsr filesystem (you may want to
stop the server while doing this - see below):
/usr/sbin/ufsdump 0f /dev/rmt/0b /actual/nsr/dir
Keep this - just in case...
4) To get rid of any "dead" clients do the following:
4a) Remove the client setup the graphical interface - just click a button.
4b) Remove the index files using some variation of 'rm -rf /nsr/index/client'
4c) Run 'mminfo -a -v -c client' and pick up all ssid's (if any).
4d) Run 'nsrmm -d -S ssid' for all ssid's (if any).
5) If you wish to rename do the following:
5a) Make new NS enties for clients and servers that need renaming.
Do it in /etc/hosts, NIS or DNS (CNAME)...
5b) Use the graphical interface to create new clients (and server) each with a
client alias to the corresponding old name resource.
5c) Shut down the server:
/etc/init.d/networker stop
5d) Delete all the old clients _except_ the server using the graphical
interface.
5e) Use a command like:
mv /nsr/index/old.name /nsr/index/new.name
for each client (server) renamed.
5f) If you rename the server you must manually edit /nsr/res/nsr.res.
The bulletin is a little vague on this topic. You need to search for "aliases:"
to find the client entry for the old server (the type of those paragraphs are
"type: NSR client;"). Delete the entire paragraph. The nsrmmdbd will rename
the other client indexes automagically when restarted (later!).
6) Do an ufsdump of the entire /nsr filesystem on another tape (or disk):
/usr/sbin/ufsdump 0f /dev/rmt/0b /actual/nsr/dir
This is the one you want to use later.
7) Say goodbye to the old Solaris 2.3/2.4 and wipe it out with Solaris 2.5.
I've been asked: why do this? why not upgrade? With all the patches
and security fixes and our local messing with the system, I do like
to start afresh from time to time...
8) Reinstall Networker 4.1.2 (or 4.1.3). Do NOT start the daemons. You
may also go for 4.2 right away, but you need to apply the patches
first. You are probably better off doing in two steps.
9) Restore the indexes. I always do this interactively:
cd /new/mount/point
/usr/sbin/ufsrestore if /dev/rmt/0b
...
10) Make a symbolic link from /nsr to the new dir (or alter the link
made by the install script).
11) Start the daemons and pray:
/etc/init.d/networker start
12) Install Networker on the clients if needed. Remember to fix
/etc/init.d/networker: "/usr/sbin/nsrexecd -s new.server" if
you don't.
That's all folks!
Regards,
Christian Sodemann
Geophysicist, B.Sc. M.Sc.
-----------------------------------------------
Hellebo Knut <Knut.Hellebo_at_nho.hydro.com>
It should be fairly easy if the new server inherit the old one's name and
you install the DEC nsr files in the same location as the old ones. If you
don't do this there will be trouble ahead because there are a lot of
references to the old servername in the databases.
Received on Mon May 13 1996 - 19:31:59 NZST