Use the following checklist to verify that you have adequately prepared your system for a successful upgrade.
Note: Before upgrading, back up the entire hard disk to prevent loss of data if the upgrade fails.
If you have upgraded your operating system, for example from FC 2 to FC 4, the above-mentioned RPMs must be updated for compatibility with FC 4.
up2date
on the server (if using Red Hat Network (RHN) for obtaining RPM updates)?You must install the RPM up2date
on the server if you want to use RHN for obtaining RPM updates. After installing the RPM, run the up2date
utility to register the server with RHN.
spamassassin-tools
(if installed on the server)?If you are upgrading from FC 2 to FC 4, you must uninstall the RPM spamassassin-tools
from the server, otherwise the upgrade will fail. To uninstall the RPM, run the following command:
rpm -e spamassassin-tools
Extras
in the Fedora repository.You must set up a yum repository on your local FTP server or on the server on which you are installing Parallels Pro Control Panel. The installer obtains the operating system RPMs and the required RPM updates from the repository during the upgrade. For instructions on setting up a yum repository on your local FTP server, refer to the document Setting Up a local FTP server to install Parallels Pro for Linux at the Parallels Pro Control Panel for Linux Documentation page (http://www.parallels.com/en/pro/docs).
vsftpd
, postfix
, and apt
?Uninstall vsftpd
and postfix
. If you use the apt tool for updating Linux packages, uninstall the apt RPMs apt, atrpms, atrpms-package-config, libapt-pkg
before you upgrade, otherwise the upgrade might fail. The installer uses the yum tool to provide the requisite package management environment. The presence of apt RPMs can cause RPM conflicts during the upgrade.
If you want to use apt
to obtain updates, you must install the tool after upgrading Parallels Pro Control Panel.
To verify site status:
Sites that are inconsistent display the following message:
This site is currently in an inconsistent state. This may be the result of an active or failed edit.
For more information on inconsistent sites and ways to resolve them, please search Parallels Pro Control Panel knowledge base articles (http://kb.swsoft.com/en/products/ensimprolinux).
MySQL database names that include a period (.) must be changed before an upgrade. Note that usage of the charactersforward slash (/), period (.), and equal to (=)is invalid. For instructions on renaming the database, refer to the Site Administrator online Help (accessible through the Help option on the Site Administrator control panel).
To verify that Microsoft FrontPage is consistent on all your sites, log in to the server as the root user and run the following command at the prompt:
/usr/local/frontpage/currentversion/bin/owsadm.exe -o check -p all
If Microsoft FrontPage is consistent, the message Check Completed
is displayed, otherwise errors related to the inconsistency are displayed.
For information on restoring a site to its consistent state, see the section on pre-upgrade or post-upgrade requirements.
To review your customizations for compatibility, see Appendix A. Overview of the Parallels Pro Control Panel System Checker. For more information on additional pre-upgrade tasks you might need to perform, also review the section on pre-upgrade or post-upgrade requirements.
If you have configured the installer to obtain the Parallels Pro Control Panel files from a local FTP server, make sure that the installer has access to the specified FTP server. You need to specify the server name or the IP address. The local FTP server must mirror the directory structure on Parallels Pro Control Panel FTP server. For instructions, refer to the document Setting Up a local FTP server to install Parallels Pro Control Panel for Linux at the Parallels Pro Control Panel for Linux Documentation page (http://www.parallels.com/en/pro/docs).