Documentation for the SqlBak product is currently under development. We apologize for any inconvenience.
While the documentation is being finalized, you can reach out to us through our support service, and we will strive to respond to your inquiry within a few hours.
Below is a list of articles from our blog where you can find useful materials on using SqlBak:
SSH (Secure Shell) is a method of secure data transmission over a network.
Administrators often encounter it when connecting to a Linux server by entering the command ssh userName@hostAddress, which allows them to execute commands on the remote server.
However, it is primarily a protocol, and on top of it, you can not only transmit data but also create SSH tunnels, allowing applications to transfer data over SSH.
Targeted at DBAs, this article offers an overview of CLI utilities for MySQL backup. The commands described can be implemented in Linux Shell (.sh) scripts, as well as in Windows cmd (.bat) and PowerShell (.ps1) scripts. In addition to creating backups, dumps and exporting data, we’ll also delve into MySQL restore commands.
A MySQL dump is a file that contains SQL commands, which, when executed, would lead to the recreation of the MySQL database at the moment of the dump’s export. Essentially, a MySQL dump database is a logical MySQL backup database.
mysqldumpis a utility that creates a MySQL dump. It is part of MySQL and MariaDB and gets installed alongside the MySQL client.
因为有几种方法可以在Windows上备份MySQL数据库，本文将回顾所有不同的选项，以便您选择适合您的方法。本文仅限于Microsoft Windows服务器上的MySQL数据库备份。如果您使用的是基于Linux的操作系统，请参阅如何在Linux中自动化MySQL数据库备份。
本博客文章所述解决方案适用于任何 Linux 发行版：Ubuntu、Red Hat、Open SUSE、CentOS、Debian、Oracle Linux 等。然而，包安装命令可能会有所不同。
自动备份 MySQL 服务器数据库对于防止数据丢失至关重要。要正确自动化备份，您需要按照以下步骤执行：
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 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.
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!
Incremental backup is a backup that only contain data that has changed since the previous backup, not including all the data in the database.
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.
