How to backup MySQL with SqlBak

Starting from SqlBak version 3 you canĀ back up MySQL Server databases. SqlBak supports 2 ways on how you can 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 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.

First of all, you have to establish connections to your MySQL Server. To do it, run the SqlBak app, click on the “Add” button and choose “MySQL Server (TCP/IP)” as a DBMS type.

At the opened window, specify your “Server name”, “Username”, and “Password”, then click on the “Test Connection” button to make sure the connection is set.

Once the connection is set, it’s time to create a backup job. To do it, please go to your “Dashboard” page and click on the “Add new job” button.

On the next page, go to the “Select databases” section and choose all the databases you are going to back up.

The next step is to select a place where the backups should be stored.

Note, you can use multiple destinations for storing your backups.

To set a schedule for your backups, go to the “Schedule backups” section, and set the needed schedule.

We’re almost done – the last important setting is the email notification. Scroll down to the “Send email confirmation” section and specify your email address or addresses to receive the notifications about whether your backups are successful or failed.

You have set your backup job with all the necessary settings. If it is needed, you can also set encryption and compression, add local files or folders to be backed up, add custom scripts to your backup plan, and set a restore process. Once the settings are done, click on the “Save&Exit” button in the upper right corner.

That’s it – all the backup job settings are made and the backups will be performed according to the schedule.

5 thoughts on “How to backup MySQL with SqlBak

  1. Hello, I’m trying to add a stored procedure to be executed before the backup. But it is a little complicated to perform the execution because the following error is always returned when trying to “call mystored ();” :

    Job execution error: Warning: Using a password on the command line interface can be insecure.
    mysqldump: Couldn’t execute ‘show fields from `access’: Got error 28 from storage engine (1030)
    mysqldump: Couldn’t execute ‘SHOW TRIGGERS LIKE’ access ”: Got error 28 from storage engine (1030)
    ….

    and then errors are listed on all trigger calls …
    However, I verified that it is not necessary to try to make a stored procedure call for the error to occur … Just any simple operation such as “select column1 from bd1.table1;” or “select 1;”, the same errors are occurring.
    You can help me?

    mysql Ver 14.14 Distrib 5.6.49, for Linux (x86_64) using EditLine wrapper Ubuntu 18.04.4 LTS
    Linux 4.15.0-136-generic
    SqlBak application 1.1.69

      1. I’ve also encounter this error, and i have enough disk space.

        The log says,
        “The backup folder /tmp/sqlbak/Downloads/36699_20210902013001007815/ has 1.071TB free space. The temporary folder /tmp/sqlbak/Downloads/36699_20210902013001007815/ has 1.071TB free space.”

        and the next one error out with:
        “Job execution error: mysqldump: [Warning] Using a password on the command line interface can be insecure.
        mysqldump: Got errno 28 on write”

        mysql version 5.7.29

        I wonder what is the command sqlbak runs to backup, is there a way to omit the password and use the .my.cnf instead? i think that’s what causing the error, not suppose to use -p{password} directly in command line.

        When i ssh into my server and run

        mysqldump -u{user} -p{password} my_db, i got the same warnning too, but i can run
        mysqldump my_db, successfully cause it’s reading my .my.cnf file directly.

        any idea if i can make this work?

        Thanks.

Leave a Reply to Omelchenko Alexander Cancel reply

Your email address will not be published. Required fields are marked *