Installation Guide / Eucalyptus Upgrade |
If your upgrade fails, this topic describes how to downgrade your Eucalyptus cloud to an earlier release.
The upgrade process creates a backup to /var/lib/eucalyptus/upgrade/eucalyptus.backup.TIMESTAMP. For example:
/var/lib/eucalyptus/upgrade/eucalyptus.backup.1326905212
If the upgrade fails and needs to be reverted to your earlier version, you can find your preserved data in this directory.
If the upgrade fails, all changes to the database and configuration files will be rolled back. You can retry the upgrade by following the upgrade instructions in the sections, Shutdown Services and Upgrade Eucalyptus Package Repositories.
If you do not want to continue with the upgrade after a failure, you can downgrade your installation back to the previous version. Note that downgrade instructions are different, depending on whether your Eucalyptus services are co-located or each hosted on their own machine. You will need to perform the downgrade for all services running on a single machine at the same time.
The /var/lib/eucalyptus/db and /var/lib/eucalyptus/keys directories should not be affected by the upgrade. If they have been removed subsequent to the upgrade, you must restore the contents of these directories from your backups before downgrading.
To downgrade from a failed upgrade, perform the tasks listed in the following sections.
Use the yum shell command for the following instructions. This will allow you to perform more complex transactions that are required for the downgrade.
Transaction commands for a combined machine host with CLC, Walrus, CC, and SC:
downgrade eucalyptus downgrade eucalyptus-admin-tools downgrade eucalyptus-axis2c-common downgrade eucalyptus-blockdev-utils downgrade eucalyptus-cluster downgrade eucalyptus-cloud downgrade eucalyptus-common-java downgrade eucalyptus-common-java-libs downgrade eucalyptus-sc downgrade eucalyptus-service-image downgrade eucalyptus-walrus downgrade eucanetd
CLC transaction commands:
downgrade eucalyptus downgrade eucalyptus-admin-tools downgrade eucalyptus-axis2c-common downgrade eucalyptus-blockdev-utils downgrade eucalyptus-cloud downgrade eucalyptus-common-java downgrade eucalyptus-common-java-libs downgrade eucalyptus-service-image downgrade eucanetd
UFS transaction commands:
downgrade eucalyptus downgrade eucalyptus-admin-tools downgrade eucalyptus-cloud downgrade eucalyptus-common-java downgrade eucalyptus-common-java-libs
CC transaction commands:
downgrade eucalyptus downgrade eucalyptus-admin-tools downgrade eucalyptus-cluster downgrade eucanetd
SC transaction commands:
downgrade eucalyptus downgrade eucalyptus-admin-tools downgrade eucalyptus-common-java downgrade eucalyptus-common-java-libs downgrade eucalyptus-sc
Walrus Backend transaction commands:
downgrade eucalyptus downgrade eucalyptus-admin-tools downgrade eucalyptus-common-java downgrade eucalyptus-common-java-libs downgrade eucalyptus-walrus
SAN 3PAR transaction commands:
downgrade eucalyptus-enterprise-storage-san-threepar downgrade eucalyptus-enterprise-storage-san-threepar-libs
SAN EqualLogic transaction commands:
downgrade eucalyptus-enterprise-storage-san-equallogic downgrade eucalyptus-enterprise-storage-san-equallogic-libs
SAN NetApp transaction commands:
downgrade eucalyptus-enterprise-storage-san-netapp downgrade eucalyptus-enterprise-storage-san-netapp-libs
In general, there is no need to downgrade Euca2ools.
Whenever you install Euca2ools, it will always give you the latest patch of a release (for example, you'd get 3.4.1 over 3.4.0). If, for example, you have 3.4.1 installed, then performing the following steps would downgrade to 3.4.0.