SqlBak Guide: Backup Compression
SqlBak Blog
by Ivan Gusev
1y ago
If a database that should be backed up via SqlBak is not particularly large, then there is no need to set compression options in a specific way. It is recommended to use the default values. The features below are designed to fine-tune compression for highly loaded systems and large databases. How SqlBak Works SqlBak works in the following way: Creates a backup file in a temporary folder Compresses the backup file in the temporary folder Deletes the backup file Repeats steps 1, 2, and 3 for all the databases Sends the compressed backup files to the selected destinations Deletes the compressed ..read more
Visit website
SqlBak Guide: Optimizing Backup Job Execution Time
SqlBak Blog
by Ivan Gusev
1y ago
For large data volumes, backup job execution can take a lot of time. However, there are several tricks that can help optimize the time. Parallel Execution of Backup Job SqlBak works in the following way: Creates a backup file into a temporary folder Compresses the backup file into the temporary folder Removes the backup file after the compression Sends the compressed backup file to the selected destination places Removes the compressed backup file from the temporary folder  However, it is possible to create several backup jobs (one job for each database or group of databases) and schedu ..read more
Visit website
SqlBak Guide: Backup Encryption
SqlBak Blog
by Ivan Gusev
1y ago
If you specify a password in the “Encrypt compressed files” section, then the backup files will be encrypted. Why Should Backups Be Encrypted? Backup encryption protects you from data theft. If a hacker receives access to your backup storage, he will be able to restore the backup on his server and gain access to all the data in the database. However, if the backup is encrypted, then nothing can be extracted from the file without a password. How Does SqlBak Encrypt Backups? SqlBak encrypts the backups during compression. Essentially, SqlBak simply sets the password for the backup archives. The ..read more
Visit website
SqlBak Best Practice Guide
SqlBak Blog
by Ivan Gusev
1y ago
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. Selection of databases to be backed up SqlBak does not backup the entire database management system, but each database individually. For example, databases with p ..read more
Visit website
SqlBak Guide: SQL Server Differential and Transaction Log Backups
SqlBak Blog
by Ivan Gusev
1y ago
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. Differential and transaction log backups differ from full backups in that they only backup data that have been changed. Differential backups will backup all the new data since the last full backup, while transaction log backups will backup all the new data from the moment of any backup. This fundamentally distinguishes them from full backups ..read more
Visit website
SqlBak Guide: Which databases should be chosen in a backup job?
SqlBak Blog
by Ivan Gusev
1y ago
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. Divide the list of databases into groups Typically, different databases have different requirements: backup frequency, storage duration and storage location. For example: The loss of a database with billing information for customers can completely destroy the business. But the loss of a database with logs will just be unpl ..read more
Visit website
MySQL Point-in-Time Recovery (PITR)
SqlBak Blog
by Ivan Gusev
1y ago
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 reco ..read more
Visit website
About MySQL Server Incremental Backups in SqlBak
SqlBak Blog
by Ivan Gusev
1y ago
In order to create an incremental backup, SqlBak performs binary log file backups. What are binary logs? Binary logs are files into which MySQL Server writes all data change transactions. Typically, these files are stored in /var/lib/mysql/ on Linux or C:\ProgramData\MySQL\MySQL Server 5.6 Data on Windows. The list of all MySQL Server binlog files is stored in a special binlog.index file. The transactions are recorded in the last binlog file for all databases at once in binary format. However, they can be converted to SQL statements. Re-executing these SQL statements will restore the database ..read more
Visit website
MySQL Point-in-Time Recovery (PITR)
SqlBak Blog
by Ivan Gusev
1y ago
Point-in-time recovery is the concept of restoring data to a particular time in the past. Suppose you deleted an important database spreadsheet 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 replica of the spreadsheet 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 spreadsheet 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 ..read more
Visit website
About MySQL Server Incremental Backups in SqlBak
SqlBak Blog
by Ivan Gusev
1y ago
In order to create an incremental backup, SqlBak performs binary log file backups. What are binary logs? Binary logs are files into which MySQL Server writes all data change transactions. Typically, these files are stored in /var/lib/mysql/ on Linux or C:\ProgramData\MySQL\MySQL Server 5.6 Data on Windows. The list of all MySQL Server binlog files is stored in a special binlog.index file. The transactions are recorded in the last binlog file for all databases at once in binary format. However, they can be converted to SQL statements. Re-executing these SQL statements will restore the database ..read more
Visit website

Follow SqlBak Blog on FeedSpot

Continue with Google
Continue with Apple
OR