The recommended Linux VM installation runs Mini DBA Engine and Mini DBA Console as Docker containers using the supported Compose bundle.
The Engine continuously monitors your databases while the Console provides browser access. Both containers use persistent host storage so configuration, licensing, monitoring history and secure Console state survive upgrades and container replacement.
- Versioned Mini DBA Engine and Console images.
- One-command installation and repeatable upgrades.
- Configurable persistent data path for an attached VM data disk.
- Engine traffic kept on a private Docker network by default.
- Windows, Linux and container Engines can all connect to the same Console where required.
Linux container bundle
Docker Compose configuration, installer, management script and README.
Download 2026.1 bundleInstall on a Linux VM
Install Docker Engine and Docker Compose v2 first. Attach and mount a persistent data disk before starting Mini DBA.
- Download and extract the bundle on the VM.
- Confirm the data disk is mounted persistently, for example at
/data. - Run
bash install.sh /data/minidbafrom the extracted directory. - Open
http://VM-NAME-OR-IP:8080from an allowed network. - In Console Settings, add
net.tcp://engine:8734/MiniDBAService/tcp. - Activate the Engine licence or begin the trial, then add the database servers to monitor.
/etc/fstab before installation. If the mount is absent, stop Mini DBA rather than allowing its mount path to become an ordinary directory on the OS disk.
What is stored on the data disk?
- Engine configuration, licence and monitored-server definitions.
- Metrics, query history, alerts, logs and diagnostic databases.
- Console Engine connections and MCP key hashes.
- Console data-protection keys and operational logs.
The default is /var/lib/minidba. For a production VM with an attached data disk, pass a path such as /data/minidba to the installer.
Operate and upgrade
bash manage.sh status
bash manage.sh logs
bash manage.sh restart
bash manage.sh upgrade
bash manage.sh stopBack up the complete Mini DBA data directory before an upgrade. The stop command removes containers and the private network but does not delete persistent data.
Network and HTTPS
The bundle publishes Console HTTP port 8080. It does not publish Engine port 8734 because the included Console reaches the Engine through their private Docker network.
Before making the Console available outside a trusted network, put it behind HTTPS using your organisation's reverse proxy or private access layer. Restrict inbound traffic and include the persistent data path in normal backup monitoring.
Native Linux service
A native systemd deployment is an advanced, support-assisted option. The Docker Compose bundle is the standard Linux installation because it packages both components, isolates dependencies and provides a repeatable upgrade path.