Thanks to:
Vinzenz Esser <Vinzenz.Esser_at_emass.com> Alan Davis <Davis_at_Tessco.Com>
"Scott Plummer" <plummerd_at_ix.netcom.com>
"John J. Francini" <francini_at_progress.com>
Jim Bostwick <Jim_Bostwick_at_cargill.com>
<wmills_at_WellsFargo.COM>
Ian Mortimer <ian_at_physics.uq.edu.au>
Who had comments about my proposed procedure.
1. John has done these 3.2x to 4.0a to 4.0d rolling upgrades in less than a
day, and felt that the risk
of getting files mis-synchronized or lost is minimized by this method.
2. Alan pointed me to the genufi and related tools of the Reinstallation
Toolkit, which I'm playing with now.
3. John Plummer provided me with his annotated list, which I am attaching
below.
4. Vincenz pointed out that I forgot to consider the "worst case", and
should prepare and test a re-bootable
disk of my original system so I can go back if the bad-things-happen.
5. Jim cautioned me about a number of issues:
"I haven't actually tried as extensive a 'reload' as you contemplate,
but would worry a lot about simply copying the following from 3.2G to
4.0D:
/etc/sysconfigtab (there are a LOT of new knobs to twiddle, don't know
if your old one will be compatible)
/usr/shlib/so_locations (highly dependent upon the so's which almost
certainly HAVE changed)
/usr/sys/conf/param.c
I *think* there are changes to the xdm-config stuff as well - perhaps
someone else will have more concrete information.
I would also look very carefully at the rc.xxx scripts before blindly
replacing them - it's been a while since I drove a v3.2 system, but
believe there are significant changes."
6. Bill cautioned about C2 security
7. Ian suggested the double upgrade route by minimizing the number of
installed subsets to those actually used.
Thanks to all. I think what I will do is the following:
1. Make a Worst-Case copy of the system disk
2. vdump the sybase data
3. tar up the user's home directory trees
4. tar up the /etc/fdmns tree
5. And do a rolling upgrade.
But I want to take a closer look at the Reinstallation Toolkit which Alan
Davis suggested.
I will re-summarize after the event based on the singularity of what occurs.
Thanks and regards,
Bruce
My original question appears below:
I am about to have us embark on an upgrade of several 4100 systems which
run Sybase databases, all of which are now V3.2G and will be upgraded to
V4.0D plus jumbo patch 3. The systems each have several 3-channel RAID
controllers and about 40 Gbytes of data
Rather than follow the normal upgrade path of 3.2G to V4.0a to V4.0d, we
plan a different strategy for which I'd like your comments.
Because we want to minimize the downtime, even on a weekend, we plan do the
upgrade in the following fashion:
1. Set systems to Single User Mode.
2. Backup the Sybase Database files, logs, etc. by using tar.
3. Run a script which tars up everything we can think of which denotes the
system's current configuration.
Listed below are the files we want to save.
4. Install firmware upgrade
5. Install V4.0d, install patch3 using existing disk partitions
6. Untar the saved system configuration files
7. Reboot
8. Re-install Sybase
9. Untar the Sybase data, logs, etc.
Listed below is the set of files, relative to / that I think we need to tar
up. There is no LSM on this system, but there is
ADVFS in use with root_domain#root, usr_domain#usr, and var_domain#var as
well as several domains of data.
/bin/tar cR "$FILESTOSAVE" is the tar comand we will use with pwd at /
from our script.
I'd like your comments if we have left out anything critical, and on a
higher level, if you have any suggestions as to the sanity of this approach.
I will summarize.
./.cshrc
./.login
./.netscape
./.profile
./DXsession
./etc/apc_repository
./etc/binlog.conf
./etc/csh.login
./etc/disktab
./etc/exports
./etc/fdmns
./etc/fstab
./etc/ftpusers
./etc/gettydefs
./etc/group
./etc/hosts
./etc/hosts.equiv
./etc/hosts.lpd
./etc/inetd.conf
./etc/inittab
./etc/lprsetup.dat
./etc/magic
./etc/mailertable
./etc/motd
./etc/namedb
./etc/networks
./etc/ntp.conf
./etc/passwd
./etc/passwd.dir
./etc/passwd.pag
./etc/ppp/options
./etc/printcap
./etc/profile
./etc/rc.config
./etc/remote
./etc/resolv.conf
./etc/routes
./etc/rpc
./etc/sec/audit_events
./etc/sec/event_aliases
./etc/securettys
./etc/sendmail.cf
./etc/services
./etc/shells
./etc/snmpd.conf
./etc/svc.conf
./etc/sysconfigtab
./sbin/bcheckrc
./sbin/init.d
./sbin/rc0.d
./sbin/rc2.d
./sbin/rc3.d
./usr/lib/X11/app-defaults/DXpause
./usr/lib/X11/app-defaults/DXsession
./usr/lib/X11/app-defaults/DXterm
./usr/lib/X11/app-defaults/Mwm
./usr/lib/X11/app-defaults/XTerm
./usr/lib/X11/app-defaults/Xdefaults
./usr/lib/X11/app-defaults/pwrchute
./usr/lib/powerchute
./usr/local
./usr/opt/swxcr/swxcrmon.maillist
./usr/share/lib/Mail.rc
./usr/share/lib/termcap
./usr/share/lib/terminfo/dec.ti
./usr/share/lib/kernel_options/kernel_options.db
./usr/shlib/so_locations
./usr/skel
./usr/sys/conf/param.c
./usr/users
./var/adm/cron/.proto
./var/adm/lmf
./var/adm/syslog.dated
./var/adm/sendmail/aliases
./var/shlib/so_locations
./var/spool/mail
./var/spool/mqueue
./var/yp/Makefile
./var/yp/ypxfr_1perday
./var/yp/ypxfr_1perhour
./var/yp/ypxfr_2perday
./var/X11/Xserver.conf
./var/X11/fs/config
./var/X11/xdm/Xresources
./var/X11/xdm/Xservers
./var/X11/xdm/Xsession
./var/X11/xdm/Xsetup_0
./var/X11/xdm/xdm-config
./var/X11/xdm/xdm-config.fs
./var/spool/cron/crontabs
Regards
+--------------------------------------+
Bruce B. Platt, Ph.D.
Comport Consulting Corporation
78 Orchard Street, Ramsey, NJ 07446
Phone: 201-236-0505 Fax: 201-236-1335
bbp_at_comport.com, bruce_at_ bruce.platt_at_
OR, bruce_at_bbplatt.com
Received on Fri Jun 04 1999 - 12:06:58 NZST