If you specify a password in the “Encrypt compressed files” section, then the backup files will be encrypted.
Ivan Gusev
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.
SqlBak Guide: SQL Server Differential and Transaction Log Backups
Differential and transaction log backups are available only for local SQL Server connections. If you backup SQL Server using SqlBak, then you can add differential or transaction log backups to your backup plan in the “Advanced backup schedule” settings.
SqlBak Guide: Which databases should be chosen in a backup job?
In one database management system, there can be multiple databases. When creating a backup job, you can choose which databases specifically need to be backed up. The backup of each database will be made independently from the other databases and placed in a separate archive.
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.
SqlBak does not store your backups on its servers. Backups are sent directly from your server to the storage location.
SqlBak Guide: Optimizing Backup Job Execution Time
For large data volumes, backup job execution can take a lot of time. However, there are several tricks that can help optimize the time.
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!
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.
5 ways to reduce SQL Server backup size
SQL Server backup is a page-by-page physical copy of the database files. And, generally, the size of a backup is about the size of the database. However, there are several ways to cut the backup size substantially.
Reducing the backup size has the following benefits:
How to backup and restore SQL Server on Linux
In this article, we will describe how to create a backup of a SQL Server that is installed on Linux.
How does SQL Server create a backup?
You can create a SQL Server backup by running the T-SQL command BACKUP DATABASE.This command saves the backup file to a specified directory. SQL Server backups are created quickly because it requires just copying data from the database files to the backup file.
When creating a backup, you do not need to stop SQL Server or switch it to single-user mode, and the database continues to work as usual during this operation.