From: Cohen, Andy (Andy.Cohen@cognex.com)
Date: Thu May 08 2003 - 10:35:50 EDT
Sorry for the somewhat delayed summary but I wanted to do the whole upgrade
to completion before summarizing.
Several great suggestions:
=======================================
First Denise McCracken gave me a script to capture most, if not all, of what
was needed. Note: copy or save $SAVEDIR to another machine or an NFS mount
so you have access to it during and after the upgrade.
CAUTION: don't run this without editing for your site!
Maybe this will help. It's an excerpt from a script that I wrote to do OS
upgrades. Edit as necessary, don't run it straight up. ;)
cd $SAVEDIR
fi
#
echo "Making directories for saveouts..."
mkdir etc dna lmf rcd init.d local spool tftpboot home vol
echo "Making special directory for LSM saveouts..."
#Save out LSM stuff for worst-case disaster recovery
if [ -d $SAVEDIR/volstuff ]
then
cd $SAVEDIR
/bin/rm -r volstuff
fi
volsave -d $SAVEDIR/volstuff
echo "Saving out the /etc directory..."
cd /etc
tar cvpf - .|(cd $SAVEDIR/etc;tar xvpf -)
echo ""
echo "Saving out /var/dna..."
cd /var/dna
tar cvpf - .|(cd $SAVEDIR/dna;tar xvpf -)
echo ""
echo "Saving lmf (licenses)..."
cd /var/adm/lmf
tar cvpf - .|(cd $SAVEDIR/lmf;tar xvpf -)
echo ""
echo "Saving sbin..."
cd /sbin
tar cvpf - rc?.d|(cd $SAVEDIR/rcd;tar xvpf -)
echo ""
echo "Saving out /sbin/init.d..."
cd /sbin/init.d
tar cvpf - .|(cd $SAVEDIR/init.d;tar xvpf -)
echo ""
echo "Checking to see if /usr/local is linked to /$SQROOT..."
if [ -d "/usr/local/upgrade" ]
then echo "Linked to /$SQROOT, no saveout needed."
else
cd /usr/local
tar cvpf - .|(cd $SAVEDIR/local;tar xvpf -)
fi
echo ""
echo "Saving out spool directory..."
cd /usr/spool
tar cvpf - .|(cd $SAVEDIR/spool;tar xvpf -)
echo ""
echo "Saving out tftpboot..."
cd /usr/tftpboot
tar cvpf - .|(cd $SAVEDIR/tftpboot;tar xvpf -)
echo ""
echo "Checking for and saving home files..."
cd /
tar cvpf - home/*|(cd $SAVEDIR/home;tar xvpf -)
tar cvpf - usr/home/*|(cd $SAVEDIR/home;tar xvpf -)
tar cvpf - usr/users/*|(cd $SAVEDIR/home;tar xvpf -)
echo ""
echo "Saving $HOSTNAME to $SAVEDIR..."
cd /sys/conf
cp -p $HOSTNAME $SAVEDIR
echo ""
echo "Saving the rhosts file..."
cd /
cp -p .rhosts $SAVEDIR
if [ -d "/etc/vol" ]
then
cd /etc/vol
tar cvpf - .|(cd $SAVEDIR/vol;tar xvpf -)
fi
clear
=======================================
Next Dr. Otto Titze sent me this:
one never should copy /etc/fstab!
To recover other disk with advscan carefully look at /etc/fdmns. It is not
possible to copy that. The entries have changed, istead of rzxx you now have
to use dskxx.
Plan carefully where to store your old configuration files
- first I had the configuration file on another local disk
then I run into troubles with advscan and didn't get them immediately
- maybe it is better to have them on a NFS disk
Some things don't save much time and are re-done again than for copying
the configuration files.
E.g.
-NFS-setup
-also netsetup
-I found out that I had to do NISsetup again at clients and slaves.
Even at the master copying the appropriate files and modifying rc.config
did not work. Finally I made a new setup, copied the files and then
repeated the setup with modify.
- latsetup is also fast, but you should know how many terminals you
had before. And then copy old latstartup.conf.
You save a lot work regarding the printing environment. Copy the old
printcap and the particular spool directories. (This also a good way to
unify
the printing environment on all systems.
Also copying the lmf database saves a lot of time (s.below)
Because some things which planned originally didn't work and I
run in many problems the checklist below may not be complete
(I had tu survive!)
PS: My problen was a thread on this list under subject
Tru64 new instal - but with old settings
Here my final check list:
SUMMARY (my personal action/check list, as it worked now):
- New Installation
- advscan -r dskX
- edit content of old fstab into new /etc/fstab !!!
- mount the disk with the backup files
- mkdir old mount points
- mount -a
- netsetup, DNSsetup, nfssetup
- copy from old /etc/ to new /etc:
printcap
latstartup.conf
hosts.*
securettys
ftpusers
exports
bootptab
tftptab (one some systems)
shells
- do latsetup
- restore /var/adm/lmf/ldb and ldb_history (get license database)
- copy -i /usr/skel/* to /usr/skel
- copy /var/spool/lpd* to /var/spool
- do nissetup
- restore /var/yp/src (only for NIS master)
- do nissetup (using modify)
- Check:
/etc/inittab for lat gettys
/usr/sys/conf/NODENAME for changes made to the old system
compare /etc/sysconfigtab, edit changes from old /etc/sysconfigtab
=======================================
Shaun Racine said:
We had a problem with corrupted hardware database (which was corrupted on
all our backup tapes too), so to resolve we did a fresh install of 5.1A on
a AlphaServer 4100, not clustered. Our data disk was separate under LSM,
we managed to back this up to tape before hand and restore to non-LSM data
disk afterwards. In our configuration /var was in same partition as /usr.
The files we needed were;
/etc/printcap
/etc/passwd
/etc/hosts
/etc/group
/.rhosts
/.profile
/etc/hosts.equiv
/usr/users....
/usr/spool...
/usr/local...
/etc/sysconfigtab !!! don't just copy old one in, but compare for your
site specific changes.
crontab !!! , the one from backup was empty, so I suggest copying it to
ordinary file first.
and re-run mailsetup.
We created 2 new advfs partitions on our datadisk;
/exroot
/exusr
and have them mounted all the time. These hold a complete copy of original
root (/) and usr partitions, made by using vdump/vrestore pipe. So if we
have forgotten anything then we can still get it without bother of
resorting to tape.
========================================
and Howard Arnold sent:
All the license information is kept in /var/adm/lmf/ldb. I would copy this
file to a staging area some place to be reinstalled later. I would also copy
/etc/hosts, /etc/services, /etc/resolv.conf. Any others I think would depend
on what you are running. If your running Oracle I would cut out the
parameters in the /etc/sysconfigtab file into a stanza file to be reloaded
again once 5.1A is built. I wouldn't just copy the sysconfigtab file because
it is a little different in 5.1A. The same is true for /etc/rc.config.
====================================
That's it. The upgrade went very well (after dealing with 3 different
hardware failures/problems.
Thanks again everybody!
Andy
ORIGINAL QUESTION
=================
Hi,
We have 3 machines we need to upgrade from 4.0E (or F) to 5.1A. I've done
this on a 4100 by upgrading to each interim release but want to do the rest
of the machines by installing 5.1A fresh. The question I have is how to do
this while minimizing the amount of post-installation configuration work.
For instance I'd like to be able to save as many configuration files from
4.0 as possible so I can copy them back after installing; e.g. -- whatever
files store the LICENSE PAK information or networking information, etc. Has
anybody done this? Do you have a list of what these various files are? I
understand that the complete list would vary by implementation but if
somebody had some sort of list that could be shared I'd really appreciate
it.
The machines I'm upgrading are a 1000A, an AS 800 5/500, and a DS20E. The
DS20E has an RA3000 attached to it and is using LSM to mirror the system
disks (I don't know if LSM is used for the RA3000 in any way).
Many thanks!
Andy
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:18 EDT