Completing an Upgrade

9

Overview

This chapter describes files to check and steps for completing an upgrade.

What Happened During the Upgrade

A record of what the installation program did during an upgrade can be important to determine if the upgrade was a success. The output of the upgrade is saved in the following files:

If upgrade fails - /a/var/sadm/system/logs/upgrade_log
If upgrade completes and system reboots - /var/sadm/system/logs/upgrade_log

Cleaning Up the System After an Upgrade

During an upgrade, the Solaris installation program merges local software modifications of the existing system with the new software; however, in some cases, it is not possible. The following file provides a list of the unpreserved local modifications during the upgrade that may need to be fixed:

If upgrade fails --/a/var/sadm/system/data/upgrade_cleanup
If upgrade completes and system reboots - /var/sadm/system/data/upgrade_cleanup

Table 9-1 provides the entry descriptions of the unpreserved local modifications that may be found in the upgrade cleanup file.

Table 9-1 upgrade_cleanup

Entry	Explanation	Recommended Action
*file1: existing file renamed to file2*	*file1* was on the system at the time of the upgrade. It had been modified since its original installation, so upgrade renamed *file1* to *file2* and saved the new file as *file1*.	Determine whether the modifications made to *file2* should be made to the new version of the file, *file1*.
*file1: existing file preserved, the new version was installed as file2*	*file1* has been preserved, and upgrade installed the new version of the file as *file2*.	Determine whether the differences in the new version of *file2* should be incorporated into the preserved version of *file1*.
*file:* had been deleted and has now been restored	*file* had been deleted from the system since its original installation, and the upgrade installed the new version of *file*.	Determine whether *file* should be deleted.
*file: file type was changed from type1* to *type2*	*file* has changed types since its original installation, from *type1* to *type2. For example, you may have changed an actual file to be a symbolic link. The upgrade changed file* back to its original type, *type1*.	Determine whether *file* should be changed back to *type2*.
*file: target of symbolic link was changed from target1* to *target2*	Since the original installation, *file* was changed to be a symbolic link to *target2* instead of *target1. The upgrade changed file* to point to its original *target1*.	Determine whether *file* should be changed to point to *target2*.
*file1: target of hard link was changed from file2*	When originally installed, *file1* was a hard link to *file2. At the time of the upgrade, file1* was no longer a hard link to *file2*`.`Upgrade restores the original hard link.	Determine whether *file1* should be changed to what it was before the upgrade.

How to Upgrade Clients With Different Platforms and Platform Groups

If you've upgraded a heterogeneous OS server, clients of that server are automatically upgraded only if their platform (SPARC, x86) and platform group (for example, sun4d, sun4L, i386) is supported by the Solaris CD. For example, if you upgrade a SPARC server using the SPARC Solaris CD, only SPARC clients that share the platform group on the CD are upgraded.

To upgrade clients with different platforms and platform groups, you must use the server_upgrade command. See the server_upgrade man page or x86: Solaris 2.5 Installation Notes or the SPARC: Installing Solaris Software for more instructions.