From d123bae6d55aa1d8db26345b7321eb4580b5cf7c Mon Sep 17 00:00:00 2001 From: Harshini Rangaswamy Date: Tue, 15 Oct 2024 16:29:08 +0200 Subject: [PATCH 1/4] add: Migration from Caching to Valkey --- ...rate-caching-valkey-to-aiven-for-valkey.md | 91 +++++++++++++++++++ sidebars.ts | 7 ++ 2 files changed, 98 insertions(+) create mode 100644 docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md diff --git a/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md b/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md new file mode 100644 index 00000000..717e972c --- /dev/null +++ b/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md @@ -0,0 +1,91 @@ +--- +title: Migrate Aiven for Caching or Valkey to Aiven for Valkey™ +--- +import ConsoleLabel from "@site/src/components/ConsoleIcons" +import ConsoleIcon from "@site/src/components/ConsoleIcons" + +Migrate your Aiven for Caching or Valkey databases to Aiven for Valkey™ using the Aiven Console migration tool. + +## Prerequisites + +Before starting the migration process, ensure the following: + +- A target [Aiven for Valkey service](/docs/products/valkey/get-started). +- Source database details: + - **Hostname or connection string**: The public hostname, connection string, or + IP address used to connect to the database. + - **Port**: The port used to connect to the database. + - **Username**: The username with sufficient permissions to access the data. + - **Password**: The password used to connect to the database. +- Firewall rules updated or temporarily disabled to allow traffic between source and + target databases. +- A source Caching or Valkey service secured with SSL. +- A publicly accessible source Caching or Valkey service or one with a VPC peering + connection between private networks. You'll need the VPC ID and cloud name. + +## Database migration steps + +1. Log in to the [Aiven Console](https://console.aiven.io/) and select the + Aiven for Valkey service for your migration. +1. Go to from the sidebar. +1. Scroll to > **Migrate database** to start the + migration. +1. Follow the wizard to guide you through the migration process. + +### Step 1: Configure + +Review the prerequisites and click **Get started** to begin. + +### Step 2: Validate + +In the migration screen, enter the connection details: + +- Hostname +- Port +- Username +- Password + +Select **SSL encryption recommended** for a secure connection, and click **Run check**. + +The [Aiven Console](https://console.aiven.io/) validates the database configurations. If +any errors occur, follow the on-screen instructions to resolve them and rerun the check. + +:::note +The migration does not include service user accounts or commands in progress. +::: + +### Step 3: Migrate + +Once validation is complete, click **Start migration** to begin migrating data to +Aiven for Valkey. + +### Step 4: Replicate + +While the migration is in progress: + +- You can close the migration wizard and monitor the progress later from the + page. +- To stop the migration, click **Stop migration** in the migration progress window. + Data already transferred to Aiven for Valkey is preserved. + +To prevent conflicts during replication: + +- Do not create or delete databases on the source service. +- Avoid network or configuration changes that might disrupt the connection between source + and target databases, such as firewall modifications. + +If the migration fails, resolve the issue and click **Start over**. + +### Step 5: Close and complete the migration + +After the migration: + +- **Stop replication**: If no further synchronization is needed, and you are ready + to switch to Aiven for Valkey after testing. +- **Keep replicating**:If continuous data synchronization is needed. Avoid system + updates or configuration changes during active replication to prevent unintended + migrations. + +:::note +When replication is active, Aiven for Valkey ensures your data stays in sync by +continuously synchronizing new writes from the source database. diff --git a/sidebars.ts b/sidebars.ts index 40cf1107..2e664625 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -1895,6 +1895,13 @@ const sidebars: SidebarsConfig = { 'products/valkey/howto/connect-java', ], }, + { + type: 'category', + label: 'Data migration', + items: [ + 'products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey', + ], + }, { type: 'category', label: 'Read replica', From a7b496ac1840aec4b1057eda20e17eac4ce321ea Mon Sep 17 00:00:00 2001 From: Harshini Rangaswamy Date: Fri, 25 Oct 2024 10:26:24 +0200 Subject: [PATCH 2/4] fix: spacing --- .../valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md b/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md index 717e972c..c7c37eba 100644 --- a/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md +++ b/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md @@ -82,7 +82,7 @@ After the migration: - **Stop replication**: If no further synchronization is needed, and you are ready to switch to Aiven for Valkey after testing. -- **Keep replicating**:If continuous data synchronization is needed. Avoid system +- **Keep replicating**: If continuous data synchronization is needed. Avoid system updates or configuration changes during active replication to prevent unintended migrations. From 15ab534a9ef29ff71b35d87a6c2916781d9fb8c2 Mon Sep 17 00:00:00 2001 From: Harshini Rangaswamy Date: Fri, 25 Oct 2024 16:25:31 +0200 Subject: [PATCH 3/4] fix: feedback --- .../migrate-caching-valkey-to-aiven-for-valkey.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md b/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md index c7c37eba..5bed294f 100644 --- a/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md +++ b/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md @@ -19,10 +19,15 @@ Before starting the migration process, ensure the following: - **Password**: The password used to connect to the database. - Firewall rules updated or temporarily disabled to allow traffic between source and target databases. -- A source Caching or Valkey service secured with SSL. +- A source Aiven for Caching or Valkey service secured with SSL. - A publicly accessible source Caching or Valkey service or one with a VPC peering connection between private networks. You'll need the VPC ID and cloud name. +:::note +The migration does not include service user accounts or commands in progress. +::: + + ## Database migration steps 1. Log in to the [Aiven Console](https://console.aiven.io/) and select the @@ -34,7 +39,7 @@ Before starting the migration process, ensure the following: ### Step 1: Configure -Review the prerequisites and click **Get started** to begin. +In the migration wizard, review the prerequisites and click **Get started** to begin. ### Step 2: Validate @@ -50,10 +55,6 @@ Select **SSL encryption recommended** for a secure connection, and click **Run c The [Aiven Console](https://console.aiven.io/) validates the database configurations. If any errors occur, follow the on-screen instructions to resolve them and rerun the check. -:::note -The migration does not include service user accounts or commands in progress. -::: - ### Step 3: Migrate Once validation is complete, click **Start migration** to begin migrating data to @@ -78,7 +79,7 @@ If the migration fails, resolve the issue and click **Start over**. ### Step 5: Close and complete the migration -After the migration: +After the migration, select one of the following: - **Stop replication**: If no further synchronization is needed, and you are ready to switch to Aiven for Valkey after testing. From ab1ce2ce6e01c22a020c389cf5d5a9468626c482 Mon Sep 17 00:00:00 2001 From: Harshini Rangaswamy Date: Fri, 25 Oct 2024 16:29:32 +0200 Subject: [PATCH 4/4] fix: feedback --- .../valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md b/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md index 5bed294f..7f664d05 100644 --- a/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md +++ b/docs/products/valkey/howto/migrate-caching-valkey-to-aiven-for-valkey.md @@ -20,7 +20,7 @@ Before starting the migration process, ensure the following: - Firewall rules updated or temporarily disabled to allow traffic between source and target databases. - A source Aiven for Caching or Valkey service secured with SSL. -- A publicly accessible source Caching or Valkey service or one with a VPC peering +- A publicly accessible source Aiven for Caching or Valkey service or one with a VPC peering connection between private networks. You'll need the VPC ID and cloud name. :::note