Dbvisit Standby MultiPlatform 12.4.0 (1 Sep 2026) Released

New Feature

Oracle

Introduced zero data loss feature. More details can be found here.

Improvements:

General

PROJECT-2228 - The legal name of Dbvisit Software NZ Ltd was incorrect in some places and has been corrected.

PROJECT-2262 - In order to more easily accommodate settings for Zero Data Loss notifications, all notification settings have been moved to a new page in the GUI, This includes global email settings, email and Slack address, and Observer notification settings, as well as the new ZDL notification settings. Note that in dbvcli, the notification settings have not moved, and the ZDL notification settings can be found in the dbvcli auto-update command

PROJECT-2283 - The login page has had a facelift.
PROJECT-2287 - An update to our end-user license agreement is available in the installers.

PROJECT-2257 - Several places in the interactive CLI offered by dbvcli that offer a list of items would abort if the items didn’t fit in the terminal. Pagination support has been added to the following:

Oracle:
- dbvcli new—source host, DDC import list, source database, standby host
- dbvcli activate—activation points and custom scripts
- dbvcli dr-test resume—activation points
- dbvcli switchover—custom scripts
SQL Server:
- dbvcli new—source host, source instance, source database, standby host, standby instance
- dbvcli activate—custom scripts
- dbvcli switchover—custom scripts
- dbvcli instance add—host
- dbvcli instance edit—instance
- dbvcli instance show—instance
- dbvcli instance unlink—instance
- dbvcli edit-schedule—READ ONLY mode schedule
- dbvcli remove-schedule—READ ONLY mode schedule
PostgreSQL:
- dbvcli new—source host, source cluster, source PostgreSQL installation, standby host, standby PostgreSQL installation
- dbvcli activate—custom scripts
- dbvcli switchover—custom scripts

Changes to CLI and API

/api/v2 (no new endpoints)

No endpoints were added or removed. All changes are new fields added to support Zero Data Loss; requests that do not use the new fields behave exactly as before.

API	What changed
`POST /activate/oracle`	New optional request fields `use_redo_mirror` and `redo_mirror_dir`: activate using the redo log copies that Zero Data Loss mirrors to the standby host, and optionally specify the directory containing them (defaults to the configured standby redo mirror directory).
`POST /dr-test/resume/oracle`	Same new request fields as `/activate/oracle`: `use_redo_mirror` and `redo_mirror_dir`.
`POST /auto-update/edit/oracle`	New optional request fields to turn Zero Data Loss on or off and configure it: `zero_data_loss`, `replication_mode` (`dbvisit` or `external`), `source_redo_mirror_dir`, `standby_redo_mirror_dir`, `zdl_send_email`, `zdl_send_slack`.
`POST /create-standby/oracle`	New optional request fields to set up Zero Data Loss as part of creating the standby database: `zero_data_loss`, `replication_mode`, `source_redo_mirror_dir`, `standby_redo_mirror_dir`.
`POST /auto-update/show/oracle` `POST /auto-update/edit/oracle`	The response now includes a `zero_data_loss_config` object with the current Zero Data Loss settings: `enabled`, `replication_mode`, `send_email`, `send_slack`, `source_redo_mirror_dir`, `standby_redo_mirror_dir`. It is `null` for non-Oracle configurations.
`POST /list` `POST /new/oracle`	Each returned configuration now includes: `data_loss_exposure_seconds` and `data_loss_exposure_formatted` — how many seconds of transactions would be lost if the primary database were lost now, based on the redo received on the standby (including Zero Data Loss streaming). `log_chain_intact` — false if archive logs are missing from the standby's log chain. `zero_data_loss` — the current state of Zero Data Loss redo replication: `replication_state` (`bootstrapping`, `replicating` or `errored`), the latest redo timestamps on the primary and the standby, the redo log members being replicated, the current transfer rate, and any error. the new `zero_data_loss_config` object inside `auto_update` (see above).
`POST /log-gap-report/oracle`	The response now includes `data_loss_exposure_seconds` and `data_loss_exposure_formatted`, the same `zero_data_loss` status object as `/list`, and `log_chain_gaps` — the ranges of archive log sequences missing from the standby's log chain.
`POST /license/show/oracle\|postgresql\|sqlserver` `POST /license/edit/oracle\|postgresql\|sqlserver`	The returned license details include a new `zero_data_loss` flag indicating whether the license includes the Zero Data Loss feature.

The legacy /api/dashboard endpoint also gains DataLossExposureSeconds, DataLossExposure, LogChainIntact, and a ZeroDataLoss object with the replication mode, state, timestamps, transfer rate, and any error.

dbvcli (no new commands; no top-level flag changes)

New flags:

Command	New flags
`activate oracle` (both variants)	`--use-redo-mirror`, `--redo-mirror-dir`
`dr-test resume`	`--use-redo-mirror`, `--redo-mirror-dir`
`auto-update edit` (Oracle)	`--zero-data-loss`, `--replication-mode`, `--source-redo-mirror-dir`, `--standby-redo-mirror-dir`, `--zdl-send-email`, `--zdl-send-slack`
`create-standby` (`csd`) (Oracle)	`--zero-data-loss`, `--replication-mode`, `--source-redo-mirror-dir`, `--standby-redo-mirror-dir` + matching prompts

Output changes:

auto-update show — new Zero Data Loss section.
list — for ZDL configurations, the Time Gap cell shows DLE <value> (or Initial transfer / (ZDL error)) and the Auto Update cell shows ZDL/ZDL External instead of On.
log-gap-report — new DATA LOSS EXPOSURE section; MISSING LOGS section when archive logs are missing from the standby.

Removal

PROJECT-2203: The DR Score concept has been removed.

We're here to help!