This topic describes basic concepts behind the creation of dSources from DB2 instances.
Database Level Operation
DB2 Database Level Support
Delphix operates at the database level and requires that
- The staging and target hosts must have the empty instances created prior to Delphix using them
- The desired OS user to execute commands related to dSource and VDB operation for each instance has been added as an environment user
Note: Make sure staging instance used for linking doesn’t have existing restoring database with the same name.
DB2 for Delphix ingests data by using a staging database created on a discovered Standby instance of DB2. The dSource uses the staging database to stay in sync with the production database. This is done by first going through the linking process during which a full backup is used to recover an initial copy of the production database to the staging database. Storage for the staging database is provided by Delphix via an NFS mount to storage exported by the Delphix system.
A single standby instance can contain data from multiple source databases.
During the linking process, you can optionally set up an HADR connection between the original source databases and copies on the Standby instance. By doing this the Standby instance will always keep its databases in sync with the source databases using HADR for log shipping. It is important to note that a single Standby instance (dSource) can contain multiple databases from multiple different servers and instances as long as each database has a unique name.
In case of standalone staging host we can use resynchronization utility to keep staging database up to date as source database.
Delphix HADR standby configuration may not meet DR requirements and should not be used as such without evaluating your needs.
Virtual Instance (VDB) Provisioning
A VDB is created based off the desired dSource snapshot and is provisioned to the desired instance on a target system. This operation is executed with the desired target system OS environment user.