Upgrading the Instance Version

Precautions

• Instance version description

  When upgrading versions of some CBH instances, two upgrades may be required. So, check the current version and the upgrade process before you start, as shown in Table 1.

  Table 1 Process of upgrading a bastion host instance to the latest version

  Version In Use	Applicable Process
  3.3.37.0 or earlier	Two upgrades are required. First upgrade (minor version upgrade): Upgrading the current version to 3.3.37.7. Rollback is not allowed during the upgrade. Second upgrade (cross-version upgrade): Upgrading the version from 3.3.37.7 to the latest version.
  3.3.38.0 to 3.3.50.0 (including 3.3.38.0 and 3.3.50.0)	Two upgrades are required. First upgrade (minor version upgrade): Upgrading the current version to 3.3.50.7. Rollback is not allowed during the upgrade. Second upgrade (cross-version upgrade): Upgrading the version from 3.3.50.7 to the latest version.
  3.3.52.0 or later (except the latest version)	(Minor version upgrade) Directly upgrade the current version to the latest version.

• Before the upgrade
  • Back up data to ensure a quick rollback in case of upgrade failure. For details, see Which Types of System Data Can Be Backed Up in the CBH System?
  • For a cross-version upgrade, the start time for a scheduled upgrade must be at least 24 hours later than the current time. You are advised to upgrade the service during idle hours. If a scheduled upgrade is set, you cannot shut down, restart, change, or expand the capacity of the bastion host. Before the upgrade starts, you can cancel the scheduled upgrade and reset the upgrade time.
• During the upgrade
  • The version upgrade takes about 30 minutes. Although the CBH system is unavailable during this period, there is no impact 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 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 will change to Rolling back edition.
• 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.
  • After a cross-version upgrade is successful, the system enters a seven-day rollback retention period (during which the upgrade button is unavailable). If the rollback retention period expires, the rollback cannot be performed. Verify the CBH data after the upgrade.
  • The scale-out after the upgrade cannot be rolled back. If you plan a scale-out task after an upgrade, start the scale-out task 5 minutes later when the upgrade is finished.
  • 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 port 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.
• Version rollback

  After a rollback, the bastion host will restore to what it is before the upgrade. Data changes and new data will be lost as the bastion host will be interrupted during the rollback. Exercise caution when performing this operation.

Constraints

• In the new version of CBH, the application publish function is optimized. After the upgrade, to use the application O&M functions as usual, install the required plug-in on the application publish server as prompted. For details, see Installing RemoteApp Program.
• To upgrade version 3.3.40.0 and 3.3.41.0, synchronize the time of OBS buckets first.
• In the current version, hitless upgrade is not supported for all instances. During the upgrade, services need to be suspended.

Prerequisites

The CBH system data has been backed up.

Before you upgrade, back up the CBH system data in the event of upgrade failures. For details, see Which Types of System Data Can Be Backed Up in a CBH System?

Procedure

1. Log in to the CBH console.
2. Click in the upper left corner on the displayed page and select a region.
3. In the Version column of the instance list, you can view the current version and upgrade information of the instance.
4. In the row containing the target instance, click Upgrade Schedule in the Version column.
5. In the displayed instance upgrade dialog box, select the scheduled upgrade time and enter YES in the dialog box. Then click OK.
6. Wait for the upgrade to complete. It takes about 15 minutes to 2 hours for the upgrade to finish at the backend. The actual upgrade time varies depending on the upgrade type. Once the upgrade starts, the instance status changes to Upgrading.
   

   Upgrade types:

   • If two upgrades are required, it takes about 15 to 30 minutes to complete the first upgrade. During this period, the bastion host service will be interrupted.
   • During the cross-version upgrade, a new CBH instance will be created, and the CBH instance you are using will be interrupted. It takes about 30 minutes to 2 hours to complete the upgrade. During the cross-version upgrade, the instance status changes to Upgrading first, and then to Migrating data, Configuring HA, and to Running.

7. When the CBH instance status changes to Running, the CBH system is available.

   After the upgrade is complete, view the instance version on the instance list page. If the instance version does not change after the upgrade, the upgrade fails. Contact technical support.

   

   If two upgrades are involved, ensure that the first upgrade is successful and then perform the second upgrade.