Choose MatrixOne tools and record versions

Select by task, then check tool version and deployment mode. A repository, successful help command or rendered Helm chart does not establish production certification.

Task

Starting point

Boundary

Standalone deployment and scheduled operations

mo_ctl, scheduled operations

Shell tool; distinguish git/binary/docker modes

Declarative management on existing Kubernetes

Operator acceptance

CRD, chart, Operator and MO image versions differ

Cluster installation and components

Distributed mo_ctl

Different commands from the standalone namesake; check installed enterprise package

Logical export and restore

mo-dump

Preserve SQL and CSV files; not a physical backup

Physical backup, snapshot and PITR

Backup selection

Distinguish tools from server features; test supported restore combinations

MO change replication

mo_cdc

Check retention, checkpoint and sink data

pprof, goroutines and object inspection

mo-service, mo-tool

Internal formats and debugging commands are version-specific

Regression tests

MO-Tester

Test cases do not certify capacity

Analytical and transactional benchmarks

SSB, TPC-C

Fix scale, concurrency, warmup, duration and error rate

Choose mo-load, mo-sysbench, mojo, mcp-mo and the separate mo-dashboard repository according to maintenance status and dependencies; code availability is not official support. The separate mo-dashboard aggregates development issues/log links; mo-tool dashboard manages Grafana dashboards.

The SQL function mo_ctl(...) differs from shell mo_ctl. Current main restricts the SQL execution entry to the system account’s moadmin role. Internal fault-injection/storage commands are not general-user operations. See the SQL entry implementation.

Verification record

Record MO tag/commit, tool tag/commit or package version, OS/CPU, deployment mode, dependencies, fixtures, passing/failing checks, date and evidence path. For Kubernetes also record server version, chart, CRD, Operator/backup images, StorageClass and object-storage configuration. Record Secret names rather than credentials. Label each combination as executed, source-checked or unverified; a tool name does not cover every release.