Native MySQL and MariaDB backups
SaveState coordinates the database-aware export and encrypted backup as one Windows workflow.
- Engines
- MySQL and MariaDB
- Plaintext dump file
- Not written to disk
- Credentials
- Windows Credential Manager
Application-consistent data instead of a live-directory copy
Copying a running database data directory—even from a stable volume snapshot—does not by itself guarantee a logically consistent database. SaveState instead invokes the installed native dump tool with transaction-safe settings and streams its output into the encrypted Kopia repository.
The app detects compatible XAMPP, MariaDB, and MySQL tool installations. A database profile cannot be saved until its connection has been tested successfully.
Choose the exact recovery scope
A profile can protect every non-system database, selected databases, or selected tables from one database. Native routines, events, triggers, binary values, and UTF-8 data are included by default; compatible MariaDB tools can also include users and grants.
Restore data is streamed from the encrypted snapshot into the selected native database client. Customers should still rehearse restores against an isolated database after upgrades or material schema changes.
- Auto-detects native dump and restore tools
- Supports scheduled, retained, and manual database backups
- Keeps the database password out of the connection URL and project files
Put this feature into a recovery plan
Install SaveState on Windows, protect a representative data set, and test the restore before it is urgent.
Choose a plan