3.5.1 Matrix Server Upgrade Guide
Chapter 3: Double Rolling Upgrades 34
Copyright © 1999-2006 PolyServe, Inc. All rights reserved.
24. If you did a fresh installation of the operating system, extract the
backup tar files saved in step 16 to /etc/opt/polyserve and /var/opt/
polyserve.
25. Install the kernel:
• For SLES9 systems, install the Matrix Server 3.5.1 Support RPM
(use the 32-bit version) and the MxFS-Linux kernel patches RPM
and then compile the kernel. See Appendix B for more information.
• For RHEL4 systems, install the appropriate PolyServe binary
kernel. Run the following command:
# rpm -ihv <kernelname>.rpm
Ensure that the new kernel is set as the default in the /boot/grub/
menu.lst file. If you need to build a custom kernel, see Appendix C
for more information.
26. Reboot the server.
27. Install Matrix Server 3.5.1 from the Matrix Server product CD or the
location where you have downloaded the software. Be sure to install
the 64-bit version of the RPM.
# rpm -i <mountpoint>/pmxs-3.5.1-<xxxx>.x86_64.rpm
28. When you removed the previous version of Matrix Server, the
uninstall process saved all Matrix Server configuration files that had
been modified at your site. The old files were saved with the suffix
.rpmsave.
After Matrix Server 3.5.1 is installed, the installation process runs the
mxcheck utility, which will report errors for the saved files. Review
the mxcheck report to locate the saved files and then compare them
with the new versions of the files that have been installed. You will
need to migrate your customized values from the old files to the new
files as necessary. You can then delete the .rpmsave files.
NOTE: If your mxinit.conf file includes SanPulse start options, be sure
to rename the options as described under “Changes for
SanPulse Start Options” on page 4.