This topic describes how to provision a VDB from a replicated dSource or VDB through DCT. After replication delivers objects to a target CD engine, DCT surfaces those replicated objects alongside local objects in the unified data management view. The provisioning process is the same as standard VDB provisioning, except that you first select the replica namespace that contains the replicated object.
Prerequisites
You must first do the following:
-
A replication specification has been configured and at least one replication update has completed successfully. Read Replication overview for details.
-
A compatible target environment is registered in DCT and connected to the target CD engine. For connector-specific environment setup, refer to the Ecosystem documentation.
-
If the replicated object depends on a plugin data connector, that plugin must be installed on the target CD engine at a version equal to or higher than the source engine's plugin version. For more information, read CD engine plugin management.
Procedure
-
In DCT, navigate to Data > Data Management > VDBs.
-
Click Provision VDB and select the target CD engine that received the replica.
-
In the source selection step, choose the replica namespace that contains the replicated dSource or VDB.
-
Select the dSource or VDB within the replica, then choose a snapshot or point-in-time to provision from.
-
Complete the remaining provisioning steps as you would for any standard VDB. For connector-specific provisioning details, refer to the Ecosystem documentation.
Post-provisioning
Once the provisioning job starts, DCT displays the new VDB in the Data > Data Management > VDBs list. The VDB is fully functional and can be managed through DCT like any other VDB, including refresh, rewind, snapshot, and bookmark operations.