In regard to: Re: [Networker] Moving client to a different Networker...:
I would think that transferring the indexes and running the "scanner -m"
might have saved me a significant amount of time over a full "scanner
-i" given that these are large savesets with many small files (mailstore
backups, some savesets spanning 5+ tapes)...if I read right, there
wouldn't be a danger of the indexes being pruned in the meantime
(networker runs nsrck -L1 on startup, and it seems that pruning would
only happen with an -L3 or higher, or a -m).
I wouldn't want to bet large amounts of money on that, but in general
I think that's true.
Oh, one other thing that's important to note: when you create the clients
on the new server, be certain you use the exact same client id as the old
server. That prevents the problem that has been discussed in another
thread today, about the ~client-1 appearing after a scanner.
However, if I do go the route of simply keeping a record and scanning in
savesets as needed, I'll have to use scanner -i, and I think in the end that
is what I will go with. I've backed up a copy of the output of mminfo -av and
mminfo -av -m, and will use that as needed.
That should give you what you need. Note: there's nothing to say that you
have to blow away your old media database on your old system. Just shut
down NetWorker, rename /nsr to /nsr.oldserver, delete any client index
directories under /nsr.oldserver that you need to to free up space, and
then install the storagenode/client/etc. packages. If you ever need to go
back and do media database reporting, you just move the old directory back
into place and temporarily install the server component.
As for ssid collisions, according to Preston's post and my searching, looks
like I should not have a problem with ssids. The only matching short ssids
occurred between a saveset on the new server and a bootstrap on the old
server, which I would not have need nor ability to recover.
I had often wondered about the newer format ssids and whether they were
globally unique. It's nice to have some confirmation that the longer
ones are generally going to be unique.
Tim
--
Tim Mooney Tim.Mooney AT ndsu DOT
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
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
|
