From 9c955b258fe84cbeb1d4c4e546dd52604a890dc4 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Tue, 1 Apr 2025 17:18:43 +0200 Subject: [PATCH 1/6] fix(rdb): update upgrade eng version --- .../how-to/upgrade-version.mdx | 31 +++++++++++++++++-- 1 file changed, 28 insertions(+), 3 deletions(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx index ef71083c5d..8df7828056 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx @@ -32,6 +32,30 @@ The version upgrade is only available for: - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [PostgreSQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) running on an outdated engine version +## How to remove incompatible data types + +Before upgrading to a major PostgreSQL version, you must remove any data types incompatible with `pg_upgrade`. + +The `reg*` data type, for example, cannot be persisted by `pg_upgrade`. + +Run the following command in your Database Instance to remove all instances of the `reg*` data type: + +```sql +SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalog.pg_attribute a + WHERE c.oid = a.attrelid + AND NOT a.attisdropped + AND a.atttypid IN ('pg_catalog.regproc'::pg_catalog.regtype, + 'pg_catalog.regprocedure'::pg_catalog.regtype, + 'pg_catalog.regoper'::pg_catalog.regtype, + 'pg_catalog.regoperator'::pg_catalog.regtype, + 'pg_catalog.regconfig'::pg_catalog.regtype, + 'pg_catalog.regdictionary'::pg_catalog.regtype) + AND c.relnamespace = n.oid + AND n.nspname NOT IN ('pg_catalog', 'information_schema');  +``` + +## How to upgrade the engine version + 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the name of the database whose engine you want to upgrade. The Database Instance information page appears. 3. Click **Upgrade** under **Database engine**. A pop-up appears. @@ -40,9 +64,10 @@ The version upgrade is only available for: - **Upgrade only**: This method has no impact on your original Database Instance. Your Database Instance will remain available with its original endpoint and will continue to be billed. - **Upgrade and switch incoming traffic**: With this method, your endpoint is migrated to the new Database Instance automatically. This option will create a clone of your Database Instance, and will automatically migrate the endpoint to the new Instance. The original Database Instance remains available and will continue to be billed. The endpoint will be deleted from the original Database Instance. - - When you upgrade to a new version, there is no synchronization between the source and target Database Instances. To avoid data loss, we recommend you stop any write operations running on your applications during the upgrade. If you let them run during the process, the data will be stored only in the source Database Instance. + When you upgrade to a new version: + - There is no synchronization between the source and target Database Instances. To avoid data loss, we recommend you stop any write operations running on your applications during the upgrade. If you let them run during the process, the data will be stored only in the source Database Instance. + - Your Database Instances in [High Availability (HA)](/managed-databases-for-postgresql-and-mysql/concepts/#high-availability) mode will migrate to a standalone Instance. To maintain your HA mode, you must manually [activate HA]() after the upgrade is complete. @@ -56,7 +81,7 @@ The version upgrade is only available for: 4. Click **Upgrade version**. A new Database Instance is created. - On PostgreSQL, engine extensions are handled and upgraded automatically during the upgrade process. + In PostgreSQL major upgrades the `pgaudit` and `pg_stat_statements` [engine extensions](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) will be removed. You must reinstall these extensions once the upgrade is complete. From 211def85cf0ceefb828320977f06719899188383 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Wed, 2 Apr 2025 09:42:17 +0200 Subject: [PATCH 2/6] fix(rdb): update upgrade eng version2 --- .../how-to/upgrade-version.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx index 8df7828056..46569f247d 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx @@ -56,6 +56,10 @@ SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalo ## How to upgrade the engine version + + Before updating your endpoint, we recommend running a dry-run of the Database Instance upgrade to validate the process. + + 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the name of the database whose engine you want to upgrade. The Database Instance information page appears. 3. Click **Upgrade** under **Database engine**. A pop-up appears. @@ -85,3 +89,4 @@ SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalo +[ \ No newline at end of file From cc59901e94e224b7a437aa2ba9cfebe03ed7f132 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Wed, 2 Apr 2025 11:45:13 +0200 Subject: [PATCH 3/6] fix(rdb): ad ha page --- menu/navigation.json | 4 ++ .../how-to/enable-high-availability.mdx | 43 +++++++++++++++++++ .../how-to/upgrade-version.mdx | 23 ++++------ 3 files changed, 55 insertions(+), 15 deletions(-) create mode 100644 pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx diff --git a/menu/navigation.json b/menu/navigation.json index f27cefda92..0b145bf717 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -2301,6 +2301,10 @@ "label": "Upgrade Database Instance engine version", "slug": "upgrade-version" }, + { + "label": "Enable High Availability", + "slug": "enable-high-availability" + }, { "label": "Apply scheduled maintenance", "slug": "apply-maintenance" diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx new file mode 100644 index 0000000000..bc039be6e2 --- /dev/null +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx @@ -0,0 +1,43 @@ +--- +meta: + title: How to enable High Availability + description: Learn how to switch a standalone node to high availability mode for your Database Instance. +content: + h1: How to enable High Availability + paragraph: Step-by-step instructions for converting a standalone node to high availability mode. +tags: managed-database high-availability node-configuration database-instance +dates: + validation: 2025-04-02 + posted: 2025-04-02 +categories: + - managed-databases + - database-instance-management +--- + +You define your Database Instance's node configuration upon its [creation](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database). Two node configuration modes are available with PostgreSQL or MySQL Database Instances. + +- **High Availability**: creates a secondary Instance with an up-to-date replica of the database. If the primary Instance fails, the secondary takes over requests. +- **Standalone**: a standalone database provisioned on a single node. + +If you are standalone mode, you change the node configuration to High Availability in the console anytime. + + + Once you upgrade to the High Availability mode, you cannot revert to standalone. + + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) in standalone mode. + +1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. +2. Click the name of the Database Instance you want to configure. Your database's Overview page displays. +3. Scroll down to the **Node settings** section. Then, click **Activate High Availability**. +4. Review the new estimated cost. +5. Click **Activate** to do so. + + + The action of changing the node configuration will perform a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several tens of seconds. + + diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx index 46569f247d..688840f308 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx @@ -17,7 +17,7 @@ categories: If your database engine is outdated, you can upgrade the version to the latest one anytime via the Scaleway console. -You must upgrade your engine version if your Database Instance uses an End of Life engine version that is no longer maintained. + You must upgrade your engine version if your Database Instance uses an End of Life engine version that is no longer maintained. @@ -56,10 +56,6 @@ SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalo ## How to upgrade the engine version - - Before updating your endpoint, we recommend running a dry-run of the Database Instance upgrade to validate the process. - - 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the name of the database whose engine you want to upgrade. The Database Instance information page appears. 3. Click **Upgrade** under **Database engine**. A pop-up appears. @@ -71,22 +67,19 @@ SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalo When you upgrade to a new version: - There is no synchronization between the source and target Database Instances. To avoid data loss, we recommend you stop any write operations running on your applications during the upgrade. If you let them run during the process, the data will be stored only in the source Database Instance. - - Your Database Instances in [High Availability (HA)](/managed-databases-for-postgresql-and-mysql/concepts/#high-availability) mode will migrate to a standalone Instance. To maintain your HA mode, you must manually [activate HA]() after the upgrade is complete. - - - - When you upgrade to a new version, Database Instance advanced settings are synced as far as they are still available on the new database engine version. + - Your Database Instances in [High Availability (HA)](/managed-databases-for-postgresql-and-mysql/concepts/#high-availability) mode will migrate to a standalone Instance. To maintain your HA mode, you must manually [enable HA](/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability) after the upgrade is complete. + - Database Instance [advanced settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) are synced as far as they are still available on the new database engine version. - - Follow the [migrating endpoints via the CLI](/managed-databases-for-postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to quickly migrate your endpoints. You can use this procedure to revert the migration anytime.

+ + Follow the [migrating endpoints via the CLI](/managed-databases-for-postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to quickly migrate your endpoints. Before doing so, we recommend running a dry-run of the Database Instance upgrade to validate the process.

+ You can use the same CLI command to revert the endpoint migration anytime.

Keep in mind that reverting the endpoint will not affect the data stored on the databases. This means that if some entries were added to the upgraded database, they will not be added back to the old version when you change the endpoints. 4. Click **Upgrade version**. A new Database Instance is created. - In PostgreSQL major upgrades the `pgaudit` and `pg_stat_statements` [engine extensions](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) will be removed. You must reinstall these extensions once the upgrade is complete. + - In PostgreSQL major upgrades the `pgaudit` and `pg_stat_statements` [engine extensions](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) will be removed. You must reinstall these extensions once the upgrade is complete. + - If you are upgrading to PG16, we recommend you to [reset your user passwords](/managed-databases-for-postgresql-and-mysql/how-to/add-users) from the console or using `psql`, [PostrgreSQL's CLI](https://docs.postgresql.fr/13/app-psql.html). You must create a new password that follows the **SCRAM-SHA-256** format. The previous versions' password format is no longer supported in PG16. - -[ \ No newline at end of file From 6baa137c8f8b7ce19660f1320d3575fd6eb3c6aa Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Wed, 2 Apr 2025 14:56:43 +0200 Subject: [PATCH 4/6] fix(rdb): review team Co-authored-by: Benedikt Rollik Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- .../how-to/enable-high-availability.mdx | 6 +++--- .../how-to/upgrade-version.mdx | 8 ++++---- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx index bc039be6e2..a17aa6c6de 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability.mdx @@ -19,7 +19,7 @@ You define your Database Instance's node configuration upon its [creation](/mana - **High Availability**: creates a secondary Instance with an up-to-date replica of the database. If the primary Instance fails, the secondary takes over requests. - **Standalone**: a standalone database provisioned on a single node. -If you are standalone mode, you change the node configuration to High Availability in the console anytime. +If you are standalone mode, you can change the node configuration to High Availability in the console anytime. Once you upgrade to the High Availability mode, you cannot revert to standalone. @@ -32,10 +32,10 @@ If you are standalone mode, you change the node configuration to High Availabili - A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) in standalone mode. 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. -2. Click the name of the Database Instance you want to configure. Your database's Overview page displays. +2. Click the name of the Database Instance you want to configure. Your database's **Overview** page displays. 3. Scroll down to the **Node settings** section. Then, click **Activate High Availability**. 4. Review the new estimated cost. -5. Click **Activate** to do so. +5. Click **Activate**. The action of changing the node configuration will perform a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several tens of seconds. diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx index 688840f308..610e18a311 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx @@ -34,7 +34,7 @@ The version upgrade is only available for: ## How to remove incompatible data types -Before upgrading to a major PostgreSQL version, you must remove any data types incompatible with `pg_upgrade`. +Before upgrading to a newer major PostgreSQL version, you must remove any data types incompatible with `pg_upgrade`. The `reg*` data type, for example, cannot be persisted by `pg_upgrade`. @@ -68,7 +68,7 @@ SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalo When you upgrade to a new version: - There is no synchronization between the source and target Database Instances. To avoid data loss, we recommend you stop any write operations running on your applications during the upgrade. If you let them run during the process, the data will be stored only in the source Database Instance. - Your Database Instances in [High Availability (HA)](/managed-databases-for-postgresql-and-mysql/concepts/#high-availability) mode will migrate to a standalone Instance. To maintain your HA mode, you must manually [enable HA](/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability) after the upgrade is complete. - - Database Instance [advanced settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) are synced as far as they are still available on the new database engine version. + - Database Instance [advanced settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) are synced as long as they are still available on the new database engine version. @@ -79,7 +79,7 @@ SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalo 4. Click **Upgrade version**. A new Database Instance is created. - - In PostgreSQL major upgrades the `pgaudit` and `pg_stat_statements` [engine extensions](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) will be removed. You must reinstall these extensions once the upgrade is complete. - - If you are upgrading to PG16, we recommend you to [reset your user passwords](/managed-databases-for-postgresql-and-mysql/how-to/add-users) from the console or using `psql`, [PostrgreSQL's CLI](https://docs.postgresql.fr/13/app-psql.html). You must create a new password that follows the **SCRAM-SHA-256** format. The previous versions' password format is no longer supported in PG16. + - In PostgreSQL major upgrades, the `pgaudit` and `pg_stat_statements` [engine extensions](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) will be removed. You must reinstall these extensions once the upgrade is complete. + - If you are upgrading to PG16, we recommend you [reset your user passwords](/managed-databases-for-postgresql-and-mysql/how-to/add-users) from the console or using `psql`, [PostrgreSQL's CLI](https://docs.postgresql.fr/13/app-psql.html). You must create a new password that follows the **SCRAM-SHA-256** format. The previous versions' password format is no longer supported in PG16. From 78e10c265e94bfc1f7a49ac202c685b8414ce286 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Wed, 9 Apr 2025 14:26:08 +0200 Subject: [PATCH 5/6] fix(rdb): review hugo --- .../how-to/upgrade-version.mdx | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx index 610e18a311..bcef8a1a69 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx @@ -34,11 +34,11 @@ The version upgrade is only available for: ## How to remove incompatible data types -Before upgrading to a newer major PostgreSQL version, you must remove any data types incompatible with `pg_upgrade`. +Before upgrading to a newer major PostgreSQL version, you must remove any data types incompatible with the `pg_upgrade` tool. The `reg*` data type, for example, cannot be persisted by `pg_upgrade`. -Run the following command in your Database Instance to remove all instances of the `reg*` data type: +Run the following command in your Database Instance to identify all instances of the `reg*` data type: ```sql SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalog.pg_attribute a @@ -54,6 +54,8 @@ SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalo AND n.nspname NOT IN ('pg_catalog', 'information_schema');  ``` +We recommend you remove the identified instances before continuing. + ## How to upgrade the engine version 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. @@ -67,19 +69,19 @@ SELECT count(*) FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n, pg_catalo When you upgrade to a new version: - There is no synchronization between the source and target Database Instances. To avoid data loss, we recommend you stop any write operations running on your applications during the upgrade. If you let them run during the process, the data will be stored only in the source Database Instance. - - Your Database Instances in [High Availability (HA)](/managed-databases-for-postgresql-and-mysql/concepts/#high-availability) mode will migrate to a standalone Instance. To maintain your HA mode, you must manually [enable HA](/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability) after the upgrade is complete. + - Your Database Instances in [High Availability (HA)](/managed-databases-for-postgresql-and-mysql/concepts/#high-availability) mode will migrate to a standalone Instance. To maintain your HA mode, you must manually [enable HA](/managed-databases-for-postgresql-and-mysql/how-to/enable-high-availability) after the upgrade is complete. The same applies when upgrading [Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica). - Database Instance [advanced settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) are synced as long as they are still available on the new database engine version. - Follow the [migrating endpoints via the CLI](/managed-databases-for-postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to quickly migrate your endpoints. Before doing so, we recommend running a dry-run of the Database Instance upgrade to validate the process.

- You can use the same CLI command to revert the endpoint migration anytime.

- Keep in mind that reverting the endpoint will not affect the data stored on the databases. This means that if some entries were added to the upgraded database, they will not be added back to the old version when you change the endpoints. + Before performing an engine upgrade migration, we recommend testing the process in a "dry-run". This allows you to estimate the migration time and verify its success without affecting your source instance. To do so: + - Run the migration without checking the "migration endpoint" flag. This will simulate the migration process. If the test is successful, you can then proceed with the actual migration. Follow the [migrating endpoints via the CLI](/managed-databases-for-postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to migrate your endpoints after the upgrade. You can use the same CLI command to revert the endpoint migration anytime. + - Keep in mind that reverting the endpoint will not affect the data stored on the databases. This means that if some entries were added to the upgraded database, they will not be added back to the old version when you change the endpoints. 4. Click **Upgrade version**. A new Database Instance is created. - - In PostgreSQL major upgrades, the `pgaudit` and `pg_stat_statements` [engine extensions](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) will be removed. You must reinstall these extensions once the upgrade is complete. - - If you are upgrading to PG16, we recommend you [reset your user passwords](/managed-databases-for-postgresql-and-mysql/how-to/add-users) from the console or using `psql`, [PostrgreSQL's CLI](https://docs.postgresql.fr/13/app-psql.html). You must create a new password that follows the **SCRAM-SHA-256** format. The previous versions' password format is no longer supported in PG16. + - In PostgreSQL major upgrades, the `pgaudit` and `pg_stat_statements` [engine extensions](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) will be removed. You must reinstall these extensions on each database they are installed once the upgrade is complete. + - If you are upgrading to PG16, we recommend you [reset your user passwords](/managed-databases-for-postgresql-and-mysql/how-to/add-users) from the console or using `psql`, [PostrgreSQL's CLI](https://www.postgresql.org/docs/current/app-psql.html#APP-PSQL-META-COMMAND-PASSWORD). PG16 uses the **SCRAM-SHA-256** format to store passwords. The previous versions' password format is no longer supported in PG16. You can re-save your passwords after the upgrade and they will be stored in the correct format automatically. From 3eae032cf0a383708a271852819de2a23d30ba3b Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Wed, 9 Apr 2025 14:58:46 +0200 Subject: [PATCH 6/6] fix(rdb): review hugo2 --- .../how-to/upgrade-version.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx index bcef8a1a69..13b3b724d4 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version.mdx @@ -75,7 +75,7 @@ We recommend you remove the identified instances before continuing. Before performing an engine upgrade migration, we recommend testing the process in a "dry-run". This allows you to estimate the migration time and verify its success without affecting your source instance. To do so: - - Run the migration without checking the "migration endpoint" flag. This will simulate the migration process. If the test is successful, you can then proceed with the actual migration. Follow the [migrating endpoints via the CLI](/managed-databases-for-postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to migrate your endpoints after the upgrade. You can use the same CLI command to revert the endpoint migration anytime. + - Run the migration without checking the "migration endpoint" flag. If the test is successful, you can then proceed with the actual migration. Follow the [migrating endpoints via the CLI](/managed-databases-for-postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to migrate your endpoints after the upgrade. You can use the same CLI command to revert the endpoint migration anytime. - Keep in mind that reverting the endpoint will not affect the data stored on the databases. This means that if some entries were added to the upgraded database, they will not be added back to the old version when you change the endpoints. 4. Click **Upgrade version**. A new Database Instance is created.