Data Control Tower (DCT) provides V2P support for Oracle, SQL Server, SAP ASE, and supported AppData connectors, enabling users to convert dSources and virtual databases (VDBs) into physical databases for recovery, migration, and operational use cases.

  • Oracle connector

    • Supports in-place conversion of VDBs or pluggable databases (vPDBs) to physical databases on ASM or filesystem storage.

    • V2P leverages underlying engine capabilities such as RMAN-based data transfer and snapshot/timeflow selection for recovery.

    • Used for disaster recovery, migration, and production restoration scenarios.

    • For more information, read Perform Virtual to Physical operation on Oracle in DCT.

  • SQL Server connector

    • Supports V2P export of virtual databases to physical storage in a target environment via DCT UI or automation workflows.

    • Post‑operation steps such as database recovery may be performed automatically or manually, depending on configuration.

    • For more information, read Perform Virtual to Physical (V2P) operation on SQL Server VDB in DCT.

  • SAP ASE connector

    • Enables V2P on dSources and VDBs through a guided workflow in DCT.

    • Users select a provision point, target environment, and configuration parameters before initiating export.

    • Supports optional recovery execution after data transfer to bring the physical database online.

    • For more information, read Perform V2P on an SAP ASE dSource or VDB in DCT.

AppData connector V2P

Supported AppData connector plugins can expose connector-specific settings in the V2P wizard. The wizard displays a V2P Parameters step when the plugin declares virtualToPhysicalDefinition and supports dvp version 5.1.0 or later.

The V2P Parameters step is generated from the connector plugin schema. The Source Config Parameters section is generated from sourceConfigSchema. Field labels and types vary by connector. Connectors without the required schema continue to use the existing static target directory flow.

Prerequisites

  • Use a connector plugin that supports dvp version 5.1.0 or later and declares virtualToPhysicalDefinition.

  • Register the target physical host as an environment in DCT with the required environment user and credentials.

  • For VDB exports, verify that you have the Export permission. For dSource exports, contact your DCT administrator to confirm the required permission because the DCT permissions reference does not list a separate dSource V2P permission.

Procedure

  1. Open the AppData VDB or dSource that you want to export.

  2. Click Actions > Virtual to Physical.

  3. Complete the Physical Database, Data State, and Target Configuration steps.

  4. Complete the V2P Parameters step. Enter the connector-specific target host fields and any required source configuration parameters.

  5. Review the dynamic values in the Summary step and submit the operation.

  6. Monitor the V2P operation from the Operations page (Administration > Operations).

  7. After the operation completes, verify that the physical database is running on the configured port or target configuration.

 

Last updated
Oct 8, 2026