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:
If you received the following error: [JR-STATUS:520]. Job completed, but result not yet received by dashboard. Waiting for application data. This means that the backup job itself completed, but its final result did not fully reach the SqlBak dashboard on sqlbak.com. SqlBak is designed to continue working even without a connection to sqlbak.com. However, in … Read more
In the previous article, we showed how to use the SqlBak API to automate backup health checks: detecting failed jobs, offline servers, missing recent backups, and retention policy issues. The next logical step is to bring that data into Grafana so backup monitoring becomes part of your overall observability stack alongside CPU, RAM, disks, and … Read more
Database backups are often configured once and then quietly forgotten — until something goes wrong. In modern environments, teams may operate dozens or hundreds of database servers supporting ERP, CRM, and other critical systems. At the same time, they are managing many other priorities — sales, inventory, procurement, HR, production, and more — each with … Read more
Starting from version 17, PostgreSQL introduced native support for incremental backups, enabling more efficient and storage-friendly backup strategies. One of the key requirements for incremental backups is enabling WAL (Write-Ahead Log) file summarization. This article explains how to enable WAL summarization by updating PostgreSQL configuration settings. 1. Backup the Configuration File Before making any changes, … Read more
Backup is a critical part of database operations. Incremental backups can significantly reduce the performance load on a PostgreSQL server. This article covers the process of creating incremental backups of PostgreSQL on Windows, as well as restoring them. What is an Incremental Backup? An incremental backup is not a backup of the entire database, but … Read more
One of the key differences between PostgreSQL and other DBMSs is its large and diverse community, which creates a wide range of tools for working with and administering the system. This is undoubtedly a good thing, but sometimes such variety can be overwhelming — many tools exist for the same task, and it’s not always … Read more
A recovery model is a database property that determines when the transaction log is cleared. The transaction log is a binary file associated with the database, typically with the .ldf extension. It records all transactions performed by users in the database. The transaction log serves two primary purposes: Database recovery after failures. For instance, if a … Read more
Full database backups are a great thing, but creating them frequently can be inconvenient. If the database is large, the backup will also be large, and creating it can put a significant load on the server and the network when transferring the backup to storage. To avoid doing full backups all the time and to … Read more
By default, the SqlBak Docker container includes client utilities for working with databases, such as sqlcmd, mysql, mysqldump, psql, pg_dump, and pg_restore. However, these utilities may not be backward compatible with older database versions. For example, when connecting to a MySQL 8.1 database using the mysqldump utility from the Docker container, which is designed for MySQL … Read more
If your MySQL database is running in Docker, backing it up is no more complicated than backing up a database installed directly on the server. However, there are tips, tricks, and best practices that can simplify the process. Backup the database, not the container Although MySQL in Docker is ultimately just a program interacting with … Read more
