The steps required to upgrade Oracle VM Manager are provided in this section. Major changes to Oracle VM Manager that improve performance, stability and enhance usability, require that you read this section thoroughly before you proceed with an upgrade.
When upgrading from a release prior to Oracle VM Manager 3.3.1, the upgrade process deletes any existing job or event history prior to upgrade. This is due to a redesign of the job and event models within Oracle VM Manager that greatly improves performance. There is no way to access your job or event history after an upgrade.
This upgrade requirement raises a number of important points that you should be aware of before proceeding:
Perform a full backup of your Oracle VM Manager database and configuration file before performing any upgrade steps described here. See Backing Up The Oracle VM Manager Configuration File for information on backing up Oracle VM Manager.
If necessary, set the location for storing backups of the local MySQL database for Oracle VM Manager to the default path before you attempt to upgrade Oracle VM Manager. Ensure that the default path is configured until the upgrade completes successfully. See Backing up the MySQL Database Repository for information on default paths and procedures.
Environments with large job and event histories take a long time to process before the upgrade process can complete. Therefore, it is important that you take this into account when you plan your upgrade. You may need to set aside a few days to complete an upgrade for a very large deployment that includes numerous servers and virtual machines.
During the actual upgrade process it is very important that no jobs are triggered using the Oracle VM Manager Web Interface, the Oracle VM Manager Command Line Interface or the Oracle VM Web Services API. In the case that a job is triggered during the upgrade process, the upgrade may abort. In this situation, you must check that all jobs are complete and then attempt to run the upgrade script again.
If necessary, set the umask default on Oracle VM Manager to
0022before you begin the upgrade process. If umask is set to another value, it can cause the upgrade process to end unexpectedly.
It is absolutely critical that before you upgrade Oracle VM Manager you make sure that you meet the minimum system requirements described in Section 3.2.1, “Hardware Requirements”. Since Oracle VM Manager 3.3 differs from previous releases, in that it requires that its database is hosted locally, it is possible that a system hosting a previous release of Oracle VM Manager does not meet the requirements for this release. Check the minimum hardware requirements and upgrade system hardware, if required. Remember that if you increase the RAM available to your system, you should also increase the amount of swap space available. General guidelines for this vary, but a rough rule for this is to set the swap space to an equivalent of the amount of physical RAM on your system once you pass the 8 GB mark.
Ensure that no other Linux users have access to the Oracle VM Manager host and that any monitoring services are disabled during the upgrade process.