From 1906a114ecac753435a5a202ceaaa0e5f9160507 Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 26 Jun 2025 16:13:46 +0200 Subject: [PATCH 1/4] fix(rdb): migration index --- .../reference-content/migrating-databases.mdx | 31 +++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 pages/managed-databases-for-postgresql-and-mysql/reference-content/migrating-databases.mdx diff --git a/pages/managed-databases-for-postgresql-and-mysql/reference-content/migrating-databases.mdx b/pages/managed-databases-for-postgresql-and-mysql/reference-content/migrating-databases.mdx new file mode 100644 index 0000000000..a02c71cded --- /dev/null +++ b/pages/managed-databases-for-postgresql-and-mysql/reference-content/migrating-databases.mdx @@ -0,0 +1,31 @@ +--- +meta: + title: Migrating to Scaleway Managed Databases for PostgreSQL and MySQL + description: Learn how to migrate your PostgreSQL and MySQL databases to Scaleway Managed Databases for improved performance and scalability +content: + h1: Migrating to Scaleway Managed Databases for PostgreSQL and MySQL + paragraph: Discover the benefits of migrating your PostgreSQL and MySQL databases to Scaleway Managed Databases and get step-by-step guidance on the migration process +tags: databases postgresql mysql migration managed-databases +dates: + validation: 2025-06-26 +categories: + - managed-databases +--- + +Scaleway Managed Databases allows you to run your Database Instances without setting up or managing infrastructure. Scaleway is responsible for implementing and maintaining features that improve the performance, scalability, security and high-availability of your Database Instances. + +If you have a self-managed database instance, or you use a different cloud provider, you can easily migrate your databases to Scaleway. + +Different factors, such as the size of your databases and your application use-case, can determine the best migration method. Below is a list of the different migration methods and their benefits, as well as a link to each of the tutorials that show you how to carry out your method of choice. + +| Database size | Downtime tolerance | Engine | Recommended migration method | Benefits | +| --- | --- | --- | --- | --- | +| < 100GB | Can afford downtime | PostgreSQL | [Dump/restore from local machine](/managed-databases-for-postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases/#using-pgadmin) | Easy, straightforward | +| > 100GB | Can afford downtime | MySQL and PostgreSQL | [Dump/restore from a Scaleway Instance](/tutorials/migrate-databases-instance/) | Avoids local storage and bandwidth bottlenecks | +| Any size | Cannot afford downtime | PostgreSQL | [Set up logical replication](/managed-databases-for-postgresql-and-mysql/api-cli/logical-replication-as-subscriber/) | Zero downtime, real-time data sync, flexible migration windows, easy rollback. Refer to the official PostgreSQL documentation for a list of [logical replication restrictions](https://www.postgresql.org/docs/16/logical-replication-restrictions.html) | + + + + + + From 39f55890675314bda392bf0993586ca2cf8efaba Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 26 Jun 2025 16:15:08 +0200 Subject: [PATCH 2/4] fix(rdb): add to menu --- menu/navigation.json | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/menu/navigation.json b/menu/navigation.json index 966f828ffd..0765b75a7c 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -2204,13 +2204,17 @@ "label": "PostgreSQL extensions reference", "slug": "postgresql-extensions" }, + { + "label": "Understanding the autohealing feature", + "slug": "autohealing" + }, { "label": "Encryption at rest performance benchmark", "slug": "encryption-at-rest-performance-benchmark" }, { - "label": "Understanding the autohealing feature", - "slug": "autohealing" + "label": "Migrating to Scaleway Managed Databases", + "slug": "migrating-databases" }, { "label": "PostgreSQL version updates", From cf67357b3dbe483f86cef8b38e355c027428f3fd Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Thu, 26 Jun 2025 16:58:16 +0200 Subject: [PATCH 3/4] fix(rdb): add to menu --- menu/navigation.json | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/menu/navigation.json b/menu/navigation.json index 0765b75a7c..d3a40972f5 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -2204,14 +2204,6 @@ "label": "PostgreSQL extensions reference", "slug": "postgresql-extensions" }, - { - "label": "Understanding the autohealing feature", - "slug": "autohealing" - }, - { - "label": "Encryption at rest performance benchmark", - "slug": "encryption-at-rest-performance-benchmark" - }, { "label": "Migrating to Scaleway Managed Databases", "slug": "migrating-databases" @@ -2219,6 +2211,14 @@ { "label": "PostgreSQL version updates", "slug": "pg-version-updates" + }, + { + "label": "Encryption at rest performance benchmark", + "slug": "encryption-at-rest-performance-benchmark" + }, + { + "label": "Understanding the autohealing feature", + "slug": "autohealing" } ], "label": "Additional Content", From ceebf7645de534c737a84b489bdf44c96f49a59c Mon Sep 17 00:00:00 2001 From: ldecarvalho-doc <82805470+ldecarvalho-doc@users.noreply.github.com> Date: Mon, 30 Jun 2025 13:31:12 +0200 Subject: [PATCH 4/4] fix(mdb): review ro --- .../reference-content/migrating-databases.mdx | 6 ------ 1 file changed, 6 deletions(-) diff --git a/pages/managed-databases-for-postgresql-and-mysql/reference-content/migrating-databases.mdx b/pages/managed-databases-for-postgresql-and-mysql/reference-content/migrating-databases.mdx index a02c71cded..a3c88fc374 100644 --- a/pages/managed-databases-for-postgresql-and-mysql/reference-content/migrating-databases.mdx +++ b/pages/managed-databases-for-postgresql-and-mysql/reference-content/migrating-databases.mdx @@ -23,9 +23,3 @@ Different factors, such as the size of your databases and your application use-c | < 100GB | Can afford downtime | PostgreSQL | [Dump/restore from local machine](/managed-databases-for-postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases/#using-pgadmin) | Easy, straightforward | | > 100GB | Can afford downtime | MySQL and PostgreSQL | [Dump/restore from a Scaleway Instance](/tutorials/migrate-databases-instance/) | Avoids local storage and bandwidth bottlenecks | | Any size | Cannot afford downtime | PostgreSQL | [Set up logical replication](/managed-databases-for-postgresql-and-mysql/api-cli/logical-replication-as-subscriber/) | Zero downtime, real-time data sync, flexible migration windows, easy rollback. Refer to the official PostgreSQL documentation for a list of [logical replication restrictions](https://www.postgresql.org/docs/16/logical-replication-restrictions.html) | - - - - - -