4.3.170.1​

Release Date: 21st October 2026

New Features​

Object Editor​

Object Admin has been redesigned and is now available as the Object Editor under Configuration > System Administration. Administrators can now select a class from a single Class dropdown to view its data in one consolidated grid, replacing the previous menu-based navigation.

Custom Dashboard – Custom Layout​

A Custom Layout option has been added to Custom Dashboard, allowing users to define their own dashboard templates rather than relying solely on the predefined templates. Layouts are built from configurable rows of widgets, providing greater flexibility in how dashboards are presented.

Enhancements​

Manage Runsheets – Import / Export Enhancements​

The Import / Export feature in Manage Runsheets now supports additional columns, providing full coverage of the fields available on a runsheet task. This allows runsheet tasks to be exported and imported with complete field data.

Release / Project Environment View Report – Multi-Release Selection​

The Release / Project Environment View report now supports the selection of multiple releases, allowing environment usage across several releases to be reviewed together in a single view.

Event Calendar – Multi-System Selection​

The Event Calendar now supports the selection of multiple systems, allowing users to view event data for several systems at once.

System Instances – Interface Details in Fact Sheet​

System Interface details are now available in the Fact Sheet view of System Instances, providing a more complete view of an instance and its interfaces in one place.

Booking Approval Queue Report – Creation Date and Parent Booking Access​

The Booking Approval Queue report now displays the booking creation date and provides an option to view the parent booking record.

Booking Fact Sheet – Navigation to Booking Insight Report​

The Booking Fact Sheet view now allows users to navigate directly to the Booking Insight report. This option is available for Confirmed and Unconfirmed bookings only.

Environment Pulse – Full Screen Mode​

The Environment Pulse dashboard now supports a full screen mode. Users can toggle the view to expand the dashboard to full screen, making it easier to monitor environment status on large displays.

Service Request Form – Version Field for Change Requests​

The Service Request form now includes a Version field for the Change Request type, allowing the version associated with a change to be captured as part of the request.

3.12 Major Release Items​

What's New​

NEW FEATURE: AI Mask Review (AIMR)​

Get your Mask Configurations right before you run them. AI Mask Review checks your configuration against what profiling found in your data, and suggests fixes column by column.

• Catch configuration errors before masking runs - Missing lookups, fixed values and date formats, duplicate entries, and unique or key columns that would break.
• Faster masking runs - Advice on the best masking function, chunk size and table settings for large tables.
• Don't like the advice? Dismiss it - Dismissed suggestions stay dismissed for that data source, unless the suggestion changes. Your feedback helps shape what AI Mask Review suggests next.

New configurations created by profiling are reviewed automatically. For existing ones, open Pattern Details and click AI Review. See the AI Mask Review guide for details.

Unique and nullable columns are now detected during profiling​

Profiling now records which columns have a unique index or unique constraint, and which columns are nullable. AI Mask Review uses this to keep unique columns unique after masking and to avoid masking key columns.

Database Health Diagnostics, expanded​

Diagnostics introduced in 3.11 now cover more of the supported databases, with fixes for Teradata, Sybase and DB2 checks.

---

Changes​

Validation now runs with every masking run

• Validation runs automatically at the end of every masking execution, so every masked column is checked without a separate step.
• Validation configurations and standalone validation scans have been decommissioned. See the Deprecation Notice below.
• The compliance PDF and CSV reports have been updated to match.

Cleaner configuration screen

• Secondary settings on the Data Configuration screen now sit under a collapsible Advanced Configuration section.

TDM Report

• Long data source and configuration names are now shown in full.

Fixed value masking

• Clearer log messages, and columns are skipped cleanly when no fixed value is set.

---

Fixed Issues​

Profiling

• Oracle profiling no longer fails with ORA-12547 on SSL connections.
• Teradata profiling now reports the correct Data Length for character columns.

Masking

• Teradata DATE columns with an explicit FORMAT are now masked.
• XML masking on Microsoft SQL Server now converts values back to XML correctly.
• Using NULL as the flag string no longer causes a "NO Data In The Column" error.
• Fixed bind parameters in an Oracle column comparison query.

Validation

• "Na" values are no longer counted in the validation score.
• Multi-condition cross-table masking on MySQL and MariaDB now validates correctly when a flag column is also masked.

TDM Report

• Validation and masking executions are now listed in chronological order.

Database Diagnostics

• Teradata "Long Running Queries" now shows only queries that are currently running.
• Fixed Sybase tablespace utilisation and cache diagnostics.
• Fixed SQL0206N errors in some DB2 diagnostic queries.

---

Deprecation Notice​

Validation Configurations and Standalone Validation Scans​

Validation configurations and standalone validation scans have been decommissioned in this release. Validation now runs automatically at the end of every masking run, using that run's masking configuration, so there is nothing to set up.

• Validation can no longer be configured or run on its own.
• Profiling no longer creates a validation configuration.
• Results from earlier validation scans are still available to view.

What you need to know

• You no longer need to create or maintain validation configurations. Any steps in your process that ran a validation on its own can be removed.
• To check a result, open the Execution Console after a masking run. See the Validation guide for details.

---

Known Issues​

Unique_ID Masking

• Others_UniqueID masking may not preserve uniqueness on some numeric columns.

Sybase Profiling

• Profiling may fail when the profiling user has only column-level SELECT permissions on the specified columns.

PostgreSQL Masking

• Many-To-One masking may fail on schemas whose names contain uppercase letters.
• Self-referenced conditional masking may fail with an exception.

Delta Profiling

• When using cross-language profiling, applying a delta profile scan to an existing Mask Configuration with Update may leave the Country and Language values blank on the existing rows. The newly added row is not affected. As a workaround, use Create to build a new configuration from the delta profile scan.

1.10.0 Major Release Items​

What's New​

Choose What Each Onboarding Workflow Does​

New Onboarding shows a workflow as the pipeline it runs: Ingest, Snapshot, Send, Clone and Mount. Tick only the parts you need. A workflow that skips Ingest starts from a source already on the appliance, and one that skips Snapshot starts from an existing snapshot, so refreshing a test copy from last night's snapshot is a Clone + Mount workflow of a few steps. Combinations that cannot run are refused before the workflow is created.

See Onboard Application for the full workflow.

One Volume per Database, Mounted as a Folder​

Each SQL Server database is onboarded onto a single volume, and every volume mounts as a folder under the host's vME folder: <vME folder>\sources\<id> for a source and <vME folder>\clones\<id> for a clone. A host can hold as many volumes as it needs, and a folder path tells you at a glance which dataset a volume belongs to. You choose the vME folder when you install the Windows connector, and you can change it later in the connector's tray settings.

Snapshots and Rollbacks Coordinated with the Host​

vME stops and starts the host's databases for you around a snapshot or a rollback, so a volume a SQL Server host has mounted is never changed under that host. When you take a snapshot of a mounted source, or Create Bookmark or Rollback To Bookmark on a mounted clone, the host's agent:

1. takes the databases on that volume offline and takes its disk offline,
2. waits while vME takes the snapshot or rolls back,
3. brings the disk back at the same folder and sets the databases online again.

Each step is shown as the host reports it.

The onboarding wizard's Snapshot step does the same. Tick Don't stop/start the host databases only when you have already taken them offline yourself. If no agent can reach the host, vME refuses and lists the steps to do it by hand; once the databases are offline, Proceed without the host finishes the job.

See iSCSI Connector for details.

See Where Every Dataset Is Attached​

The Sources, Snapshots and Clones lists show what is attached where and who is using it:

• Attached to names the host that has the volume mounted, whether it is connected, and the folder it is mounted at.
• Used by links to the unfinished workflows that depend on a dataset.
• Sources and clones show when they were created.
• Tick several rows and Delete selected. vME deletes clones first, then snapshots, then sources, and explains in plain words anything it will not delete, for example a source that still has snapshots or one an unfinished workflow is using.

Rename iSCSI Sources and Clones​

Sources and clones exported over iSCSI can be renamed from the web console, the API or the CLI. The export keeps its target name, so a host that has the volume mounted stays connected while you rename it. A dataset an unfinished workflow is using is not renamed, and the message names the workflow.

Follow Every Workflow from One List​

The Recent Workflows list shows each workflow's Technology, with filters for state, date, snapshot, host and source, and grouping. Open a workflow's Stages to see each step and how long it took. Deleting a workflow warns you when it mounted a clone on a host and removes only what that workflow created. A cancelled workflow opens read-only, so you can still see what it did.

Agent Manager: Host Details, Editing and Host Maintenance​

The Agent Manager lists your agents and shows each host's details as its agent reports them: Windows version, CPU and memory, domain, IP addresses, iSCSI initiator name, vME folder, SQL Server instances and versions, and the databases on the host. Edit Agent sets an agent's label, environment and tags.

Host maintenance shows every iSCSI target and portal a host still holds, marked in use, idle (the dataset is on this appliance but the host is not using it) or orphaned (no dataset on this appliance answers for it any more). Select the ones you no longer need and Forget selected: the host removes those entries and touches nothing else.

See Agent Manager for more.

Register Your vME Appliances Once​

The vME Appliances tab of the Agent Manager keeps the appliances this vME sends data to. Add an appliance, Test the connection and Establish trust once. The Send step of a workflow then offers the registered appliances by name, with their pools.

Set Up a New Appliance from Its Console​

A new vME appliance opens a setup menu on its console the first time it starts: configure IPv4 networking (DHCP or a static address with gateway and DNS), set the hostname and the NTP server, and test connectivity. When you finish, it shows a summary with the address to continue at, and the console keeps showing that address. The browser Setup Wizard then shows the network settings already in effect, with Edit these settings if you want to change them.

See the Setup Wizard (First Boot) Guide.

Improvements​

• iSCSI exports need no client address. Creating an iSCSI source or clone asks only for its size; the export's settings show its target name. NFS exports keep their client address and user mapping.
• Safer replication. A send with Overwrite if it already exists is refused when the destination has clones, and the refusal names them. Nothing is destroyed.
• The connector keeps to its own disks. Source preparation and clone mount bring online and format only the disks behind the job's own iSCSI targets, wait for a slow disk to appear, and stop with the targets they expected and the disks they found when nothing matches. Windows automount is restored whenever a clone mount ends.
• Staging databases detach cleanly. Other connections to a staging database are closed before it is detached or restored over, so an open session does not stop an ingest or a teardown.

API Changes & Upgrading​

Update the Windows connector (MSI) to 1.4.0 on your SQL Server hosts. Folder mounts, host-coordinated snapshots and rollbacks, host details and Host maintenance all need it. The installer asks for the vME folder (VME_ROOT for a silent install). vME checks what each connector reports it can do, so a host still on an older connector keeps working for what it supports, and a feature it lacks is refused with a message rather than attempted.

Workflows created before the upgrade keep their drive letters. They are shown under Advanced on the mount step.

Changes to check in a custom REST integration:

• POST /snapshot/create and POST /snapshot/rollback on a mounted iSCSI dataset can answer 202 Accepted with a task_id while the host is coordinated. Poll GET /snapshot/task/<task_id>. A refusal answers 409 with the manual steps; pass "skip_host": true only once you have taken the databases offline yourself.
• iSCSI network_info takes no client_address, anonuid or anongid. NFS keeps all three.
• Workflows take parts, start_from and config_mode, and return parts and live_steps. Each SQL Server database uses one volume.
• POST /source/rename and POST /clone/rename accept iSCSI datasets. A dataset an unfinished workflow is using answers 409 with used_by.
• A request without a username or api-key answers with a JSON error rather than a server error page.

New endpoints:

• The appliance registry: /peer and /peer/<id> with test, trust, pools and agents.
• DELETE /object/destroy deletes up to 100 sources, snapshots and clones in one call and reports each one.
• PATCH /agent with "action": "update" sets an agent's label, environment and tags. Agent listings return each agent's tags, capabilities and host details.
• Source and clone listings return guid, attached_to and used_by.

The vME API reference documents every route, and the vME Postman collection includes an Onboarding (API) folder that runs the one-volume, folder-mount flow.

CLI: vme snapshot create and vme snapshot rollback take --skip_host and --wait; without --wait they print the task id. New vme peer and vme object destroy commands match the API. See the CLI guide.

4.3.169.1​

Release Date: 15th July 2026

New Features​

Environment Pulse Dashboard​

A new Environment Pulse dashboard has been added under Environment > Reports, giving users a real-time, tile-based "heartbeat" view of every environment resource across the landscape. Resources are grouped by Environment Group and colour-coded by status (In-Operation, Unplanned Outage, Planned Outage, Provisioning), with filters for Environment Group, System, and status, plus an adjustable tile size for scanning large estates at a glance.

Event Form – Recurring Events​

The Event Form now supports creating recurring events, removing the need to manually create the same event multiple times. Users can define a recurrence pattern once and have future occurrences generated automatically.

Database Health Diagnostics are here!*​

When a masking run is slow, you no longer have to rely on a DBA to tell you why. Get a fast, clear view inside your database - long-running queries, tablespace usage, and (on supported engines) blocking sessions - so you can investigate slowness and delays yourself. Every check is read-only and safe, and this is just the start, with more diagnostic capabilities coming in future releases. (*Data Manager License Required)

Enhancements​

Manage Runsheet – Mid-Sequence Task Insertion​

Manage Runsheet now supports inserting a task at a selected position within an existing sequence. Subsequent tasks automatically shift their scheduled dates/times to accommodate the newly inserted task, removing the need to manually re-date every downstream task.

Orchestration Manager – Backup & Restore Progress Updates​

The Backup and Restore feature in Orchestration Manager has been enhanced to display live progress updates as the process runs, giving users clear visibility into how far along a backup or restore job is rather than waiting without feedback until it completes.

Security Updates​

SAML Authentication Library Upgrade​

The platform’s SAML authentication library has been upgraded to a newer supported version. This update improves the security, compatibility, and reliability of SAML-based Single Sign-On (SSO) authentication.

4.3.169.1.2​

Release Date: 29th July 2026

Enhancements​

Booking Form – Configurable Add Project Button​

The Add Project button in the Booking Form can now be disabled through configuration, providing greater control over project creation.

Fixed​

Detailed Editor – Tab Data Visibility​

Resolved an issue where data across various tabs in the Detailed Editor was visible only to System Administrators. Authorised users can now view the data as expected.

Cache Clear – Class Selection Dropdown​

Resolved an issue where data was not visible in the Class Selection dropdown when clearing the cache.

4.3.169.1.3​

Release Date: 12th Aug 2026

Enhancements​

Change Request Closure by Requester​

Requesters can now close their own service requests, providing greater control over the request lifecycle.

Description Length Validation​

Added a maximum character limit of 25,000 characters to the Description field to improve input validation and data consistency.

Fixes​

Environment Flow​

Resolved an issue where environment labels were displayed incorrectly when an environment instance was connected to multiple environments.

Improved Multi-Tab Session Handling​

Improved session handling when the same Ecosystem user accesses the application across multiple browser tabs, providing more consistent session behavior.

Data Archiving​

Resolved an issue where an archiving job could fail when no data was available for a specific class.

4.3.169.1.4​

Release Date: 26th Aug 2026

Enhancements​

Runsheet Notification Message​

Enhanced the validation of Runsheet notification messages to allow image tags in supported content.

Fixes​

Data Configuration Import​

Resolved an issue where the search box was not functioning correctly within the Import feature of Data Configuration.

3.11 Major Release Items​

What's New​

Database Health Diagnostics are here!​

When a masking run is slow, you no longer have to rely on a DBA to tell you why. Get a fast, clear view inside your database - long-running queries, tablespace usage, and (on supported engines) blocking sessions - so you can investigate slowness and delays yourself. Every check is read-only and safe, and this is just the start, with more diagnostic capabilities coming in future releases.

• Diagnostic Check

  

• Tablespace Utilisation on an Oracle Database

Informix is here!​

The go-to database for high-throughput transactional and embedded workloads now plugs straight into TDM - profiling, masking, and compliance included. Another key platform, fully covered.

Now supporting Ubuntu 24!​

TDM workerbees and our Enov8-built MongoDB instances are now certified on the U24 operating system.

Conditional masking just got smarter.​

Two new ways to build more precise rules:

• In operator - Check a column against an entire list of values in a single rule. No more writing one rule per value.

• Multiple criteria - Combine several conditions on the same column for finer, context-aware masking.

  • Example #1: Multiple Conditions on the Same Flag Column

  • Example #2: Multiple Conditions on Multiple Flag Columns

---

Changes​

Connection setup

• Added tooltips, placeholder hints, and a new Description field to make connections easier to configure and reduce errors.

Connection name limit

• Connection names now have a maximum length, preventing failures caused by overly long auto-generated config names.

---

Fixed Issues​

Compliance Report

• Sources with no PII now correctly show as Compliant in PDF reports.

Compliance timeline

• Execution columns now stay Pending when profiling, masking, and validation run out of order, instead of showing a misleading OK.

JSON masking

• Large files now stream during processing, so files over 20 GB mask reliably.

MSSQL masking

• Better handling of collation mismatches between source and temp tables.

Oracle masking

• Fixed a temp-table issue affecting Oracle 10g.

Teradata masking

• Fixed intermittent table-resolution errors during chunked merges.

Parquet masking

• ID fields like ACN, ABN, and TFN now stay as text, preserving leading zeros.

File masking reports

• Entries with invalid file paths or schemas now appear in reports with a clear status.

Custom function masking

• Config state is now isolated during runs, giving consistent results every time.

---

3.11.1​

Release Date: 29th July 2026

Fixed Issues​

Fixed Value Masking​

• Inline validation now correctly handles datasets containing a mix of null and non-null values.

Many-to-One Masking​

• Right-padded values in fixed-length CHAR columns are now masked correctly.

MSSQL Conditional Masking​

• Resolved an issue where columns could not self-reference during conditional masking.

Note: When the column used for the condition is also the column being masked, validation will be evaluated against the already-masked value, which may result in inaccurate validation results. Use a separate flag column for validation accuracy.

---

3.11.2​

Release Date: 12th August 2026

Fixed Issues​

Fixed Value Masking​

• Resolved an issue where Extended ASCII (Latin-1) characters were not encoded or stored correctly during fixed value masking, causing garbled or mismatched values in masked output. Affected characters are now handled correctly, ensuring accurate encoding and consistent results.

Fixed Value Inline Validation​

• Resolved an issue where inline validation could incorrectly report Replace With Null and Replace With Empty masking as unmasked or failed. Null and empty masked values are now handled correctly against the null exclusion list, so validation results accurately reflect successful masking.

---

3.11.3​

Release Date: 26th August 2026

Fixed Issues​

MSSQL Fixed Value & Replace with Null Validation​

• Resolved an issue where Fixed Value and Replace with Null validation on Microsoft SQL Server could under-report masking success including columns that were fully masked showing as "Not Masked" or "Skipped." This affected sparsely populated columns, columns with no maskable data, and text/ntext column types where SQL Server's comparison restrictions caused validation to fail outright. Masking itself was never affected; only the validation score reported for these cases has been corrected.

Known Issues​

Oracle Fixed Value Masking​

• Fixed Value masking on Oracle may fail with an ORA-29499 "chunk not found" error when applied to certain LOB columns.

1.9.0 Major Release Items​

What's New​

First-Time Setup Wizard​

New appliances now boot into a guided Setup Wizard that walks you through every first-run step in the browser: hostname, network (DHCP or static IP with DNS), timezone, TLS certificate, licence activation, admin password, authentication method, and the initial storage pool. There is no more manual bootstrapping over SSH.

See the Setup Wizard guide for the full step-by-step walkthrough, including DHCP vs static IP networking and installing your own TLS certificate.

End-to-End iSCSI Agent Orchestration​

vME can now drive the SQL Server iSCSI workflow remotely and automatically. A lightweight Windows agent (installed from an MSI, run as a background service) enrols each SQL Server host with vME and then picks up and runs onboarding, migration, and clone mount/unmount jobs on demand - with no one logging in to run PowerShell.

Agents are managed centrally from the new Agent Manager in the web console: create one-time enrollment tokens, watch each agent's live status, and rotate keys - all over an outbound-only connection (port 443), so no inbound ports need to be opened on the SQL host.

See the iSCSI Connector - Automated (Windows Agent) guide for setup and usage.

Application Onboarding Wizard (Beta)​

A new Onboard Application wizard (Beta) guides you through cloning a production database onto another vME appliance end to end - pairing the two appliances, discovering the source host, and driving the iSCSI agent through prep, snapshot, clone, and mount. This is an early Beta; we'd love your feedback.

See Onboard Application (Beta) for the full workflow.

Container Connection Details​

vME now surfaces each database container's connection details - host, port mappings, mount paths, database type, and environment variables (such as POSTGRES_USER / POSTGRES_PASSWORD) - in the web UI, so you can connect to a running database without hunting for its settings. The container list API (GET /docker/container/list) returns the port mappings, mounts, database type, and environment variables as well.

See Getting container connection info for details.

Consistent Snapshots​

When you snapshot a source or clone that has running database containers, vME now stops those containers first, takes the snapshot, and restarts them - so the captured data is consistent rather than mid-write. The UI shows a container-aware confirmation listing exactly what will be stopped.

See Snapshots for more info.

Rename Sources and Clones in the UI​

You can now rename sources and clones directly from the web console, instead of destroying and recreating them. (Renaming is not supported for iSCSI sources and clones.)

Unix CLI Install​

The vME CLI can now be installed on Unix, in addition to Windows, so you can run it from the command line on either platform. The CLI is also up to date with the 1.9.0 API. See the CLI guide to download and install.

Improvements​

• Clearer LDAP errors - a failed LDAP login now shows the actual error returned by the directory, instead of a generic message.
• Licence errors surfaced - operations blocked by an unlicensed or expired appliance now show a clear licence error.
• Longer sessions - the web session timeout has been extended to 24 hours.

Fixed Issues​

iSCSI connector

• Snapshots now flush the LUN write cache before the snapshot is taken, so clones are no longer occasionally created RAW/empty.
• Skip-backup no longer crashes when pointed at a single backup file.

Platform

• Login now signs in correctly on the button press after a session timeout.
• Fixed a UI refresh glitch when switching between menu items.
• Fixed cross-appliance API calls failing due to certificate handling.
• Resolved intermittent stale database-connection errors.

API Changes & Upgrading​

The 1.9.0 REST API is documented in the vME API reference. A few endpoints changed shape in this release - if you maintain a custom REST integration, review these before upgrading. (The vME web UI and CLI ship updated with the release and need no changes.)

Grab the updated vME Postman collection to get all the new and changed endpoints ready to run - it also includes an Onboarding (API) folder that replicates the full Onboard Application flow as ordered, chained requests.

Breaking changes

• POST /user/modify now requires your current_password, and a password change is sent as a structured object:

  - { "username": "jane", "password": "NewPass456!" }
  + {
  +   "username": "jane",
  +   "current_password": "OldPass123!",
  +   "password": { "current": "OldPass123!", "new": "NewPass456!", "confirm": "NewPass456!" }
  + }
  
• DELETE /user/delete now requires your password and a typed confirmation:

  - { "username": "ubuntu123" }
  + { "username": "ubuntu123", "password": "MyPassword123!", "confirm_text": "DELETE ubuntu123" }
  
• POST /db/receive is now asynchronous - it returns 202 Accepted with a task_id. Poll GET /tasks/<task_id> for completion instead of expecting a synchronous result.

New and improved

• New endpoints: POST /db/send/cancel, POST /user/changepass, POST /db/network/create, DELETE /db/network/delete, and GET /tasks/<task_id>.
• iSCSI sources & clones over the API: POST /source/create and POST /clone/create accept a network_info block (type: iscsi, with auto_grow / vsize), and the iSCSI target is provisioned automatically as part of creation.
• System-to-system db send no longer needs an SSH/PEM key - vME establishes trust with the receiver automatically using its admin api-key.

1.9.1​

Version 1.9.1 is a focused update to the Onboard Application workflow and the iSCSI connector, based on feedback from teams using them day to day.

What's New​

Choose Your Own Database Name Prefix​

Databases ingested onto iSCSI storage were always named with a fixed ISCSI_ prefix. The ingest step now has a Target database prefix field (under Advanced options) so you can pick a naming scheme that suits your environment. The default remains ISCSI_, already-ingested databases are detected using your chosen prefix, and teardown detaches using the same prefix the workflow ingested with.

Tear Down the Source Host​

Once an application has been onboarded and cloned to the target appliance, you can clean up the source SQL host with one click. Tear down source detaches the staging databases, disconnects the workflow's iSCSI sessions, and frees the drive letters on the source host - without touching the source dataset on the appliance, so you can keep cloning from it. Only the workflow's own sessions and databases are affected.

Recognisable Snapshot Names​

Snapshots created in the wizard now default to a name derived from your source name (for example SalesDB-20260729103000) instead of the generic prepared-<timestamp>. The name stays fully editable, and invalid characters are rejected with a clear message.

Automatic Drive Letter Assignment​

The ingest and clone-mount steps now pick free drive letters automatically instead of defaulting to fixed letters that may already be in use. The pickers prefer the host's recommended letters when free, and never assign the same letter to data and log. Selecting an in-use letter manually still asks for confirmation before reformatting.

Improvements​

• P: and S: are now assignable as data/log drive letters across the wizard and the Windows connector.
• Teardown is kinder to shared hosts - a full iSCSI cleanup no longer restarts the Windows iSCSI service, so other iSCSI workloads on the same host are not interrupted, and mount-point cleanup only touches the drive letters the workflow owns.

Fixed Issues​

Onboard Application​

• Workflow steps completed directly via the REST API (for example with the Postman collection) are now recorded on the workflow and shown on the wizard's stepper, which refreshes live - previously the stepper only updated for actions taken inside the wizard itself.

iSCSI Connector​

• Tearing down a clone could leave the iSCSI session reconnecting automatically: persistent target registrations are now parsed and removed correctly, so a torn-down target stays disconnected.
• Sessions are now disconnected reliably even when the target is no longer in the discovered-targets list.
• Disks are taken offline before their session is disconnected, so volumes dismount cleanly during teardown.
• The teardown's database-detach step can be skipped cleanly when there is nothing to detach, instead of stalling the run.

API Changes & Upgrading​

Update the Windows connector to use the new features. The custom database prefix and the teardown fixes live in the Windows iSCSI connector - update the connector (MSI) on your SQL Server hosts as part of this upgrade. Until a host's connector is updated, ingests on that host keep the default ISCSI_ prefix regardless of what is set in the wizard.

Behaviour change for direct connector use: in the teardown script, the disconnect selection now takes Windows disk numbers (as shown in the script's disk listing) instead of session list positions. ALL and MATCH selections are unchanged, and wizard-driven teardowns are unaffected.

API additions (all optional, backwards compatible):

• The ingest and teardown jobs accept a dbPrefix value (migrate.dbPrefix / unmount.dbPrefix).
• The snapshot, clone, source, and send APIs accept optional workflow tracking fields (workflow_id, wizard_step, role) so API-driven onboarding steps appear on the wizard's stepper.
• The vME Postman collection's Onboarding (API) folder has been updated to use these fields.

1.9.2​

Version 1.9.2 continues the Onboard Application and iSCSI connector work.

What's New​

Choose Which Databases To Restore From Your Backups​

The ingest step can now probe backup paths: every database found is listed with its backup set (stripes, differential, backup time) and you tick the ones to ingest. Sets that cannot be restored are marked with the reason, and a name that already exists on the host is flagged as a replacement. A probe reads backup headers only, so it can run before the iSCSI drives are prepared.

Ingest From Full Plus Differential Backups​

A striped full plus its newest differential now restores as one backup set, and stripes may span several backup paths. An incomplete set stops the run naming the files it found.

Choose the Source SQL Instance​

An optional SQL instance field on the ingest step pins the source instance on hosts running more than one. Teardown targets the instance the ingest used.

Database State in Discovery​

Host discovery reports each database's state, and a database that cannot be read cannot be selected as a source.

Improvements​

• Ingest jobs are no longer limited to one hour, and restore progress appears in the job log as it runs.
• Drive letter suggestions are simply the first two free letters.
• Backup paths are entered one per line; a trailing comma or semicolon is ignored.
• A step whose agent stops reporting shows in amber as stopped reporting instead of running forever. An agent that comes back still reports the real outcome.

Fixed Issues​

Onboard Application​

• Deleting a workflow with cleanup now detaches the staging databases on the source SQL host before destroying the source dataset, instead of leaving them unreadable on the instance.
• A delete that reports itself as still in progress can simply be run again and completes the cleanup.
• A clone attached with a custom database prefix no longer gains an extra ISCSI_ on top; clones attach under the name the ingest created.
• The setup wizard rejects invalid hostnames, and the NTP field accepts IPv4-mapped IPv6 addresses.

iSCSI Connector​

• A workflow could prepare, format or reclaim drive letters from another workflow's disks when one source name was a prefix of another. Workflows now match their own disks exactly and stop rather than touch a disk they cannot confirm as their own.
• Clones no longer attach with a doubled name such as ISCSI_Sales_Sales. Existing doubled names can be renamed with ALTER DATABASE ... MODIFY NAME, a metadata-only change.
• The attach honours the configured database prefix instead of always applying ISCSI_.

API Changes & Upgrading​

Update the Windows connector (MSI) on your SQL Server hosts. Everything above except the wizard changes lives in the connector. In particular, ingesting from existing backup files requires the updated connector: on an older one the probe reports a configuration error and the ingest cannot start. Other ingest modes keep their previous behaviour until a host is updated.

If you used a custom database prefix in 1.9.1: clones mounted before this upgrade may carry a doubled name the teardown will not match. Detach them on the host or rename them with ALTER DATABASE ... MODIFY NAME first.

API additions (all optional, backwards compatible):

• migrate.probeOnly reports the backup sets in migrate.backupPaths (as backupSets in the job result) without restoring; drive letters are not required. Pass the reported files back as backupPaths to restore a subset.
• migrate.sqlInstance pins the source SQL instance.
• attach.dbPrefix applies the wizard's prefix to an API-driven attach.
• job_timeout_seconds overrides a job's default timeout (24 hours for an ingest, one hour otherwise).
• Host discovery includes each database's state.
• Agent jobs can report a non-terminal timed_out state when the host's agent stops reporting; a returning agent can still move the job to completed or failed.
• The vME Postman collection carries a version so it can be matched to a release.

Behaviour note for direct connector use: the clone attach derives each database's name from its primary data file rather than the file name.

1.9.3​

Version 1.9.3 adds wrong-instance protection for ingest and rounds out driving the Onboard Application through the API.

What's New​

Wrong-Instance Protection for Ingest​

On hosts running more than one SQL instance, database ids repeat across instances. The wizard now records which instance your databases were selected on and blocks a selection that spans instances, and the connector stops an ingest before anything is backed up or restored when the job resolves to a different instance than the selection was made on. Runs without an explicit database selection are unaffected.

Improvements​

• Portal addresses on the discovery, ingest, and mount steps are validated when you submit: a mistyped address is rejected immediately with a message instead of queuing a job that fails later on the host.
• A failed agent job now fails its workflow: the failed step is named on the final page, and Mark complete asks for explicit confirmation while a step has failed.

Fixed Issues​

Onboard Application​

• Workflow steps completed through the API (for example with the vME Postman collection) now record the same details the wizard records, so the wizard renders API-driven workflows correctly.
• Resume source provisioning and Re-apply iSCSI settings now succeed on a partially or fully provisioned source.
• Two sends started at the same time no longer conflict during first-time transfer setup.

API Changes & Upgrading​

API additions and behaviour (backwards compatible):

• /db/network/create on a dataset that already has its network settings returns success with "Network already configured" instead of an error.
• migrate.selectionInstance on an ingest job names the instance a database selection was made against; the job aborts before restoring when it resolves to a different instance. Omit it to keep the previous behaviour.
• receiver.ssh_address on /db/send sets the data-transfer host when it differs from the target's API address (for example a private address between appliances).

Update the Windows connector (MSI) to 1.3.3 on your SQL Server hosts to get the wrong-instance protection; other changes live on the appliance.

4.3.168.2.2​

Release Date: 10th June 2026

Fixed​

• Resolved an issue where users could encounter an incorrect Max Concurrent User count error during login.

4.3.168.2.3​

Release Date: 11th June 2026

Fixed​

• Improved session cleanup to ensure session files are removed correctly.

4.3.168.1​

Release Date: 1st April 2026

New Features​

Horizontal Navigation Menu​

A new horizontal navigation menu has been introduced to provide direct, streamlined access to core Enov8 modules, reducing reliance on nested navigation structures.

The updated navigation model centralises access to key modules (Environment, Release, Project, Event, Service, Configuration, Data, Orchestration), improving efficiency and simplifying the user experience. The scalable design also ensures the menu can accommodate future module expansion without impacting usability.

Environment Flow – End-to-End Flow Modelling & Status Monitoring​

A new capability, Environment Flow, has been introduced to enable modelling of end-to-end flows across environment instances and system interfaces. Users can define logical flows representing interconnected components within their environment landscape, providing a clearer view of system interactions and dependencies.

Each flow is assigned a dynamic status that reflects the health of its underlying components. Any change in the status of an environment instance or interface (e.g., downtime or failure) is automatically propagated to the associated flow, allowing users to quickly identify impacted flows and take corrective action. This enhances visibility, improves impact analysis, and supports proactive monitoring of critical environment pathways.

Enhancements​

Redesigned Top Bar​

The top bar has been redesigned to deliver a cleaner, more structured interface with enhanced accessibility to global actions. The update introduces support for dark and light mode, along with modernised icons and refreshed visual styling, improving overall clarity and consistency.

The enhanced layout and visual hierarchy provide a more intuitive user experience, enabling quicker access to key actions while aligning with the platform’s broader UI modernisation.

Global Search – UI Modernisation & Category-Based Filtering​

The Global Search experience has been redesigned with a modern UI, improving usability, readability, and overall visual consistency across the platform.

The update introduces category-based filtering via a left-hand panel, allowing users to quickly refine results across areas such as Environment, Events, Systems, and Packages. With grouped results and category-level visibility, users can navigate search outcomes more efficiently, reducing the time required to locate relevant records.

Data Model Management – Unified Interface & Backup Restore Enhancement​

Data Model Management has been streamlined into a unified interface, bringing all model lifecycle operations into a single, consolidated view. Previously distributed across multiple dropdown options (Load, Backup, Delete), these actions are now centrally accessible, improving usability and reducing navigation complexity.

The Load Model capability has also been enhanced to include visibility of automated system backup files. This enables users to quickly restore models directly from available backups without relying on external tracking or manual processes, significantly improving recovery efficiency and operational control.

Bulk Edit Enhancements​

Bulk edit capabilities have been extended across key modules to support additional update and configuration actions, enabling more efficient management of large datasets.

The following enhancements have been introduced:

Report	Bulk Actions Supported
Configure Environment	Create Tags, Update Versions
Manage Events	Create Tags, Update Version, Update Environment
Manage Service Requests	Update Root Cause Type, Update Priority

These enhancements reduce manual effort, improve data consistency, and streamline administrative workflows across the platform.

Subscription Manager – UI Redesign & Category-Based Unsubscription View​

The email unsubscribe experience has been redesigned with a modernised UI, improving usability and providing clearer visibility into subscription preferences.

The updated interface introduces a category-based view, allowing users to filter unsubscribed items by class (e.g., System, Environment Instance, System Interface) from the left-hand panel. This enables users to quickly identify and manage the specific objects they have unsubscribed from, improving transparency and control over notification settings.

Dynamic Date Range Handling in Shared Report URLs​

Date range handling in shared report URLs has been enhanced to support dynamic date selections. Previously, when users selected predefined ranges (e.g., This Month, Last 30 Days) and shared the URL, the exact date values at the time of sharing were persisted.

With this update, shared URLs now retain the selected date range type rather than fixed dates. When the URL is accessed, the report dynamically recalculates and displays data based on the current date context. For example, a report shared with This Month will always display data for the current month at the time of access.

For Custom Date selections, the explicitly chosen date range is preserved and consistently displayed when the shared URL is opened.

This enhancement ensures reports remain contextually relevant while maintaining accuracy for fixed-date scenarios.

Orchestration Manager – Enhanced Scheduling (Weekly & Monthly Support)​

Scheduling capabilities within Orchestration Manager have been extended to support Weekly and Monthly execution frequencies. This enhancement provides greater flexibility in defining automation schedules, enabling alignment with more complex operational and business-driven timelines.

4.3.168.1.7​

Release Date: 21st April 2026

Fixed​

• Resolved an issue where user login approval status did not update correctly.

4.3.168.1.8​

Release Date: 8th May 2026

Enhancements​

• Async Orchestration Backup: Added an asynchronous backup feature to Orchestration Manager. Users can now trigger backups without blocking other operations.

Fixed​

• Resolved an issue where data format was different to the configured format in Runsheet Activity & Event Insight Reports
• Increased the width of Data Source in Execution Console for TDM
• Resolved an issue with Status color not coming properly in Action Runsheet area.

4.3.168.1.9​

Release Date: 20th May 2026

Enhancements​

• The Booking Form "Service Request" copy feature has been improved to support copying the booking sub type.
• The WYSIWYG Editors within Manage Runsheets now include enhanced table editing capabilities, allowing users to easily add or remove rows and columns.

Fixed​

• Addressed an issue that prevented changing the booking status to "deleted."

3.10 Major Release Items​

What's New​

Reporting & Compliance Enhancements​

TDM reporting has been redesigned to provide a more in-depth compliance view across onboarding and operational activity. Reports can be generated at any stage of application onboarding, with time and date filters to review database activity for defined periods (for example, quarterly reporting windows). PDF and CSV outputs consolidate profiling, masking, and validation outcomes at the column level across multiple executions. Users can also download reports for all jobs executed within the selected period, with filters applied to target specific results such as TFN matches across a single database or grouped databases.

Enhanced Chunking for Fixed-width File Masking​

Added chunked processing support for fixed-width file masking to improve throughput on large datasets. This update improves scalability and reduces memory overhead for high-volume file inputs.

Enhanced Grouped Connection Support​

Extended grouped data connection capabilities with delta profiling and bulk delta scan execution across related data sources. Masking configurations can now also be created or updated in bulk, improving operational efficiency and consistency in larger environments.

Expanded Database & Feature Support​

Added new capabilities across multiple platforms, including:

• XML masking and casting support for MSSQL
• SSL/TLS (including TCPS) support for Oracle and Sybase
• Enhanced MongoDB GSSAPI authentication with additional configuration options

---

Changes​

MongoDB Log Rotation​

Automated log rotation is now configured during MongoDB installation to prevent log growth and disk space issues. The installer creates and validates a daily rotation policy that retains 7 compressed logs.

Enhanced TDM Configuration Descriptions​

Field descriptions in profile and mask configurations have been updated to provide clearer, more informative guidance. Users will now see contextual information, including usage considerations and any limitations, helping to improve configuration accuracy and reduce setup errors.

---

Fixed Issues​

Others_UniqueID Pattern - Database Masking​

• Updated masking logic for columns with unique constraints so generated values maintain uniqueness and avoid integrity conflicts during masking operations.

Improved Database Profiling Accuracy​

• Profiling status for columns containing special characters is now reported correctly, including detailed failure information where applicable.

Conditional Masking​

• Improved conditional masking behavior when the dependent or flag column contains null values. Conditions are now evaluated consistently so rules behave as expected for null-based scenarios.

Database Compatibility Fixes​

Resolved compatibility issues across supported databases, including:

• Oracle — conditional masking, date handling, and quoting issues
• PostgreSQL and Aurora variants — validation accuracy and empty table handling
• MySQL and MariaDB — cross-table masking and merge behaviour
• MSSQL and Sybase — masking, validation, and function handling
• Teradata — schema handling and function stability

File Processing Enhancements​

Improved file-based workflow behavior and diagnostics, including:

• Consistent masking and validation for fixed-width, CSV, and JSON files
• Improved handling of file paths, including missing files and non-standard path formats
• Clearer, more informative messages during file processing

3.10.1​

Release Date: 24th April 2026

Fixed Issues​

Teradata​

Resolved cleanup of Enov8_Rn_Tbl post-masking to ensure it is removed after execution.

MSSQL​

• Introduced chunking support for inserts into temporary tables to improve performance and stability during large operations.

• Fixed issues with fixed value masking when chunking is enabled, ensuring consistent processing.

• Resolved issues in cross-table conditional masking to ensure reliable execution.

Compliance Report​

• Improved UI/CSS styling for the TDM Compliance Report for better readability and presentation.
• Reintroduced the Forensic Results section within the report, now positioned in the appendix.

Free Text Masking​

Enhanced free text masking capabilities to:

• Detect and sanitise numeric data within unstructured text.
• Recognise and mask Australian Medicare numbers.
• Dynamically adjust text character limits based on available server memory to prevent out-of-memory errors.

3.10.2​

Release Date: 13th May 2026

Fixed Issues​

Oracle and MongoDB Masking​

• Resolved an issue where chunked distinct value retrieval caused an error during Many-to-One masking.

PostgreSQL Masking​

• Improved fixed-value masking SQL generation for PostgreSQL when no flag conditions are configured, avoiding an unnecessary flag-column reference in that scenario.

Release Date: 6th March 2026

Key Features​

• User & Role Management: Added full administrative user management capabilities within vME. Administrators can now add, modify and delete users directly from the platform.
• LDAP Integration: vME now supports integration with Active Directory via LDAP, allowing centralised authentication and improved enterprise security alignment.
• ZFS Pool Disk Discovery: When creating a ZFS storage pool, vME now automatically retrieves and displays available disks and partition information, simplifying storage configuration and reducing manual effort.
• iSCSI Volume Autogrow: iSCSI storage volumes now automatically grow as needed. Manual size configuration has been removed, providing a simpler and more reliable provisioning experience.
• CHAP Authentication for MSSQL iSCSI: Added CHAP authentication support when mounting MSSQL databases over iSCSI for enhanced security.

Enhancements​

• Operating System Disk Protection: System disks are now clearly identified and protected from accidental pool creation, reducing risk during storage configuration.
• Improved Logging: Logging has been enhanced to provide clearer, more structured messages to assist with troubleshooting and operational visibility.
• CLI Alignment: The CLI has been updated to align with the latest API capabilities, ensuring consistent behaviour across interfaces.
• Container Image Pull Refresh: Added automatic refresh during container image pulls to provide better visibility into progress.
• Dark Mode Improvements: Improved text consistency and readability in Dark Mode.
• Frontend Stability Improvements: Addressed UI refresh behaviour and improved overall frontend responsiveness.
• Documentation Updates: Updated API, CLI and frontend documentation to reflect new capabilities and screenshots.

Bug Fixes​

• Disk Validation: Resolved an issue where invalid physical device paths could be passed during disk operations.
• Pool Disk Display: Fixed an issue where newly created iSCSI disks were incorrectly appearing as available disks for pool creation.
• Security Library Update: Addressed frontend security warnings related to third party libraries.