In regard to: [Networker] Networker 7.4 SP2 - How to start over, JGillTech...:

Is there something
I should do before I wipe out the current install?

Read the threads in the archive that Michael Leone has been involved in
in the past couple weeks.  He's experienced some major difficulty getting
at his old savesets because client ids weren't preserved when he moved to
a new system.

Assuming the hardware and the server name will stay exactly the same, I
would (off the top of my head)

- run an mminfo report with client names and client ids, and save that
  to a file on some other system.  Even if you change the client names,
  there's no harm (and there's some benefit, as Michael has learned) in
  preserving the client ids when you create the clients on the new server.

        mminfo -a -r 'client,clientid' | sort -u > clients-clientids

- save to a file (and probably print and store in a secure area) all
  your current licensing info, including the enabler and auth codes.
  When you reinstall, you will need to input the enablers to activate your
  licenses for a "trial period" (probably 45 days).  You may even be able
  to use the same auth codes (which permanently activate the licenses),
  but I wouldn't bet on that.

        echo 'print type: NSR License;' \
                | nsradmin -s yourservername -i - > networker-enablers


- do a full backup of your server using NetWorker
- do a bootstrap save (if it didn't happen as part of your server backup).

- run a bootstrap report, and save that output somewhere offsite.  Make
  a note of what volume your bootstrap is on, and put that volume aside.

        mminfo -B > networker-bootstraps

- run an mminfo report of all savesets and save it to a file.  You'll
  probably never need it, but you never know.

        mminfo -s yourservername -ot -av > all-savesets-by-date


There may be other stuff I'm not thinking of, but this should be a good
start, and will cover the major stuff.

  The client names
will change when I reconfigure... something that I have recently done
and experienced problems with.  Does the DR guide outline a DR practice
run?

DR assumes you want to bring everything back exactly as it was.  What
you'll be doing has very little to do with DR.

I respect Bruce's opinion and comments on this, but I'm on the other side
of the fence.  If you have the time, a "do over" will get you into a known
good state -- you might never get to that point by fixing things as you
find them.  Installing NetWorker and configuring everything from scratch
is also a good learning experience.

Fazil's comments about having a plan are good advice.  Knowing what types
of data retention categories you have will tell you what you need for
pools.  One mistake I made when I set up NetWorker was to use more pools
and more groups than I really need.

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