Migrate from In-Memory DB v1 to v2
Important:
In-Memory DB v2, powered by Valkey, is now available, bringing Valkey (Redis®-compatible) engines in versions 8, 8.1, and 9. It also adds extended snapshot retention and native IONOS CLOUD Observability integration.
Creation of clusters using In-Memory DB v1 is deprecated through the DCD and only limited operations are supported on legacy clusters.
Creation of v1 clusters through the API will be deprecated as of July 31, 2026.
An automatic migration from v1 to v2 is impossible. You must manually migrate existing v1 clusters to the new v2 infrastructure through the v2 API. For step-by-step instructions, see Manual migration.
Manual migration
You must perform the migration through the In-Memory DB v2 API.
Important: Creation of v1 clusters through the API will be deprecated as of July 31, 2026. Migrate existing clusters to v2 before this date.
Prerequisites:
You must have the contract administrator or owner role, or the Access and manage DBaaS privilege, to manage clusters.
The v2 API requires API token authentication (
tokenAuth). Include a valid token in theAuthorizationheader of every request. For information on generating tokens, see the Authentication API.
1. Create a new In-Memory DB v2 instance using the v2 API. For the API documentation, see In-Memory DB v2 Cloud API.
2. If you want to move data from your v1 instance, migrate it to the new In-Memory DB v2 instance.
3. Update your applications to connect to the new In-Memory DB v2 Endpoints.
Note: Updating your applications to the new endpoint may briefly interrupt connections. Plan for a short cutover window while traffic switches from v1 to v2.
Next steps
Create an In-Memory DB Cluster: Provision your new v2 cluster in the DCD.
FAQ: Common questions about In-Memory DB v1 and v2.
Last updated
Was this helpful?