Provision a Cassandra virtual database (VDB) to create a writable, space‑efficient copy of Cassandra data from a snapshot. Use this task when you need an isolated Cassandra environment for development, testing, or troubleshooting.

Before you begin

  • A linked Cassandra data source exists
  • A snapshot of the data source is available
  • Target hosts meet Cassandra and connector prerequisites

Steps

  1. Navigate to Data > Data Management > VDBs.
  2. On the VDBs page, select Actions in the top-right corner.

  3. Select Provision VDB.

    Create Empty VDB creates a VDB without any source data — it is an empty HANA database. Provision VDB creates a VDB from an existing dSource or VDB snapshot.

  4. Source

    Select whether to provision from a dSource or a VDB.

    • dSources tab – Select an existing dSource to provision from.
    • VDBs tab – Select an existing VDB to provision from.

    Select the desired source and Select Next.

  5. Provision point

    Select the point in time from which the VDB will be provisioned.

    • Select Provision Point – Choose a snapshot from the timeline.
    • Bookmarks – Choose a named bookmark instead of a snapshot.

    Both flows — provisioning from a dSource or from a VDB — use the same remaining steps. The only difference is the Source step.

    Select Next.

  6. Enter dSource-specific parameters for your configuration.  

    1. DSource Type The type of dSource is based on the type of database restore.

    2. Mount Path The path on the host where Delphix will mount the dSource files via NFS.

    3. Cassandra Staging Cluster Node Count Number of nodes that consists of the Staging Cassandra cluster. Minimum: 3 and Maximum: 9.

    4. IP Address / Hostname of the Staging Cluster IP Address / Hostname of the interface for the Cassandra Staging Cluster (default 127.0.0.1).

    5. Staging Cassandra JMX Port Number Staging Cluster JMX port for the cluster for JMX connection requests. Ports for other nodes will be auto-incremented.

    6. Staging Cassandra CQL Native Port Number Staging Cluster CQL native port where the CQL native transport listens for clients. Ports for other nodes will be auto-incremented.

    7. Staging Cassandra TCP Port Number Staging Cluster TCP port for or Cassandra commands and data. Ports for other nodes will be auto-incremented.

    8. Enable Authentication Mode Option to enable the authentication for the Cassandra Staging Cluster.

    9. Cassandra Username Specify the username to be created for Staging Cassandra Cluster.

    10. Cassandra Password Specify the password to be set for the username created for the Cassandra Staging Cluster.

    11. Global Node Configuration Specify the global node configuration for the Cassandra Staging Cluster.

      1. Cassandra Configuration Filepath Specify the relative path of the configuration file to the Cassandra base installation directory.

      2. File Parameters Specify the additional Cassandra configuration parameters to configure the Cassandra Staging Cluster.

        1. Configuration Parameter Name Cassandra Cluster configuration parameter name.

        2. Configuration Parameter Value Cassandra Cluster configuration parameter value.

      3. YAML Password-Sensitive Parameters Specify the additional sensitive Cassandra configuration parameters to configure the Cassandra Staging Cluster.

        1. Configuration Parameter Name Cassandra Cluster sensitive configuration parameter name.

        2. Configuration Parameter Value Cassandra Cluster sensitive configuration parameter value.

    12. Additional Nodes Adding new nodes to the Cassandra cluster setup on the Target host.

    13. Environment Select the target environment from the drop-down to add the new Cassandra node to the Target cluster.

    14. Environment User Select the target environment user to add the new Cassandra node to the cluster.

    15. IP Address / Hostname of the Additional Node IP Address / Hostname of the interface for the Additional Cassandra Target Cluster Node.

    16. Target Cassandra JMX Port Number of the Additional Node Target Cluster JMX port for the cluster for JMX connection requests. Ports for other nodes will be auto-incremented.

    17. Target Cassandra CQL Native Port Number of the Additional Node Target Cluster CQL native port where the CQL native transport listens for clients. Ports for other nodes will be auto-incremented.

    18. Append Node Configuration Append the existing primary node configuration parameters to additional node configuration.

    19. Node Configuration Provide the specific node configuration for the Cassandra Target Cluster.

    20. Cassandra Configuration Filepath Provide the relative path of the configuration file to the Cassandra base installation directory.

    21. File Parameters Specify the additional Cassandra configuration parameters to configure the Cassandra Staging Cluster.

      1. Configuration Parameter Name Cassandra Cluster configuration parameter name.

      2. Configuration Parameter Value Cassandra Cluster configuration parameter value.

    22. YAML Password-Sensitive Parameters Specify the additional sensitive Cassandra configuration parameters to configure the Cassandra Staging Cluster.

      1. Configuration Parameter Name Cassandra Cluster sensitive configuration parameter name.

      2. Configuration Parameter Value Cassandra Cluster sensitive configuration parameter value.

  7. Select a Target Group for the VDB.

  8. Select the Add Dataset Group icon to add a new group, if necessary.

  9. Select a Snapshot Policy for the VDB.

  10. Select Next.

  11. Select the masking option if you wish to mask this VDB.

  12. Select Next.

  13. Specify any desired hook operations.

  14. Select Next.

  15. Review the Provisioning Configuration and Data Management information.

  16. Select Submit.

During provisioning, the connector validates inputs, cleans stale directories, configures node binaries, starts the target cluster, and flushes the database before making the VDB available.

What’s next

  • Reconfigure the VDB to an earlier snapshot
  • Unconfigure the VDB when it is no longer needed
Last updated
Oct 9, 2026