Delphix glossary

This glossary is your guide to exploring Delphix terms and definitions.

Products

Term	Definition
Delphix Continuous Data	Delphix Continuous Data is a Delphix product to deliver data on-demand to application developers and testers. Running as a virtual appliance, it is sometimes referred to as a Data Engine.
Delphix Continuous Data with Elastic Data	Elastic Data is a storage feature of Delphix Continuous Data that allows optimal data management to minimize costs through the use of block and elastic storage.
Delphix Continuous Compliance	Delphix Continuous Compliance is a Delphix product for discovering sensitive data and replacing it with realistic but fictitious data. Running as a virtual appliance, it is sometimes referred to as a Compliance Engine.
Data Control Tower	Data Control Tower (DCT) is a Delphix product that provides a data mesh to unify data governance, automation, and compliance across all applications and cloud platforms.

Interfaces

Term	Definition
Delphix Setup	Delphix Setup is the Delphix Continuous Data's user interface for system administrators to configure their engine settings, such as storage, support bundle, authentication, and network configurations.
Delphix Management	Delphix Management is Delphix Continuous Data's user interface for product administrators to manage their virtualized or masked datasets.
Delphix Self-Service	Delphix Self-Service is the Delphix Continuous Data user interface designed specifically for project teams, application developers, and testers to manage their virtualized datasets.
Command Line Interface (CLI)	Command Line Interface (CLI) is the engine's terminal interface which allows users to perform various administrative commands. This is not to be confused with the `dxtoolkit`.
Delphix Download Portal	Delphix Download Portal is the location where users download Delphix's products.
Delphix Support Portal	Delphix Support Portal is the location where users receive support for Delphix's products.

Core concepts

Term	Definition
Virtualization	Virtualization describes the capability of producing a functioning database or filesystem copy that is lightweight and ephemeral.
Masking	Masking describes the capability of iterating through a dataset to identify all sensitive fields and replace them with desensitized values to eliminate risk in lower environments.
Data Source	Data Source is a database or unstructured files located in a user's environment. It generally describes ingestion sources and is typically located in a Source or Staging Environment.
Dataset	Dataset is an instance of any collection of data, such as VDB, dSource, vFiles, data source, or database. The dataset may or may not be managed by Delphix Continuous Data.
Transaction Log(s)	Transaction Log(s) are a general term for a database's record of all events or changes. Typically used for PITR and various ingestion mechanisms. Databases that support this mechanism might refer to these files differently, perhaps calling them something like “redo logs”, but the purpose is the same.
Point-in-Time or Point-in-Time Recovery	Point-in-Time is the recovery or roll forward of a virtual database up to a user specified point in time. This is made possible through the availability of Transaction Logs ingested via LogSync or another mechanism. This is synonymous with Point-in-Time Recovery (PITR).

Continuous Data

Term	Definition
Environment	Environment is a collection of hardware and/or software required to run a source or virtualized dataset. (For example, a Linux system running PostgreSQL.) This may either be a standalone instance or a cluster of instances. See Source, Staging, and Target Environments definitions for different environment types.
dSource	dSource is the copy of a source database's persistent data layer that Delphix Continuous Data uses to create and update virtual databases (VDBs). Based on the ingestion model and data source type, the dSource could be exposed through a mount point and interacts with a Staging Database Instance, Database, or Files. Consult the data source connector documentation for specific details.
Virtual Database (VDB)	Virtual Database (VDB) is a full read-and-write copy of the source data that is provisioned from either a dSource or another VDB. A VDB is provisioned and managed by Delphix Continuous Data.
Timeflow	Timeflow describes the timeline of data of a virtual database or dSource.
Snapshot	Snapshot represents the state of a dataset at a specific moment in time. They are used to create or refresh the same or another timeline.
Hooks	Hooks are mechanisms that allow the execution of custom operations at specific points in various processes like linking, provisioning, and managing virtual datasets.
Replication	Replication is the process of copying objects from one engine (the source) to another (the target).
Unstructured Files (vFiles)	Unstructured files (vFiles) are data stored in a filesystem that is not typically accessed by a Database Management System (DBMS) or similar software.
Delphix Connector	Delphix Connector is a service that runs on the Windows Staging and Target Environments to enable communication with Delphix Continuous Data. The Delphix Connector should not be confused with Data Source Connectors.
Delphix Toolkit	Delphix Toolkit is a set of applications that are installed on the Source, Staging, and Target Environments which enables communication with Delphix Continuous Data. This should not be confused with `dxtoolkit`.
Delphix Storage	Delphix Storage is an underlying component in Delphix Continuous Data's architecture. Delphix Continuous Data uses this storage for ingesting the source data and storing the ZFS snapshots of the ingested data.
HostChecker	HostChecker is a standalone application that validates environments and hosts are configured correctly. HostChecker is available on the Delphix Download Portal.
Object(s)	Object(s) is a general term to refer to a Delphix Continuous Data entity, such as VDB, dSource, Snapshot, or Environment.

Architecture

Term	Definition
Host	Host is a single server within the environment collection. An environment is considered to be one or more hosts. For example, a RAC environment contains multiple hosts.
Staging Architecture	Staging Architecture is an ingestion strategy where a copy of the source data is recreated on an alternate environment where persistent storage is provided by Delphix Continuous Data.
Source Environment	Source Environment is the "production" or "golden" environment that contains the ideal database the user would like to virtualize in Delphix Continuous Data.
Staging Environment	Staging Environment hosts the replica, copy, or backup of the database which Delphix Continuous Data will link and ingest.
Target Environment	Target Environment is the configured infrastructure, with available database binaries, in which virtual database copies will be hosted.
Privilege Elevation	Privilege Elevation is the optional functionality to provide a low-privileged environment user with sufficient permissions to perform the required ingestion and provisioning actions. This solution is not required, but suggested for production implementation of Delphix Continuous Data.
Installation	Installation is the location on source, staging, or target hosts that maintain the dataset's binaries and data. Often referred to as Repository or Dataset Home. Installations that are part of a Source and Staging Host will also be composed of one or more Databases. These Databases enable Delphix Continuous Data to identify the location from which a specific source dataset can be ingested. Often referred to as a Source Config.
Ingestion	Ingestion is the intake process by which Delphix configures the linking connection, obtains a copy of the backing data for the dSource, persists the data to Delphix Storage and takes a snapshot.
Direct Ingestion	Direct Ingestion is a form of intake into Delphix Storage where the persistent data of a dSource is provided directly to Delphix without any need for staging (example: from Oracle RMAN)
Staged Ingestion	Staged Ingestion is a form of intake into Delphix where the persistent data of a dSource must be recreated on an alternate staging host which has mounted Delphix Storage
Staging Pull	Staging Pull is an ingestion method where Delphix controls and executes the necessary operations to prepare the data content in the Staging Environment.
Staging Push	Staging Push is an ingestion method where the user (not Delphix) controls and executes the operations to prepare the data content in the Staging Environment.

Datasets

Term	Definition
Link	Link is the process of establishing a relationship between a data source and Delphix Continuous Data. After linking a data source, Delphix Continuous Data can import data periodically and manage it as it evolves over time. Also called Attach.
Unlink	Unlink is the process of disconnecting Delphix Continuous Data from the data source. Also called Detach.
Discovery	Discovery is a process that allows the connector to gather information about installation details in an environment. The database’s discovery typically occurs as part of the initial environment setup process.
SnapSync	SnapSync is the standard process for importing data from a source into Delphix Continuous Data. An initial SnapSync is performed to create a dSource. Incremental SnapSyncs are performed to provide additional points in time to the dSource. Also, referred to as Sync.
LogSync	LogSync is an advanced process imports more granular source change data through Transaction Logs. This mechanism, often called Point-in-Time Recovery, allows for finer control of VDB point-in-time provision, refresh, or rollbacks.
Validated Sync	Validated Sync is a supportive process that executes cleanup and preparation activities on the Staging environment's database.
Resync	Resync is a Delphix operation by which the existing contents of the dSource are overwritten with a new full copy (ie a full sync) of the source data
Provision	Provision is an operation in which a new child dataset is created from a specific snapshot of the parent dataset (i.e. A VDB from a dSource, or a VDB from a VDB).
Refresh	Refresh is an operation where the virtual database is re-provisioned from its dSource's snapshot or a point in time. All current contents of the dataset are forfeited and the contents are fully restored to the state which has been captured in the chosen snapshot.
Rewind	Rewind is an operation in which the contents of a specific virtual database are reset to the last point in its Timeflow. All current contents of the dataset are forfeited and the contents are fully restored to the state which has been captured in the chosen snapshot.
Enable	Enable is an operation in which a specific virtual database is deployed to a chosen Target environment. Specifically, the persisted virtual database is made available on the environment host via the appropriate network storage operation(s), and then visible and usable on that host. If there is an associated DBMS using that virtual database, the DBMS instance is also started.
Disable	Disable is an operation in which a virtual database is removed from the Target environment on which it is currently deployed. If there is an associated DBMS using the virtual database, that DBMS instance is also stopped.
Start	Start is an operation in which the associated DBMS is started. The virtual database must be in an ENABLED state on the Target environment for this operation to succeed
Stop	Stop is an operation in which an associated DBMS is stopped, but the virtual database is left in an ENABLED state on the Target environment.
Migrate	Migrate is an operation in which a specific virtual database is dissociated from one Target environment and moved to another Target environment on the same Delphix Continuous Data. A complete virtual database migration typically involves DISABLE, MIGRATE, and ENABLE operations. See REPLICATION to migrate datasets from one Delphix Continuous Data to another.
Virtual To Physical (V2P)	Virtual To Physical (V2P) is an operation to take a virtual database and provision it to a third-party database outside of Delphix Continuous Data. This is often used for disaster recovery purposes or as part of a performance test.

Data Source Connectors

Term	Definitions
Connector	Connector refers to the Delphix Continuous Data's data source connection mechanism. A connector enables Delphix Continuous Data functionality with a specific data source system or DBMS. See other connector types for specific details.
Standard Connector	Standard Connector are connectors that are built and supported by Delphix. They are included for free with a Delphix Continuous Data License Agreement.
Select Connector	Select Connector are connectors that are built and supported by Delphix but require a separate License Agreement.
Premium Connector	Premium Connector are connectors that are built and supported by a third party. They often require a separate License Agreement.
Plugin	Plugin is the software delivery framework for many Connectors. The user must upload the plugin into Delphix Continuous Data to install the associated Connector.

Transparent Data Encryption (TDE) definitions

Term	Definition
Artifact directory	Directory on the target system (not on Delphix Storage) which stores keys needed to support Delphix workflows on TDE-enabled vPDBs. It is located under the toolkit directory.
Auxiliary container database (CDB)	Provisioning an Oracle vPDB requires running recovery to bring the snapshotted datafiles into a consistent state. This needs to be done in the context of a container database, which is created on the target system. After the recovery is complete, the vPDB is unplugged and plugged into the target container, and the auxiliary container is deleted.
Exported KeyFile	File located on the target Oracle host which contains keys that have been exported from the KeyStore. It is encrypted with a secret that is specified when it is exported. The exported KeyFile itself cannot be used as a KeyStore, but its contents can be imported into a new KeyStore.
Key rotation	Process for changing the master encryption key in the KeyStore via ADMINISTER KEY MANAGEMENT SET KEY. This does not remove the original key, rather it adds a new key to the wallet and future data will be encrypted with the new key.
KeyStore/wallet	File found on the Oracle host which stores the keys used to encrypt and decrypt the internal table keys in a database. Every KeyStore has a password that is set when it is first created and must be supplied for operations on it.
Parent KeyStore	KeyStore with the keys used to encrypt the dSource PDB files.
Target KeyStore	KeyStore for the target CDB into which the TDE-encrypted vPDB is plugged.

Users roles

User role	Role privileges	Group privileges
Reader	Access statistics on the dSource, VDB, or Snapshot such as usage, history, and space consumption	Access statistics on all dSources, VDBs, or Snapshots in the group such as usage, history, and space consumption
Provisioner	Access statistics on the dSource, VDB, or Snapshot such as usage, history, and space consumption Provision VDBs from owned dSources and VDBs	Access statistics on all dSources, VDBs, or Snapshots in the group such as usage, history, and space consumption Provision VDBs from all dSources and VDBs in the group
Owner	Provision VDBs from owned dSources and VDBs Perform Virtual to Physical (V2P) from owned dSources Access the same statistics as a Reader Refresh or Rollback VDBs Take Snapshots of dSources and VDBs	Provision VDBs from all dSources and VDBs in the group Refresh or Rollback all VDBs in the group Snapshot all dSources and VDBs in the group Perform Virtual to Physical (V2P) from owned dSources Apply custom policies to dSources and VDBs Create template policies for the group Assign Owner privileges for dSources and VDBs Access the same statistics as a Provisioner, Data Operator, or Reader
Data operator	Access statistics on the dSource, VDB, or snapshot such as usage, history, and space consumption Refresh or rollback VDBs	Access statistics on all dSources, VDBs, or snapshots in the group such as usage, history, and space consumption Refresh or rollback all VDBs in the group

User privileges

User type	Role privileges	Group privileges
sysadmin	Can perform typical system administration duties such as: modifying NTP, SNMP, SMTP settings; managing storage; downloading support logs for the Delphix Continuous Data Engine, and performing upgrades and patches. The sysadmin user launches the initial Delphix Setup configuration application and has access to the Command Line Interface (CLI).	Has privileges for storage, upgrades, network, etc.

Types of notification

Type

Notification

Event

Completion of some action in the Delphix Continuous Data Engine. Examples include user-initiated tasks such as snapshots or VDB provisioning, policy-based tasks, and background monitoring and maintenance tasks.

Alert

Caused by a single event on a Delphix Continuous Data Engine. Also known as a System Event, and viewable through the System Event Viewer. Examples include warnings on source/target environment settings, recoverable errors, or incorrect connection settings.

Alert Levels: Informational, Warning, Critical

Fault

A persistent event on a Delphix Continuous Data Engine that remains until the issue is resolved. The fault may be marked resolved automatically or require that it be resolved manually. Selecting to Ignore a fault will also ignore future faults of that exact type against the same object.

System faults describe states and configurations that may negatively impact the functionality of the Delphix Continuous Data Engine and which can only be resolved through active user intervention.

Examples: Delphix Continuous Data Engine storage failure, communication failures between the Delphix Continuous Data Engine and a source or target environment/host

Fault Levels: Warning, Critical

Delphix Self-Service terms

Term	Explanation
Administrator	Has full access to all report data and can configure and administer Delphix Self-Service. Additionally, can use the Delphix Continuous Data Engine to: add/delete reports add/delete users change tunable settings add/delete tags create and assign data templates and containers
Bookmark	A logical reference to a point in time on a branch. You can use it as a point from which to fork new branches. It can also be the target of policies – for example, you can arrange to keep this bookmark for two years. Bookmarks are a way to mark and name a particular moment of data on a timeline. You can restore the active branch's timeline to the moment of data marked with a bookmark. You can also share bookmarks with other Delphix Self-Service users, which allows them to restore their own active branches to the moment of data in your container. The data represented by a bookmark is protected and will not be deleted until the bookmark is deleted.
Branches	Branches are task-specific groupings you can create within a data container. A branch is used to track a logical task and contains a timeline of the historical data for that task. As you work within your data container, you can create more branches overtime to run or complete separate tasks. Branches represent a logical sequence of activity, separate from the underlying data lineage. This is the main concept introduced in the core engine and forms the basis of many higher-level primitives. Branches: Can have only one timeline active at any time Can be user-visible (e.g. exported to a user target) or implementation (e.g. just a staging source to run a series of transformations)
Branch group/target group	A collection of multiple Branches that are treated as a single entity. The system can determine compatibility automatically, or a template can be used to create more complex orchestration.
Branch timeline	A dynamic point-in-time interface for user actions within the Branch. Common activities include re-setting Data Sources to run a test, refreshing the Data Container with the most current source data, and bookmarking data to share or track interesting moments of time along the branch timeline.
Data container	Consists of one or more Data Sources, such as databases, application binaries, or other application data. Allows users to: Undo any changes to their application data in seconds or minutes Have immediate access to any version of their data over the course of their project Share their data with other people on their team, without needing to relinquish control of their own container Refresh their data from production data without waiting for an overworked DBA
Data template	Created by the Engine Administrator, data templates consist of the data sources users need in order to manage their data playground and their testing and/or development environments. Data templates serve as the parent for a set of data containers that the administrator assigns to Delphix Self-Service users. Additionally, data templates enforce the boundaries for how data is shared. Data can only be shared directly with other users whose containers were created from the same parent data template.
Data User	Delphix Self-Service data users have access to production data provided in a data container. The data container provides these users with a playground in which to work with data using the Self-Service Toolbar.