IMSVA rolls back automatically if there are
problems during the upgrade process. However, if the automatic rollback encounters
issues, you need to perform a manual rollback.
Procedure
- If you created a ghost image or have a virtual machine image of your original IMSVA, replace the upgraded image with the original image.
- Stop the cron service using the following command:
service crond stop - Check the cron settings backup file
/var/spool/cron/root.bakForUpgrade. After finding the file, restore the cron settings using the following command:rm -rf /var/spool/cron/root && /bin/mv -f /var/spool/cron/root.bakForUpgrade /var/spool/cron/root - Check the log backup file
/var/app_data/imss/log.bakForUpgrade. After finding the backup file, restore the log file using the following command:rm -rf /var/app_data/imss/log/ && /bin/mv -f /var/app_data/imss/log.bakForUpgrade /var/app_data/imss/log/ - Stop the database service using the following command:
killall postgres - On the parent device, check the database backup file
/var/app_data/imss/pgdata.bakForUpgrade. After finding the file, restore the database file using the following command:rm -rf /var/app_data/imss/db/pgdata && /bin/mv -f /var/app_data/imss/pgdata.bakForUpgrade /var/app_data/imss/db/pgdata - If not mounted, mount the root partition of IMSVA 9.0 Patch 1 using the following
command:
mkdir -p /var/tmp/orig_rootmount -t ext3 /dev/mapper/IMSVA-Root1 /var/tmp/orig_root - Restore the /boot folder using the following command:
/bin/cp -af /var/tmp/orig_root/boot-imsva-9.0-back-up-for-9.1/* /boot - Update the boot partition UUID.
- Obtain the 9.1 boot partition UUID from
/etc/fstab. - Replace 9.0 Patch 1 boot partition UUID in
/var/tmp/orig_root/etc/fstabwith 9.1 boot partition UUID.
- Obtain the 9.1 boot partition UUID from
- Restart your machine.
