Database Sources

DBackup supports a wide variety of database engines.

Supported Databases

Database	Supported Versions	Backup Method	Restore
MySQL	5.7, 8.x, 9.x	mysqldump	✅
MariaDB	10.x, 11.x	mariadb-dump	✅
PostgreSQL	12 – 18	pg_dump	✅
MongoDB	4.x – 8.x	mongodump	✅
Redis	2.8+	redis-cli --rdb	Manual
Valkey	7.2+	redis-cli --rdb	Manual
SQLite	3.x	.dump command	✅
MSSQL	2017, 2019, 2022	BACKUP DATABASE	✅
Firebird	3.x, 4.x, 5.x	gbak	✅ (pre-configured aliases)

Directory Sources

The Connections page has a Directory Sources tab: storage adapters whose folders can be backed up as files rather than as a database dump. They use the same backends as Storage Destinations but are configured as their own adapters, because the two roles use the configured path differently - a destination writes backup and chain folders into it, a source only reads folders out of it. An adapter is one or the other, never both.

To use the same server for both, use Create as Directory Source on the destination's row (or the reverse here) and adjust the path on the copy.

Database Explorer

Beyond configuring sources for backups, DBackup includes a Database Explorer that lets you browse live databases, tables, and data directly from the UI — no separate database client needed. See Database Explorer.

Adding a Source

1. Navigate to Connections → Databases → Add New
2. Select the database type
3. Choose Connection Mode: Direct or SSH (see below)
4. Fill in connection details (host, port, credentials)
5. Click Test Connection to verify
6. Click Fetch Databases to list available databases
7. Select which databases to backup → Save

Connection Modes

DBackup supports two connection modes for most database types:

Mode	Description	Use Case
Direct	DBackup connects directly to the database via TCP	Database is on the same network / Docker network or connected via VPN (recommended)
SSH	DBackup connects via SSH and runs database tools on the remote host	Database is on a remote server, not directly reachable, or no local CLI tools installed

SSH Mode

In SSH mode, DBackup connects to the remote server via SSH and executes database CLI tools (e.g., mysqldump, pg_dump) directly on that server. The backup output is streamed back to DBackup over the SSH connection. This is not an SSH tunnel - the database tools run remotely.

Supported adapters: MySQL, MariaDB, PostgreSQL, MongoDB, Redis, Valkey, SQLite, Firebird, MSSQL

Required: Database CLI Tools on Remote Host

When using SSH mode, the required database client tools must be installed on the remote SSH server. DBackup does not transfer or install any tools - it only executes them. See the individual adapter pages for the specific tools required.

MSSQL is the exception and needs no tools installed: SQL Server writes the backup itself through a T-SQL command, so SSH mode tunnels that connection instead of running anything remotely. It is the only adapter that works this way.

SSH Configuration Fields

Field	Description	Default	Required
SSH Host	SSH server hostname or IP	-	✅
SSH Port	SSH server port	22	❌
SSH Username	SSH login username	-	✅
SSH Auth Type	Authentication method: Password, Private Key, or Agent	Password	✅
SSH Password	SSH password (for password auth)	-	❌
SSH Private Key	PEM-formatted private key (for key auth)	-	❌
SSH Passphrase	Passphrase for encrypted private key	-	❌

SSH Agent

To use SSH agent forwarding in Docker, mount the agent socket:

services:
  dbackup:
    volumes:
      - ${SSH_AUTH_SOCK}:/ssh-agent
    environment:
      - SSH_AUTH_SOCK=/ssh-agent

Connection from Docker

When DBackup runs in Docker and your database is on the host:

Platform	Host Address
Linux / macOS / Windows	host.docker.internal

For Docker Compose networks, use the service name as hostname.