Lastro

Your own copy of every database.

Lastro backs up the MySQL databases you look after — on the days and at the time you choose, compressed, verified and kept for as long as you say — while it waits in the Windows tray.

Download from the Microsoft Store Windows 10 and 11, x64

12:30, on the dot: one read-only snapshot, streamed straight into a compressed file.

It keeps the good backups

It keeps the schedule

What it copies, and how

One snapshota single read-only transaction: no lock on InnoDB tables, nothing written on the server
Everythingtables and rows, views, procedures, functions, triggers and events — the file mysqldump would write
TLS, SSHdirectly, with Amazon RDS checked against Amazon’s own certificates; or through an SSH tunnel with your key
gzip, zstd, agecompressed to open anywhere, or smaller and faster; encrypted with a passphrase if you choose
S3a copy in any S3-compatible bucket — AWS, R2, B2, Wasabi — uploaded once verified, and retired with the original
HeidiSQLyour sessions imported — hosts, users, passwords and tunnels

What it refuses to do

Questions

How do I restore a backup?

Create an empty database and load the file into it. The file names no database, so it restores under any name — which is also how you try one out without touching the original:

gunzip -c portal_2026-10-06_1230.sql.gz | mysql -u root -p portal_test

A .zst file opens with zstd -dc instead, and an encrypted one with age -d, on any system, with the passphrase and nothing of Lastro’s. For a tool that cannot read compressed files, Extract .sql, beside each backup in the history, writes the plain SQL next to it, for HeidiSQL, DBeaver or phpMyAdmin to open.

What does Lastro need on the server?

Only a user that can read. Create a read-only user for Lastro, where you add a database, gives you the SQL for one that can read exactly what a backup reads — SELECT, SHOW VIEW, TRIGGER, EVENT — so the master password never has to be on your desktop.

Nothing is installed on the server. MySQL inside an EC2 instance that only listens to itself is reached through an SSH tunnel, with Windows’ own OpenSSH and your key.

Why only the Microsoft Store?

Because there Microsoft signs Lastro, and Windows trusts what Microsoft signed at once. Offered as a download from this page, the same program was unsigned, and Windows' SmartScreen and now and then an antivirus warned about it, as they warn about any new program nobody has signed. For a backup tool, a false alarm costs the trust it lives on.

The Store also installs Lastro and brings its updates; Lastro looks for none itself. A copy installed from this page before keeps working and no longer updates itself: install Lastro from the Store, and it offers to take the old copy out, keeping your list of databases.

Does Lastro send anything anywhere?

No telemetry, no analytics, no account. Lastro connects to the servers you added, to their SSH hosts if you use tunnels, and to the buckets you named for copies, if any. Nothing else on its own: new versions come from the Microsoft Store, and Lastro does not look for them itself.

A webhook, if you set one, receives the same warnings a notification shows: the name you gave the database, what happened and when — and the server’s own messages only if you ask for them.

Report…, in About, sends a problem or an idea to whoever makes Lastro, and only when you press Send, having seen all that goes: what you wrote, the version and, unless you switch them off, the Windows version and a few facts about this Lastro, such as its language, how many databases it backs up, the servers' versions and the kind of their last failures. What Lastro adds never includes a host, a database's name, a user, a path or a file.

Can I take my list to another computer?

Everything lives in one readable JSON file, %APPDATA%\Lastro\config.json. Copy it across and every database arrives with its schedule and folder — but not its password, which Windows sealed for your user on the first computer. Type each one again and it is sealed anew.

An empty lastro.portable file beside the executable keeps the configuration in the same folder instead.

Which servers, systems and languages?

MySQL 5.7, 8.0 and 8.4, and MariaDB 11.4: every change is tested by backing up an awkward database on each of them, restoring the file with the stock client and comparing the two row by row. Amazon RDS hosts are recognised and connected to over verified TLS. Windows 10 and 11, x64.

English, Português, Español, Deutsch, Français, Italiano, Polski, Русский, 中文, 日本語 and 한국어, following your Windows display language, with a choice in the preferences. Next: PostgreSQL.

Lastro is free. If it has kept a copy of something you needed, a donation helps keep it that way.

Donate