Help Center/ Cloud Bastion Host/ FAQs/ About Backup, Specification Change, and Upgrade/ What Are Precautions for Version Upgrade?
Updated on 2024-09-24 GMT+08:00
View PDF
Share

What Are Precautions for Version Upgrade?

If a new version of the CBH system is available, upgrade your CBH system to use the optimized or new system functions. For details, see Upgrading the Version of a CBH System.

Upgrading the CBH system version is free. Ensure that you are fully aware of the following impacts when you plan to upgrade the CBH system version:

  • Before the upgrade
  • During the upgrade

    The version upgrade takes about 30 minutes. Although the CBH system is unavailable during this period, there is no impacts on host resources managed on the instance. However, to prevent important data loss, do not log in to the CBH system during the version upgrade.

  • After the upgrade

    The CBH instance automatically restarts after the upgrade completes. You can then use the mapped CBH system.

    After the upgrade, you can use the configuration and storage data of the original CBH system. Version upgrading does not affect the original configuration and storage data of the CBH system.

  • Rolling Back the Upgrade

    After the version upgrade is complete or during the cross-version upgrade, you can roll back the upgrade on the bastion host details page. After the rollback starts, the status of the bastion host changes to Rolling back edition.

    After the rollback, the basion host will restore to what it is before the upgrade. Data changes and new data will be lost as the basion host will be interrupted during the rollback. Exercise caution when performing this operation.
    • If you plan a scale-out task after an upgrade, start the scale-out task 5 minutes later when the upgrade is finished.
    • A scheduled upgrade must be set at least one day before the actual upgrade time. You are advised to upgrade the service during idle hours.
    • To upgrade the service to the latest version, version 3.3.37.0 and earlier must be upgraded to 3.3.37.5 first, and versions 3.3.38.0 to 3.3.50.0 must be upgraded to 3.3.50.3 first.
    • Manual rollbacks cannot be performed during a minor version upgrade (upgrading version 3.3.37.0 or earlier to 3.3.37.5, or upgrading any version between 3.3.38.0 and 3.5.50.0 to 3.3.50.3).
    • If a scheduled upgrade is set, you cannot shut down, restart, change, or expand the capacity of the basion host.
    • Before the upgrade starts, you can cancel the scheduled upgrade and reset the upgrade time.
    • During the cross-version upgrade, you can manually roll back the version.
    • There is a seven-day retention period for cross-version upgrades. You can roll back a cross-version upgrade within seven days after the upgrade. No rollbacks are allowed once the retention period expires. So, you need to verify the upgrade in a timely manner.
    • If specification change or scale-out tasks are performed after an upgrade, no rollbacks can be performed. So, do not perform any specification change or scale-out operations until you verify the upgrade.
    • After a successful cross-version upgrade, the instance ID, server ID, instance version, and creation time will change.
    • During cross-version upgrade, ports 80, 8080, 443, and 2222 are automatically enabled for the instance. If you do not need to use these ports, disable them immediately after the upgrade.
    • During cross-version upgrade, ports 22, 31036, 31679, and 31873 are automatically enabled for the instance. After the upgrade, keep prot 31679 enabled and disable other ports immediately if you do not need to use them.
    • If a web certificate has been imported for an instance, import the certificate again after the cross-version upgrade for the instance.