Data

Tools

Indexes

Applications

Experiments

Awesome

An open API service indexing awesome lists of open source software.

https://github.com/devlifex/dback

DB Sync Manager is a powerful, cross-platform desktop application designed to simplify the complex task of migrating and backing up large databases. Whether your database is hosted on a remote Linux server, running inside a Docker container, or powering a WordPress site, DB Sync Manager provides a unified interface to stream, export, and import
https://github.com/devlifex/dback

bakcup docker mariadb mysql wordpress

Last synced: 25 days ago
JSON representation

DB Sync Manager is a powerful, cross-platform desktop application designed to simplify the complex task of migrating and backing up large databases. Whether your database is hosted on a remote Linux server, running inside a Docker container, or powering a WordPress site, DB Sync Manager provides a unified interface to stream, export, and import

Awesome Lists containing this project

README 

          
![DBack](dback.png)



# DBack — DB Sync Manager



**Desktop GUI for MySQL/MariaDB backup and restore over SSH, Jump Host, Docker, or WordPress.**



DBack connects to remote Linux servers or WordPress sites, streams database dumps to local files with compression, and restores backups to any saved host. Hosts, templates, history, and logs live in an encrypted local vault. Built with Go and [Gio](https://gioui.org).



**Repository:** [github.com/devlifeX/dback](https://github.com/devlifeX/dback/)



## Highlights



- **Streaming backups** — large dumps (5GB+) with on-the-fly `zstd`/`gzip` compression

- **Smart fallback** — retries with a remote tmp-file when SSH streams fail; supports resume and checksum validation

- **Unified hosts** — one connection, backup folder, and import queries per host

- **WordPress hosts** — backup/import/query via the embedded **DBack DB Tools** plugin (pure PHP, no shell on the server)

- **Encrypted vault** — profiles, templates, history, and logs stored in `app_data.vault.json`

- **Remote sync** — push/pull encrypted app settings to S3-compatible storage (AWS S3, MinIO, etc.)

- **SQL templates** — reusable snippets with placeholders for pre/post import queries

- **Connection testing** — step-by-step checks from the host editor (SSH + DB, or WordPress REST + preflight)

- **Modern UI** — dark GitHub-style desktop interface with sidebar navigation and host overflow menus



## Screenshots



### Hosts

Manage remote servers, filter by group, search, and run backup actions from host cards.



![Hosts screen](screenshot/1.png)



### SQL Templates

Create reusable SQL snippets with placeholders for pre/post import queries.



![SQL template editor](screenshot/2.png)



### Host profile — import queries

Configure pre-import SQL, append templates, and test queries before restore.



![Host profile queries](screenshot/3.png)



## Features



### Connectivity

- **SSH / Jump Host** — password or private key authentication

- **Docker** — MySQL/MariaDB inside containers (`docker exec`)

- **WordPress** — REST API via the **DBack DB Tools** plugin (`dback/v1`); download a site-specific plugin zip from the host editor

- **Databases** — MySQL and MariaDB only

- **Connection test** — guided SSH + database check, or WordPress ping + preflight + `SELECT 1`



### Backup & Restore

- **Preflight checks** — SSH: OS, dump/client tools, disk space, Docker status; WordPress: PHP, zlib, DB, uploads via plugin `/preflight`

- **Restore flow** — select a backup, pick a destination host, run pre-import SQL, import, then optional post-import SQL

- **Pre/post import queries** — run before restore starts; failures abort the import and show an error in the app

- **Job center** — progress and cancel controls on the Backups screen



### WordPress plugin (DBack DB Tools)

- Embedded in the desktop app; **Download Plugin** builds a zip with a per-host API token hardcoded in the plugin

- Plugin lives in [`wordpress/dback-db-tools/`](wordpress/dback-db-tools/) — pure PHP export/import/query (no `exec` / shell on shared hosting)

- Install on the site via **Plugins → Upload Plugin**; match **Site URL** in DBack to WordPress **Settings → General**

- Optional **Target database** on the host — empty uses `wp-config.php` default; set a name to create/select that DB on import and post-import queries

- Dev-only files (e.g. `wordpress_agent.md`, `*.md`) are excluded from the downloadable zip — see `release_zip.go`



### Host Management

- **Host cards** — green **Backup** action plus a **⋮** overflow menu for Edit, Duplicate, and Delete

- **Duplicate** — clone a host with one click (`Production 1`, `Production 2`, …)

- **Groups & search** — filter by group, search by name

- **Legacy migration** — old export/import profiles are flattened on load



### App Data Transfer

Settings has two tabs: **Export** and **Sync**.



**Export / Import (local file)**

- Export/import hosts, templates, backup history metadata, and activity logs

- Backup `.sql.gz` files are **not** included in the bundle

- Encrypted export with an export password (Argon2id + AES-256-GCM)

- Non-destructive merge — conflicts prompt before overwrite



**Remote Sync (S3-compatible)**

- Push or pull the same encrypted app-data bundle to `{bucket}/dback/app-data.json`

- Works with AWS S3, MinIO, and other S3-compatible endpoints

- Configure endpoint, region, bucket, access key, secret key, and SSL

- **Test Connection** verifies bucket access and read/write permissions under `dback/`

- **Push** / **Pull** appear after a successful connection test

- Encrypted with your **vault master key** (the same key used to unlock DBack), not the export password

- Sync settings (S3 credentials) are included in the remote bundle

- Pull downloads the bundle, asks for confirmation, then merges like a local import

- **Sync log** (local only, not uploaded): last push and last pull timestamps



### SQL Templates

- Create, edit, and delete reusable SQL snippets

- Append template text to pre/post import queries

- Placeholders: `{databasename}`, `{host}`, `{profile}`, `{dbuser}`



### Diagnostics & Logging

- Test SSH and database connectivity from the host editor

- Structured activity logs (operation ID, phase, strategy, attempt, masked commands)

- Debug mode mirrors logs to stderr (`--debug` or `DBACK_DEBUG=1`)



## Quick Start



### Run from source



```bash

./run.sh

```



With debug logging:



```bash

./run.sh --debug

# or

DBACK_DEBUG=1 ./run.sh

```



### Build (Linux)



```bash

./build.sh

# or

./build.sh linux

```



Output:

- `dist/dback-linux`

- `dist/dback` launcher wrapper (handles common EGL/GPU driver issues)

- `dist/dback_${APP_VERSION}_amd64.deb` — Debian/Ubuntu installer with menu icon (`/usr/bin/dback`)



Set the app version at build time:



```bash

APP_VERSION=3.6.4 ./build.sh linux

```



Version appears in **About** inside the app. Use **Check for updates** on the About screen to compare against [GitHub Releases](https://github.com/devlifeX/dback/releases); when a newer version exists, DBack downloads the matching asset and installs it (Linux `.deb` via `pkexec` + `apt`, Windows `.exe` with restart helper).



### Build (Windows)



Requirements: **Go 1.21+** and a Windows development environment.



```powershell

go build -ldflags "-X main.appVersion=3.6.4" -o dist/dback-windows.exe .

```



### Build manually (Linux)



Requirements: **Go 1.21+** and Gio development libraries.



On Debian/Ubuntu:



```bash

sudo apt-get update && sudo apt-get install -y \

  build-essential pkg-config libvulkan-dev xorg-dev libwayland-dev \

  libxkbcommon-dev libxkbcommon-x11-dev libx11-xcb-dev libxcursor-dev \

  libxfixes-dev libegl-dev

```



Then:



```bash

go build -ldflags "-X main.appVersion=3.6.4" -o dist/dback-linux .

```



### Docker alternative



If system dependencies are problematic:



```bash

./docker-run.sh

```



### GitHub Releases



Tagged releases (`v*`) are built automatically by GitHub Actions:



| Platform | Artifact |

|----------|----------|

| Linux | `dback-linux`, `dback_{version}_amd64.deb` |

| Windows | `dback-windows.exe` |



Install on Ubuntu/Debian:



```bash

sudo apt install ./dback_3.6.4_amd64.deb

```



**Launchpad PPA** (after published):



```bash

sudo add-apt-repository ppa:devlifex/dback

sudo apt update

sudo apt install dback

```



Setup and upload: [`ppa.md`](ppa.md).



Or use **About → Check for updates** inside the running app.



## Default Paths



| Purpose | Path |

|---------|------|

| App config & data | `~/.config/dback` |

| Default backups | `~/dback/backups` |

| Encrypted vault | `~/.config/dback/app_data.vault.json` |

| Remote sync object | `{bucket}/dback/app-data.json` |

| SSH known hosts | `~/.config/dback/ssh_known_hosts` |



Hosts, templates, backup history, and activity logs are stored inside the encrypted vault. Each host can override the backup destination folder.



## Security



- On first launch, DBack prompts for a **master key** (minimum 8 characters; confirmation required when creating a new vault).

- Legacy plaintext files are removed after successful migration into the vault.

- **App Data Transfer** exports require an export password. **Remote Sync** uses the vault master key instead. Metadata in history and logs may still contain host names and paths.

- S3 credentials are stored in the encrypted vault and included in sync bundles — use bucket policies and least-privilege IAM where possible.

- SSH uses **TOFU host key verification** — unknown keys are saved on first connect; mismatches are rejected.

- Remote database commands validate and shell-escape profile fields to reduce injection risk.

- Password fields are masked in the UI. Error messages are sanitized unless debug mode is enabled.



## Usage



### Hosts

1. Open **Hosts** → **+ Host**

2. Choose connection type: **SSH**, **Jump Host**, **Localhost**, or **WordPress**

3. For SSH/Docker: configure server access, database credentials, and backup destination

4. For **WordPress**: set **Site URL**, generate or reuse an **API key**, click **Download Plugin**, upload the zip on the WordPress site, then activate the plugin

5. Optional: configure pre/post import queries on the **Queries** tab

6. Use **Test Connection** in the host editor (SSH + DB, or WordPress REST)

7. On a host card, click **Backup** or open the **⋮** menu for Edit, Duplicate, or Delete



### WordPress host (quick path)

1. **+ Host** → connection type **WordPress**

2. **Site URL** — e.g. `https://example.com` (must match the live site URL)

3. **Generate Token** (once) → **Download Plugin** → upload `.zip` in WordPress admin

4. **Save Host** so the token is stored in the vault (re-download uses the same token)

5. **Test Connection** — should pass ping, preflight, and database query

6. **Backup** / **Import** work like other hosts; credentials come from `wp-config.php` on the site



For plugin and REST details, see [`wordpress/dback-db-tools/wordpress_agent.md`](wordpress/dback-db-tools/wordpress_agent.md).



### Restore

1. Open **Backups** → filter by host if needed

2. Select a backup file

3. Choose a destination host

4. Click **Import to Selected Host**



### App data export/import

1. Open **Settings** → **Export** tab

2. **Export App Data** — enter an export password

3. **Import App Data** — enter the export password for encrypted bundles



### Remote sync (S3)

1. Open **Settings** → **Sync** tab

2. Enter S3 endpoint, bucket, and credentials → **Save**

3. Click **Test Connection** — on success, **Push** and **Pull** appear

4. **Push** — uploads encrypted app data to `dback/app-data.json`

5. **Pull** — downloads the remote bundle, confirms, then merges into this device

6. Scroll to **Sync log** at the bottom to see last push/pull times (stored locally only)



## Why is it fast?



- **Direct streaming** — data flows from database to file without intermediate storage

- **SSH path** — uses `mysqldump` / `mariadb-dump` on the server when available

- **WordPress path** — plugin streams gzip SQL over HTTP (PDO or mysqli fallback; no full-file buffering)

- **Smart compression** — prefers Zstandard (`zstd`) when available on SSH hosts

- **No temp files by default** — SSH tmp-file fallback only when streaming fails



## About



Created by **dariush vesal**.



- Email: `dvworkmail2017@gmail.com`

- GitHub: [github.com/devlifeX/dback](https://github.com/devlifeX/dback/)



## FAQ



### Why does DBack require Vulkan/X11 libraries on Linux?

DBack uses **Gio**, a GPU-accelerated GUI toolkit. On Linux, Gio renders through Vulkan and creates windows via X11/Wayland, which requires development headers at build time.



### Which platforms are supported?

- **Linux desktop** — primary platform; use `./run.sh`, `./build.sh`, or download `dback-linux` from GitHub Releases

- **Windows** — `dback-windows.exe` is built on tagged releases via GitHub Actions; build locally with `go build` on Windows

- **macOS / Android** — not supported in this release



Remote **SSH/Docker/Jump** targets must run **Linux**.



**WordPress** hosts only need a WordPress site with the DBack DB Tools plugin installed (any PHP/MySQL hosting; no SSH required on the server).



### What happened to PostgreSQL and CouchDB?

Removed. DBack now supports **MySQL and MariaDB** only.



### What happened to separate Export/Import settings per profile?

Profiles are now independent **hosts** with a single connection. Legacy dual settings are migrated automatically on first load.



### What is included in remote sync?

The same data as **Export App Data**: hosts, templates, backup history metadata, activity logs, and sync settings. Backup `.sql.gz` files and local sync timestamps (last push/pull) are **not** uploaded.



### Can I use MinIO or a self-hosted S3 endpoint?

Yes. Enter the host (with or without `https://`) and port, set **Use SSL** as needed, and provide bucket credentials. The remote object path is always `dback/app-data.json` inside your bucket.



### How does WordPress backup work?

DBack embeds the **DBack DB Tools** plugin, injects your host API token into the zip, and talks to `https://your-site/wp-json/dback/v1` for export, import, query, ping, and preflight. The plugin uses pure PHP (no shell commands), suitable for shared hosting.



### Where is the WordPress plugin source?

[`wordpress/dback-db-tools/`](wordpress/dback-db-tools/). Developer docs: [`wordpress_agent.md`](wordpress/dback-db-tools/wordpress_agent.md). Go app architecture: [`agent.md`](agent.md).