Connect to MySQL
Connect to MySQL or MariaDB on this server, by host name or IP address, or through an SSH tunnel.
2 minutes to set up.
Full and incremental backups of MySQL and MariaDB, sent to a folder, FTP or the cloud, with an email after every run.
Protect your data in just a few minutes.
Detailed tutorialConnect to MySQL or MariaDB on this server, by host name or IP address, or through an SSH tunnel.
Choose the databases you want to backup. One job can include several databases.
Store backups on local drives, FTP/SFTP, Amazon S3, Microsoft Azure, Google Drive and more.
Choose when and how often the job should run. Full and incremental backups.
Get notified on success or failure by email, Slack, Teams, Discord or a webhook.
Click Run Now to start your backup job and verify the results.
It runs the standard MySQL tools for you on a schedule and keeps every copy in a folder, on FTP or in the cloud.
A full backup is an open SQL script. You can open it and see the database structure and the data that was backed up.
An incremental backup saves only the changes since the previous one. It finishes quickly and keeps the load on the server low.
The main MySQL and MariaDB releases are supported: MySQL 5.6, 5.7, 8.0 and 8.4, and MariaDB 10.6, 10.11 and 11.4.
Restore from the same window. The SQL script and the incremental backups that follow it are applied in order, so the chain comes back as one job.
Point it at your databases, then choose where the backups go. Schedule, compression, encryption, retention and email are all switches on the same form.
Local, remote or cloud-hosted.
Pick one destination or several. Click any of them for the setup steps.
Start free. Upgrade only when you need more features.
All plans: SQL Server, MySQL & PostgreSQL; remote/Azure SQL/RDS; files & folders; log shipping; unlimited Run Now backups.
View all plansTry risk-free. Get a full refund within 30 days, no questions asked.
Your data and payment information are always safe.
The community forum is open to everyone. Direct email support comes with an active Full-Service subscription, and those emails are answered within one business day.
Contact supportSQLBackupAndFTP is a backup solution for SQL Server, MySQL, and PostgreSQL databases that performs scheduled full, differential, and transaction log backups, supports incremental backups for MySQL and PostgreSQL, backs up files and folders, compresses and encrypts backup files, stores them locally, on a network, FTP/SFTP server, or in the cloud, automatically removes old backups based on retention policies, and sends email notifications on backup success or failure.
SQLBackupAndFTP is made to be simple. While for the majority of users this is a huge advantage, some specific configurations are not handled. You should not use SQLBackupAndFTP if you want to monitor SQL Server performance and schedule backups online in your browser for a large number of servers - SqlBak may be suited better for you.
No. SQLBackupAndFTP is a standalone application: once you have bought a license for a computer, it never expires and you can keep using the version you purchased forever. Only the optional Full-Service subscription renews yearly, and one month of it is included with every license.
Discounts apply automatically at checkout: 15% off from 2 computers, 20% off from 5, and 25% off from 10. The “Professional 1 database” edition is sold in packs of 5, with its own 20% discount starting at 20 computers. Above fifty computers, write to us and we will quote a price.
Yes. Full MySQL backups are made with mysqldump and restored with mysql; both tools come with the application. Incremental backups copy the MySQL binary logs.
Yes. Connect to a MariaDB server the same way as to MySQL: server name, port, user name and password.
Yes, with full backups: connect over TCP/IP or through an SSH tunnel. Incremental backups read the binary log folder, so for them SQLBackupAndFTP must be installed on the MySQL server.
Only for incremental backups. Full backups with mysqldump work without it. See how incremental backups use the binary log.
Yes. Enter a new database name when you restore, or create a restore job that connects to another MySQL server. Testing the restore is good practice, so you know the backup can be recovered.