This article will address the issue of backup encryption, why it is important, and the various approaches available. Why encrypt backups? Application-level encryption and “always encrypted” Simple backup encryption (7zip) SQL Server backup encryption Creating a certificate IMPORTANT: certificate backup Creating a backup with built-in encryption in SQL Server Restoring an encrypted SQL Server backup … Read more
In this article, various methods of monitoring backups and restores of SQL Server databases will be discussed, including tracking current progress and history. Tracking the status of your initiated backup If you initiate a backup yourself, you can instruct SQL Server to log the progress status by adding the WITH STATS parameter to the BACKUP … Read more
When you perform SQL Server backups on an industrial scale, it is easy to get confused with the created backup files, as the backup itself consists of binary data, making it impossible to understand by simply opening it in a text editor. In this article, we will look at what SQL Server offers to avoid … Read more
This simple guide will help you create backups of SQL Server on Linux.
The only noticeable difference is in the graphical tools.
SSMS is the main tool for SQL Server and is only available on Windows. Connecting from Windows to SQL Server on Linux is not always possible due to port security (1433). You will have to use the command line utility sqlcmd and T-SQL commands.
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:
Log shipping in Microsoft SQL Server is an automated solution for master-slave replication based on the transfer of transaction logs from primary to secondary servers. This process ensures continuous database cloning while minimizing the load on the primary server.
To perform a SQL Server backup is very simple — it can be done in 5 clicks via SSMS. But the topic of backups in SQL Server is deep.
Take a seat, young Padawan, for this article will be your first step toward becoming a Jedi Backup Master.
Creating backups of a SQL Server database is one of the most critical aspects of maintaining a system. There are various tools available for creating backups, such as SQL Server Management Studio, SqlBak, and SQLBackupAndFTP. However, performing backups via the command line interface can provide even more flexibility and customization options.
PowerShell and batch scripts can be used to perform SQL Server backups via the command line interface. PowerShell scripts offer advanced functionality, while batch scripts are simpler and easier to use. Command line backups provide more flexibility and customization options than GUI-based tools.
This article provides an overview of the process involved in performing SQL Server backups via the command line interface and discusses the advantages of using PowerShell and batch scripts.
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.
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.
