All documents

FPT MongoDB Enterprise

    Upgrade patch version
    Upgrade patch version
    Updated on 15 May 2026

    The Patch Version Upgrade feature allows users to upgrade their FPT MongoDB Enterprise database cluster from the current patch version to a higher version from the list. Upgrading helps you take advantage of performance, security, and feature improvements in the higher patch version. Currently, this feature does not support downgrading and is only available if your database cluster is not the latest patch version offered.

    Prerequisites

    • Ensure you have IAM permissions to manage and update the database cluster.
    • All applications or services connected to the database should be disconnected.
    • Create a full backup before upgrading so you can recover if needed.
    • Verify that your applications support the target version.

    Detailed instructions

    Step 1: Open the database overview page

    Log in to the FPT Cloud Portal and navigate to Database cluster list. Choose the FPT MongoDB Enterprise cluster that you want to upgrade from your list of clusters. On the cluster’s Overview page, you can see the current version. If this version is not the latest supported patch version, an Upgrade icon will appear next to it to allow for the upgrade.

    Step 2: Upgrade version

    On the Overview page, click the Upgrade icon next to the version information. A dialog opens showing the current version and the target version(s) available.

    Select the target version and enter the confirmation keyword in the input field. Select Upgrade to start the upgrade process.

    During the operation, the database cluster status changes to "Updating". Do not attempt to connect or make changes while the update is in progress. The cluster will automatically restart as part of the upgrade.

    After the upgrade completes successfully, the status returns to “Running”, and the database cluster is upgraded to the new version.

    Important considerations

    • Irreversible: Version upgrades cannot be undone; ensure backups are complete.
    • Disconnect clients: All application connections must be stopped before upgrading.
    • Service impact: The database cluster will be restarted, causing temporary downtime.
    • If the upgrade fails, use a backup to restore the previous state.