In regard to: Re: [Networker] NW 7.2->7.4 upgrade - clients..., Eugene...:

I am looking into upgrading our 7.2.2 server to 7.4, and moving to
RHEL 4 from RHEL 3  in the process.  I have tried reading the disaster
recovry guide 7.4 cover to cover, but I haven't been able to get the
big mental picture of the process.

Could someone explain in general the steps need to move host OS and
Networker server, while retaining client index database?

Are you actually *moving* to a different physical server, or are you going
to be upgrading/reinstalling the OS on the same hardware it currently
resides on?  Depending on your answer, you might be able to avoid most or
all of the disaster recovery procedure.

I can tell you how we plan to do it.  We're going to be using the same
hardware, so I will be reinstalling (not upgrading) the OS on that system.
Our nsr stuff (/var/nsr is the mountpoint, /nsr is a symlink to /var/nsr)
is on separate disks from the OS, so I can easily preserve NetWorker state
while kickstaring the new operating system.

With that in mind, the steps are roughly

- input the necessary update enablers to allow an upgrade to 7.4.x.

- run NetWorker DB consistency check/fix commands (the recommended nsrim
  -X, nsrck -L6, etc.)

- (optional for the paranoid) save the client indexes using "savegrp -O"

- do a full backup of the NetWorker server, using NetWorker.
- Note the bootstrap info from the backup AND what tape the bootstrap was
  saved to, just in case.

- shut down the backup server
- pull the disks with the /var/nsr filesystem, so there's absolutely no
  chance that they get blasted during kickstart.

- kickstart the same hardware as RHEL 5.2.
- perform any post-kickstart manual config, and verify jukebox and drive
  connectivity using mtx.

- add the drives containing /var/nsr back to the system, and get them
  fsck'ed, mounted, and add to /etc/fstab and verify that they get
  correctly mounted after a reboot.

- install NetWorker 7.4.2.  The install will detect the presense of
  NetWorker databases and automatically convert them to the newer format.

- install post-7.4.2 security patch.

- test backups, restores, etc.


Assuming you can somehow exactly preserve the stuff under /nsr, even if
that means doing an rsync to a different box and then rsyncing it back
later, there shouldn't be any need to go through a disaster recovery
procedure for this type of NetWorker upgrade.

Note: Oscar's note about nsrjobd doesn't make me very excited about this
upgrade.

Tim
--
Tim Mooney                                        Tim.Mooney AT ndsu DOT edu
Information Technology Services                   (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