At 08:10 AM 8/23/02 , Matthew Bourne wrote:

If your /nsr directory is a symlink to filesystem /flibble on the Solaris
box, you will need to create a filesystem /flibble on your HP box and re-
create the links.  MMINFO really is that fussy.

Yes indeed.

We discovered this (and a few other things) earlier this year.  We had our
Networker installed on the drive with the most free space, and had a
symlink pointing to it ("ln -s /applications/nsr /nsr").

Later, we upgraded the disk space on the server.  We then deleted the
symlink (with Networker shut down) and copied /applications/nsr to
/nsr.  When we cranked things up, we discovered to our dismay, that
Networker was using =both= areas.  It seems that somewhere during the
initial installation, Networker figured out where it =really= lived (cd ..
; pwd ; cd .. ; pwd) and put that in the resources file instead of using
the /nsr link.

But some utilities use the resources entry and some do not.  Now we have
two sets of client indexes and two different media databases, one with new
data and the other with before-the-relocation data.  And support says you
absolutely cannot merge databases.  They say the only option is to use
scanner on every tape written to since the relocation.


        -crl
--
Chad R. Larson (CRL22)    chad AT eldocomp DOT com
  Eldorado Computing, Inc.   602-604-3100
     5353 North 16th Street, Suite 400
       Phoenix, Arizona   85016-3228

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=