Because there are several ways to backup MySQL database on Windows, this article will review all the different options so that you can select the method that works for you. This article is limited to MySQL database backups for a Microsoft Windows Server only. If you are using a Linux-based OS, see How to Automate MySQL Database Backups in Linux.
When you face any issues with SqlBak our support team may ask you to send the Advanced Log. Below is a short tutorial on how to do this.
Starting from SqlBak version 3 you can backup MySQL Server databases. SqlBak supports two ways to connect to your MySQL databases: phpMyAdmin and TCP/IP. Below you can find a step-by-step tutorial on how to backup your MySQL Server database via a TCP/IP connection. To backup MySQL Server databases, SqlBak uses the mysqldump utility. For now, with SqlBak on Windows, only full MySQL backups are available.
There are two types of people: people who do back up their files, and people who need to start doing it.
If you are not backing up your MySQL databases yet, you should start before you lose your precious data.
Making backups is necessary, but doing this with large databases may involve high server load and using up storage space. And only creating a backup once a day or once a week could lead to losing hours of work. So how can you make backups more often without overloading the server? Incremental backups can help you with this.
Below is a short tutorial on how to enable binary log in Linux.
No matter what IT project you are creating, you will always need a sandbox for testing and development. If your product has a MySQL database, then you will need to create a database in a development environment.
With the help of SqlBak, you can backup your remote SQL Server databases according to your schedule. A standard BACKUP DATABASE command doesn’t work on a remote SQL Server — only scripts can be generated. If there is a choice between script generation or performing backups in *.bak files, it is always recommended to run the standard BACKUP DATABASE command to get *.bak files. Scripts have some drawbacks: they are larger and do not support differential and transaction log backups. A more detailed explanation about remote backups can be found in the following blog post.