cold install

[Jeff Hagstrom]

I am going over the documentation to cold install 11.00 over 10.20 and it references configuration to save. What configuration files is it talking about?

[Joseph C. Denman · Accepted solution]

Here is a good answer on a question I posted a while back.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xe24eded2442ed5118fef0090279cd0f9,00.html

Note James' response.

...jcd...

[James R. Ferguson]

Hi Jeff:

Here's the basic list I tranfer to safe-keeping for reference, reuse, and comparing against new configurations (via 'diff') during a cold installation process:

# /.forward
# /.profile
# /etc/profile
# /etc/group
# /etc/hosts
# /etc/inetd.conf
# /etc/inittab
# /etc/nsswitch
# /etc/ntp.conf
# /etc/passwd
# /etc/rc.config.d/netconf
# /etc/rc.config.d/netdaemons
# /etc/rc.config.d/nfsconf
# /etc/resolv.conf
# /etc/sendmail.cf
# /etc/services
# /etc/shells
# /etc/shutdown.allow
# /var/adm/cron/*.allow
# /var/adm/fbackupfiles/*
# /var/spool/cron/crontabs/*
# /sbin/init.d/

Don't forget to add your volume group 'vgexport' mapfiles too.

Regards!

...JRF...

[A. Clay Stephenson]

Hi Jeff,

I would add, get your user's home directories,
export / save your lp environment, and also
do a hardcopy listing of bdf, ioscan -fn, and sysdef.

The kernel tunables may change but you will have a good starting point by having the sysdef listing.

It is very possible that your SCSI device nodes may change especiallly if hardware was added to your system after 10.20 was loaded.
For example what was c2t2d0 may now be c3t2d0; this is not bad just be aware that it could happen when you vgimport the non-vg00 stuff.
This is why it's nice to have a before and after ioscan -fn. The hardware paths (10/4.12.0) will remain the same but the device nodes may not.

I will say that none of these things are essential but they surely make life easier.

Clay

[Mark Vollmers]

Jeff-

I addition to copying the files James listed to somewhere safe, also be sure to have a full backup of everything. That way, in case you lose or forgot to backup, /etc/passwd, for example, you can pull it off the tape (to a non-root directory) and get the info. Otherwise, you'll find out you forgot to copy that config file or something you need about five minutes after it's too late to go back and get it. Good luck.

Mark

[James R. Ferguson]

Hi Jeff:

I'll add one more comment. Make an Ignite 'make_tape_recovery' tape *before* you start. If all goes "south" and you want to return to ground-zero, you can.

Another, perhaps less obvious, advantage of the 'make_tape_recovery' is that you get a copy of vg00. You can always extract (albeit slowing) a file from the tape that you forgot to include in your list. This includes the mapfiles for all of your volume groups, which makes like easier when you go to 'vgimport' volume groups after the installation.

...JRF...

[Dan Bonham]

Basically,
Any system configuration file that you've added to or customized needs to be saved since they will be written over by the new system files. Netconf in an important one but the list someone had above is a good guide to use.
after you've saved the files, I would tar your entire vg00 just incase you discover a file you need after the upgrade. Also, you'll need to use ignite-ux if you want to extend "/" or "/stand" filesystems.

Rusty Sapper