2026.1 release notes
January 2026
Continuous Data 2026.1.0.0 extends incremental Virtual‑to‑Physical (V2P) recovery to Oracle RAC environments, strengthening business continuity and ransomware recovery for clustered production workloads. This release also introduces configurable system‑level dSource hook controls to address enterprise security requirements, adds support for Distributed Network Name (DNN)–based SQL Server deployments in Azure, and enables cross‑domain SQL Server linking and provisioning. Storage management is enhanced with ZFS TRIM and UNMAP support for improved capacity reclamation and visibility. In addition, Continuous Data is now certified for Windows Server 2025 with SQL Server clustering, enhances secure boot protections for Delphix GCP images, and includes numerous bug fixes and API enhancements to improve performance, security, compliance, and manageability.
On this page:
New features
Datasets documentation migration
Oracle Incremental Virtual to Physical (V2P) For RAC
Traditional Virtual to Physical (V2P) exports data from a virtual database (VDB) to a physical database and can be valuable during disaster recovery or ransomware scenarios. Upon an event, immediate use of a VDB provides rapid operational support while the physical database is hydrated in the background, allowing for full production restoration. This new capability restores any deltas on the VDB back to the physical database to ensure no transactions are lost. Incremental V2P is now available for Oracle RAC.
For more information, read Incremental V2P operation for an Oracle dataset.
Configurable dSource Hooks
This feature introduces a system-level configuration option that allows sysadmin users to enable or disable dSource hooks that run on the production hosts. This enhancement provides organizations with greater flexibility to manage dSource hooks according to their own operational and security policies, rather than enforcing a one-size-fits-all approach. By default, the configuration option will be disabled in new engines but will be enabled while upgrading any engine to this release.
For more information, read Enable and disable dSource Hooks.
API/CLI Support for multiple Oracle Key Vault clients per host
Oracle Key Vault (OKV) is a software appliance for centrally managing encryption keys and security secrets across an enterprise's on-premises and cloud environments. It is designed to manage keys for Oracle databases, such as Transparent Data Encryption (TDE) master keys. Until now, Delphix only supported one OKV client per host. This means that all Oracle databases running on the same host must connect to the same OKV server through the same OKV client, resulting in a security limitation that multiple databases on the same host must share the same TDE wallets on the OKV appliance. This was previously released as a feature preview in 2025.6. In 2026.1, Delphix now offers a fully robust CLI/API-only feature to support multiple OKV clients per host, which meets the needs of customers who require security separation between databases running on the same host.
For more information, read Managing Oracle environments.
Distributed Network Name (DNN) support in Azure clusters
DNN is the recommended connectivity method for SQL Server Failover Cluster Instances in Azure, providing improved high availability and simplified networking without relying on traditional cluster IP addresses. With this enhancement, continuous data can seamlessly connect to Azure-based SQL clusters using DNN, ensuring better compatibility, reliability, and failover support for your cloud environments.
For more information, read Requirements for SQL Server environments.
SQL Server cross-domain linking and provisioning support
Cross-domain linking and provisioning are now supported for standalone and clustered environments with mandatory trust, DNS, and proxy configuration workarounds.
For more information, read Requirements for SQL Server environments.
TRIM and UNMAP support for storage devices
Continuous Data now supports issuing TRIM and UNMAP commands to compatible storage devices, enabling accurate capacity reclamation on thin‑provisioned and flash storage. Previously, freed blocks could remain reported as used on backend arrays even after Delphix deleted data. With this enhancement, administrators can manually trigger TRIM, enable automatic trimming, or schedule periodic TRIM operations. This capability helps reduce storage discrepancies, improves capacity visibility, and optimizes backend storage utilization in enterprise environments.
For more information, read TRIM and UNMAP support for storage devices.
Certify Windows Server 2025 for MSSQL clusters
Continuous Data is now certified for Windows Server 2025 running MSSQL clusters, including Failover Cluster Instances (FCI) and Always On Availability Groups (AG).
For more information, read SQL Server matrix.
Shielded VM support for Delphix GCP images (vTPM and Integrity Monitoring)
We've strengthened our Shielded VM support with vTPM and Integrity Monitoring to enhance platform trust. The vTPM securely stores cryptographic material and records measured boot state, enabling validation that the system boots using only trusted firmware and software components. Integrity Monitoring continuously verifies the runtime system state to detect unauthorized changes. Together, these capabilities establish a verifiable chain of trust from boot through operation and help protect sensitive data from tampering.
GCP Shielded VM integrity reset required after upgrade
Engine upgrades that introduce new kernel or bootloader components may trigger integrity alerts on GCP Shielded VMs with vTPM and IMA enabled. After upgrading, run the integrity reset command to establish the updated boot measurements as the new trusted baseline.
For more information, read Reset integrity boot measurements for GCP Shielded VM.
Updated Data Encryption Algorithm to AES-256
We've updated encryption standards to use AES‑256 for protecting stored credentials, aligning with modern security best practices and customer security requirements.
Fixed issues
Release 2026.1.0.0 (January 2026)
| Issue number | Description |
|---|---|
| DLPX-83030 | Updated the action message for faults raised on detecting iSCSI configuration parameter mismatches. |
| DLPX-89452 | Fixed an issue in forward compatible replication that incorrectly tried to update config files. |
| DLPX-90128 | Fixed the fetch and update process for existing nodes based on the host when FQDN differs, preventing the creation of multiple cluster nodes with duplicate host references. |
| DLPX-91340 | Fixed an issue where an incorrect snapshot ID was being displayed in fault.oracle.log.retention.old.snapshot. |
| DLPX-93481 | Added AWS support of IMDSv2 to retrieve instance information. |
| DLPX-94906 | Fixed an issue where the use_large_pages parameter from the repository configuration template was ignored when provisioning an Oracle vPDB in a new vCDB. |
| DLPX-95341 | Fixed an issue where OCI images for some platforms were not available for 2025.5 due to cloud platform integration issues. |
| DLPX-95460 | Fixed an issue to raise faults if RECOVERY_PENDING state is fetched in two consecutive environment monitoring runs for both dSources and VDBs. |
| DLPX-95534 | Fixed an issue where enabling NTP fails after upgrading a Delphix engine with NTP disabled. |
| DLPX-95633 | Fixed an issue where provisioning an Oracle VDB on Exadata infrastructure fails for Oracle version 19.27 and later. Starting from Oracle 19.27, small pages (used by auxiliary databases created by the Delphix Engine) are not allowed on Exadata. |
| DLPX-95743 | Added more resiliency for how Elastic Data handles and recovers from network outages. |
| DLPX-95921 | Fixed an issue that caused Delphix Engines to reach out to the AWS metadata service address 169.254.169.254 even when not running in AWS. |
| DLPX-95922 | Fixed an issue where Oracle database timeflow repair fails when user shell is csh. |
| DLPX-95953 | Improved VDB performance for some pathological scenarios that exhibited high NFS latency for databases making heavy use of large data files. |
| DLPX-96035 | Fixed a bug that caused a Repave background task to fill up storage on Continuous Compliance engines. |
| DLPX-96046 | Fixed an issue that causes upgrade verification across the 2025.4 release boundary to become unresponsive and ultimately fail in some circumstances. |
| DLPX-96059 | Fixed an issue when incremental V2P was performed on the same host as the temporary production VDB, where new datafiles, added to the temporary production VDB, were removed from the VDB, resulting in data loss. |
| DLPX-96085 | Fixed NetBackup image identifier parsing when database names appear as substrings in cluster names, preventing restore failures. |
| DLPX-96244 | Fixed CVE-2025-11001 on Delphix Windows Connector. |
Known issues
| Issue number | Summary | Workaround |
|---|---|---|
| DLPX-95004 | Virtual source enable may fail with exception.lifecycle.cannot.enable.with.null.timeflow exception if a previous refresh operation fails. |
None |
| DPLX-95446 | IBM cloud image is not available for 2025.5 due to cloud platform integration issues. | For new engine deployments, install 2025.4 and upgrade to the latest release. |
| DLPX-95934 | VDBs running on Solaris may fail to come online after upgrading to 2025.4.0.* or newer. | Enable dNFS on affected Solaris VDBs. |
| DLPX-96384 | Incremental V2P fails to apply incremental backups on Oracle 23ai when new or offline datafiles are present in the source VDB/vPDB. | None |
| DLPX-96394 | SystemInfo update API request from API version 1.11.46 or earlier fails with "dsourceHooksEnabled Invalid value type "STRING". Valid types are: BOOLEAN." |
Use the latest API version 1.11.47 for SystemInfo update API requests. |
API changes
In Delphix 2026.1.0.0, the new API version is 1.11.47. This section describes all API changes since API version 1.11.46 which was released with Continuous Data 2025.6.0.0. All URL paths are relative to /resources/json/delphix.
Updates
| API object | Path | Type | Name | Change |
|---|---|---|---|---|
OracleHostParameters
|
NA | Property | tdeOkvHomePath
|
Removed property. |
Additions
| API object | Path | Type | Name | Change |
|---|---|---|---|---|
LdapServer
|
ldap/server
|
Property | isEnabledForCCE
|
New property added. |
MSSqlSnapshot
|
NA | Property | supportsAgVdbFastOperations
|
New property added. |
OfflineReplicationReceiveSpec
|
replication/receive
|
Property | cleanupOfflineData
|
New create and update parameters added. |
OracleBaseSourceRuntime
|
NA | Property | exadata
|
New property added. |
OracleInstance
|
NA | Property | okvClient
|
New property added. |
OracleOKVClient
|
/host/oracle/okvclient
|
API Type | OracleOKVClient
|
New API type for Oracle OKV client added. |
PackagedAppVersion
|
NA | Property | PackagedAppVersion
|
New HYPERSCALE packaged application added.
|
rootOperations
|
timeflow
|
Operation | timeflowSnapshotRanges |
RootOperations added to timeflow API endpoint. |
SystemInfo
|
system
|
Property | dsourceHooksEnabled
|
New property added. |
SystemInfo
|
system
|
Operation | disableDSourceHooks
enableDSourceHooks
|
New operations added. |
TimeflowSnapshotRange
|
NA | API Type | TimeflowSnapshotRange
|
New API type for time range of each snapshot within a timeflow added. |
TrimStatus
|
storage/trim
|
API Type | TrimStatus
|
New API type for TRIM status and settings in system storage added. |
Deprecated and EOL features
End of life for Oracle move-to-asm.sh in Continuous Data
The move-to-asm.sh scripted procedure has reached EOL in this release. To export an Oracle virtual DB or virtual PDB to a physical Oracle ASM or Exadata database, refer to Perform the V2P operation on an Oracle VDB or vPDB to a Physical ASM or Exadata Database.