mysqldump and pg_dump Command Builder

Build safe backup and restore commands for MySQL with mysqldump or PostgreSQL with pg_dump, with compression, retention and a cron schedule.

Free · No sign-up · Your inputs stay in your browser

Input

Build mysqldump and pg_dump commands

DatabaseHostUserBackup directory

Schema only

Output

Commands

616 characters

# Backup (credentials from ~/.my.cnf [mysqldump] section, never on the command line)
mysqldump -h 127.0.0.1 -u backup --single-transaction --quick --routines --triggers --events --hex-blob --set-gtid-purged=OFF app_production | zstd -q -T0 -c > "/var/backups/db/app_production_$(date +%F_%H%M).sql.zst"

# Restore
zstd -dc "/var/backups/db/app_production_YYYY-MM-DD_HHMM.sql.zst" | mysql -h 127.0.0.1 -u backup app_production

# Keep 14 days
find /var/backups/db -name 'app_production_*.sql.zst' -mtime +14 -delete

# crontab: every night at 02:15
15 2 * * * mysqldump ... (the line above) 2>> /var/log/db-backup.log

--single-transaction gives a consistent snapshot of InnoDB tables without locking them, and --quick streams rows instead of buffering each table in memory. pg_dump's --compress=zstd needs PostgreSQL 16 or later. A backup is only real once a restore of it has been tested.

Runs in this browser. Nothing you paste is sent to a server.

About this tool

Method, assumptions, practical next steps, and limits.

The flags that matter

For InnoDB, --single-transaction takes a consistent snapshot without locking tables and --quick streams rows instead of buffering whole tables in memory; --routines --triggers --events include stored code that is otherwise skipped. For PostgreSQL, the custom format (-Fc) is compressed and lets pg_restore run in parallel and restore single tables. See the pg_dump reference.

Credentials and testing

Passwords on the command line show up in the process list and shell history; use ~/.my.cnf or ~/.pgpass with mode 600. A backup is only proven by a restore: restore into a scratch database on a schedule, and alert if it fails.

Frequently asked questions

How do I back up a large MySQL database without locking it?

mysqldump --single-transaction --quick works for InnoDB tables without locks. For hundreds of gigabytes, a physical backup such as Percona XtraBackup or MySQL Enterprise Backup is much faster to restore.

How do I restore a single table from a pg_dump backup?

With a custom-format dump: pg_restore -d dbname -t tablename backup.dump. Plain SQL dumps cannot be restored selectively without editing the file.

Is what I paste sent anywhere?

No. The tool runs entirely in your browser with JavaScript. Nothing you type or paste is sent to our server or stored.

mysqldump and pg_dump Command Builder

Build mysqldump and pg_dump commands

Commands

The flags that matter

Credentials and testing

Frequently asked questions

Similar tools

MySQL InnoDB Tuning Calculator

PostgreSQL EXPLAIN ANALYZE Reader

UUID Generator