Guide to Setting Up Permissions for Database Backup and Restore

In order to create database backups through SqlBak or SQLBackupAndFTP, the user specified when adding the connection must have sufficient privileges to perform the backup operation. Although you can use a superuser to create a backup without any problems, it is considered best practice to create a separate user specifically for this purpose.

Below are examples of SQL scripts for creating a backup user, as well as the necessary privileges for database recovery.

Please note that it is not necessary to grant recovery permissions immediately. This can be done when you need to restore the database.

Read more

SqlBak Best Practice Guide

This guide contains recommendations for setting up a SqlBak backup job. This information has been developed and collected over years of interaction with SqlBak users. There will be no theory and formulas, only practical advice.

Note that these practices are not the only solutions. They are suitable in most cases, but can be fundamentally wrong under various circumstances.

Let’s consider the steps that are used to set up a backup job.

Read more

SqlBak Guide: Backup Storage Selection

SqlBak supports sending to 16 different storage types. In one job, you can specify multiple backup storage locations, and for each storage location, you can specify the duration of backup storage on it.

Note:
SqlBak does not store your backups on its servers. Backups are sent directly from your server to the storage location.

Read more

MySQL Point-in-Time Recovery (PITR)

Point-in-time recovery is the concept of restoring data to a particular time in the past.

Suppose you deleted an important database table at 2 p.m. on a Wednesday. You realize this fifteen minutes later and you need to restore the data. Replication will do you no good, because the table in the replica has also been deleted. Only backups can save the day.

However, if you back up your data at 1 a.m. every day, the closest recovery point to when the table was deleted will be at 1 a.m. that Wednesday. When you restore data, you will lose 13 hours of data. But if you use the point-in-time recovery strategy, you can recover data as of 1:55 pm, losing only 5 minutes!

Read more

About MySQL Server Incremental Backups in SqlBak

What are incremental backups?

Incremental backup is a backup that only contain data that has changed since the previous backup, not including all the data in the database.

Why are incremental backups needed?

Incremental backups allow performing backups much more frequently, as they are much smaller in size. However, to restore from an incremental backup, not only the incremental backup file is required, but also the entire preceding chain of backups.

Read more