Delphix architecture with Db2

This topic describes the high-level process for adding Db2 environments, linking Db2 instances to the Delphix Engine, and provisioning virtual databases.

Delphix uses a Standby server called “Staging” to support the data ingestion process. There are multiple benefits of having a Staging server between the Db2 Source Instances and the Delphix Dynamic Data Platform:

Allows the database instances to stay in sync with the source database, so end users can create or update their virtual databases as needed. The Delphix Engine snapshots the Staging server and the snapshots can be provisioned out to one or more target servers.
Supports multiple ways of ingesting data, via HADR, Backups, Archive Logs, and Staging Push.
In the case of the Staging Push feature, the user will control the restore and roll forward of the staging database.
Prevents the end-users and their related processes to be connected to the primary database instances, making the architecture more secure and reducing primary databases' potential point of failure and performance degradation.
In the case of Database Partitioning Feature (DPF), the staging and target environments will be single-node environments and all the portions on the source (logical and physical) will be converted to logical partitions on a single host.

Database partitioning feature architecture

The snapshot and provision process occurs on the instance level; all databases that exist on the standby server will be provisioned out to the target machines. Similarly, actions such as bookmark, rewind, and refresh will simultaneously apply to all the databases in the instance.