Arenadata QuickMarts adds ADQMDB backup and an updated Notebook

On 16 July 2026, Arenadata released Arenadata QuickMarts version 26.3.3.20.1.b1. Its main operational change is a built-in mechanism for backing up and restoring ADQMDB data. The vendor also expanded ADQM Notebook and updated platform components.

What the primary source confirms

Backup is launched through a step-by-step Wizard in Arenadata Cluster Manager. A copy can include databases, tables and dictionaries, with local file systems and S3-compatible storage available as destinations.

The release also provides:

• cluster-level network configuration;
• TLS and cipher-suite management in Chproxy;
• support for RHEL 9 and the certified edition of RED OS 8.0;
• ClickHouse 26.3.3.20 and Chproxy 1.30;
• selection of internal or external ZooKeeper / ClickHouse Keeper through a revised ADCM configuration.

ADQM Notebook can now display dependencies between ADQMDB objects, format SQL, present notebook overview information and migrate notebook storage to replicated tables. Chproxy support is intended to distribute load across servers.

Why a built-in copy is useful but insufficient

An ADCM-guided workflow reduces manual steps and makes execution easier to standardise. A completed backup job, however, does not demonstrate that the data can be restored within the required time and recovery point.

A production policy needs explicit answers to several questions:

1. which databases, tables and dictionaries are in scope;
2. where the backup catalogue is kept and who can change it;
3. how data is encrypted in transit and at rest;
4. how many versions are retained and when old copies expire;
5. how RPO and RTO are monitored;
6. where recovery is tested regularly.

Local storage can provide a fast copy but does not protect against a site failure. An S3-compatible destination adds independence when it is physically or logically separate, uses distinct credentials and applies an immutability policy.

Pre-upgrade checks

Start with a test cluster that mirrors the production topology and coordination service. Measure backup duration and its effect on storage, network traffic and queries, then restore a representative dataset and compare it with the source.

A practical checklist:

• verify operating-system and component-version compatibility;
• preserve the current ADCM, Chproxy and coordination-service configuration;
• create dedicated service credentials for the backup repository;
• review TLS settings and trusted certificates;
• restrict permission to back up, restore and delete;
• monitor duration, volume, age of the latest copy and failed jobs;
• test recovery of a complete working dataset, not only individual tables;
• document an upgrade rollback procedure.

Remaining limits

The official announcement describes release functionality but does not provide independent benchmarks, quantify the effect of backup jobs on query workloads or guarantee recovery times for different data volumes.

S3 support also does not establish compatibility with every implementation and access policy. A production pilot should check the selected repository’s documentation, network timeouts, object-size limits and lifecycle rules.

Practical conclusion

The new mechanism closes an important operational gap: ADQMDB backup and recovery can become a managed platform workflow rather than a separate collection of scripts. Notebook and Chproxy improvements also support everyday analytical work and load distribution.

The release delivers its real value only after a successful recovery exercise. Teams should connect the new jobs to their disaster recovery plan, keep at least one copy outside the primary cluster and verify RPO/RTO regularly.

Source: the official Arenadata announcement dated 16 July 2026.