A.0 Restoring Cloud Manager Application Server in the Event of a System Failure

To restore Cloud Manager Application to the previous release:

1. Ensure that all Cloud Manager services are shut down. Use the following command at the Application Server command line:

               /etc/init.d/netiq/cloudmanager clean
             

2. Uninstall the Cloud Manager 2.5 RPM files. Use the following command at the Application Server command line:

               rpm --erase netiq-cloudmanager-2.5 netiq-cloudmanager-lib-2.5
             

3. Install the Cloud Manager 2.4 RPM files. Use the following command at the Application Server command line:

               rpm -Uvh netiq-cloudmanager-2.4.0-<build_number>.noarch.rpm
             

4. Restore the configuration file backup that the configurator collected during the upgrade. Use a command similar to the following:

               ./backup -r -f /var/opt/netiq/cloudmanager/cfg-auto-backup-<old version>-to-<new version>.tar.gz
             

   NOTE:If you chose to perform a complete Cloud Manager file system backup, you would use a command similar to the following:

                 ./backup -r -f /var/opt/netiq/cloudmanager/<full_backup_before_2.5>.tar.gz
               

5. Restore the backup of the PostgreSQL database you used before the upgrade.

   IMPORTANT:The database you have been using with Cloud Manager 2.5 must be clean and the database user must exist for the upgrade to succeed. You might have to drop the existing database, then re-create it before you can revert to the prior database.

   When you are sure that the existing database is clean, use a command like this to restore the former database that you backed up:

                 sudo -u postgres psql -d cloudmanager -f /var/opt/netiq/cloudmanager/cm_database_backup.dump.out
               

6. Start the restored version of Cloud Manager:

               /etc/init.d/netiq/cloudmanager start