Need of versions 5.0A & 5.1A

[Angelo Di Rocco]

I want to update my current installation of Tru64 v4.0F to v5.1B. According to the installation guide, I need to follow an update path from 4.0F to 5.0A to 5.1A to 5.1B if I do not want to do a full installation. Question: Where may I find versions 5.0A and 5.1A of Tru64 on HP's site for download? I have version 5.1B.

Thank you for your help.
Angelo

[Victor Semaska_3]

Angelo,

Have you considered doing a new install from scratch instead of trying to upgrade from v4.x to v5.x? I've tried doing those type of upgrades and almost always ran into problems of one kind or another. Much easier to do a new install.

If you do do a new install, install all OS subsets. That makes management easier as well.

Vic

[Vladimir Fabecic]

Hello
You can not find OS distributions on HP site for download. There are no such things for download.
Why would you do that? I think that Victor's idea is much better. I have done lots of OS upgrades and the best way is to perform instalation from begining. After instalation you can copy configuration files from old OS (passwd file and other important files).
User and data disks will be preserved.

[nasimuddin ansari]

The biggest problem in the fresh installation -
What about AdvFS partition existing on other hard disks having users data. AdvFS version on 4.0F and 5.x are different (?). Will it create problem?

How to regenerate /etc/fdmns directory, if restoring it from backup fails?
Any command that can automatically scan all the available disk media, check the file system type; if File system is AdvFS read the meta data and generate the domain information in /etc/fsdmns and create the symbolik links to corresponding disk partition?

It this issue solved, fresh installation can be done.

[Victor Semaska_3]

nasimuddin ansari,

You make a good point. The existing AdvFS domains will mount on V5.x but they will be V3 of AdvFS. V5.x comes with V4 of AdvFS. If I remember correctly V4 handles domains with large no.s of files better. You'd have to back up the domain, recreate it, and then restore in order to get V4. Look at the manpage for mkfdmn for more details.

To regenerate the /etc/fdmns directory I've always done it manually but I've never had a lot of domains on my servers. This is how I did it:

o Before the install I get a listing of the domains in /etc/fdmns:
# ls -lR /etc/fdmns/

o After the install manually recreate the domains so for each domain:
# cd /etc/fdmns
# mkdir
# cd
# ln -s /dev/disk/dsk##x

You may be able to restore them from a backup tape but I've never tried it.

Vic

[Vladimir Fabecic]

First of all, you allways must make backup copy of all file systems! You can restore them if needed. What Victor said about advfs domains is tru. You can mount them on V5.1B. If you are not having large number of files, you do not have to "convert" domains to V4.
I also recreate domains manually like Victor said. It should not be a problem.
If you want V4 domains you will have to recreate them and restore from backup tape. I have done it many times and it worked fine. You can even restore data from ufs file system (backuped with dump) to newly created advfs file system (using restore).
Before starting upgrade label disks. You can also use "old" device naming on V5.1x (except in cluster), but there is no need. Using hwmgr -show scsi and hwmgr - view devices you can see enough about disks.

[Victor Semaska_3]

Vladimir,

To copy the accounts onto the new system is a little more complicated if you have Enhanced Security enabled. This is due to the TCB.

o Verify everything is OK, if not, fix the problems:
# /tcb/bin/authck -av

Before backing up save the accounts and the default record:
# /tcb/bin/edauth -d p -g > /p.auth
# /tcb/bin/edauth -d d -g > /p.default

After the install restore /p.auth & /p.default and:
# cat /p.auth | /tcb/bin/edauth -d p -s
# cat /p.default | /tcb/bin/edauth -d d -s

Restore /etc/passwd & /etc/group.

Verify everything is OK:
# /tcb/bin/authck -av


Vic

[Vladimir Fabecic]

Victor
You are right about Enhanced Security.
There is something more that should be done: record kernel parameters using sysconfig -q so tuning newly instaled system will be easier.

[Han Pilmeyer]

A few additional thoughts:
- There's no need to go to the newer AdvFS format unless you're experiencing problems already. It's a nice to have, but not required.
- advscan may help you to locate the domains after the upgrade
- Be very cautious when moving parameters from V4 to V5. Some parameters have changed, e.g. some of the UBC and VM parameters. It might be easier to start with default parameters
- Also be sure to check whether your configuration is still supported with V5.1B. Support for non-PCI systems and some devices were dropped
- Similarly you should check support for your applications

[Victor Semaska_3]

With regards to system parameters what I've always done is:

o Change parameters as required by app.s like Oracle.

o After a few days run /usr/sbin/sys_check -all to see what changes it recommends.

Vic