Migration architecture v1.3

Hybrid Manager (HM) provides a unified platform for migrating databases from various sources to HM-managed and externally managed Postgres clusters. The migration process relies on several key components that work together to handle schema conversion, data transfer, and continuous replication.

From Oracle

Migrations from Oracle are best suited for targeting EDB Postgres Advanced Server clusters (HM-managed or externally managed). Given the differences between the two database systems, these migrations require a specific set of components to handle both schema and data migration, with EDB Postgres Advanced Server being optimized for this purpose.

Oracle database: The source database containing the data and schemas to be migrated.

Agent: A component that connects to the Oracle source to read and extract schemas for migration. Also, registering the source with HM provides a view of the source database in the HM console for migration assessment and to enable schema migration.

DMS agent in reader mode: A component that connects to the Oracle source to read and extract data for migration.

Hybrid Manager (HM): The central control plane.

HM console: The web-based interface where users manage and monitor all migration activities.

Migration Portal: A service in HM that handles Oracle-specific schema assessment, conversion, and import to the destination database, while ensuring compatibility with EDB Postgres Advanced Server. It can also assist with schema-related issues using an AI Copilot.

Data Migration Service (DMS): The core service that performs the actual data transfer (snapshot) and continuous change replication (streaming). It includes a built-in writer for migrations to HM-managed databases.

HM-managed EDB Postgres Advanced Server database: A destination database cluster that's created and managed by HM.

DMS agent in writer mode: A component that you require only when the migration destination database is a self-managed database, external to HM. It consumes CDC records to replicate and apply changes on the destination database.

External EDB Postgres Advanced Server database: An externally managed destination for migrations, also called self-managed databases. This scenario requires an additional DMS agent component in writer mode that you connect to the destination host to receive and apply data.

See Oracle to HM-managed database for an end-to-end example that shows how to perform a migration.

From Postgres

Migrating between Postgres databases is a more streamlined process, as the schema is already compatible. This migration is primarily focused on efficient data transfer and replication and also requires a specific set of components for migration:

External Postgres database: The source Postgres database containing the data to be migrated.

Migration Toolkit or pg_dump: External tools used for the initial schema migration, as the schema itself doesn't require conversion.

Agent: A component that registers the source with HM to provide a view of the source database within the HM console for monitoring.

DMS agent in reader mode: A component that connects to the source Postgres to read and extract data.

Hybrid Manager (HM): The central control plane.

HM console: The web-based interface where users manage and monitor all migration activities.

Data Migration Service (DMS): The core service that performs the actual data transfer (snapshot) and continuous change replication (streaming). It includes a built-in writer for migrations to HM-managed databases.

HM-managed Postgres database: A destination database cluster that's created and managed by HM. It can be PostgreSQL, EDB Postgres Advanced Server, or EDB Postgres Extended Server.

DMS agent in writer mode: A component that you require only when the migration destination database is a self-managed database, external to HM. It consumes CDC records to replicate and apply changes on the destination database.

External Postgres database: An externally managed destination for migrations, also called self-managed databases. This scenario requires an additional DMS agent component in write mode that you connect to the destination host to receive and apply data.

See Self-managed Postgres to HM-managed database for an end-to-end example that shows how to perform a migration.