SqlBak Blog – Backup and monitor SQL Server databases from the web

Managing the Database Backup of Multiple Servers

January 6, 2022December 8, 2021 by Ivan Gusev

While making a database backup is not a difficult task, making one the correct way can be a little more involved. So if you’re new to the process, setting up and maintaining backups on multiple servers can initially seem intimidating.

There is no one-size-fits-all solution. Choosing a good solution depends on your individual architecture, resources and security requirements. In this article, we will discuss the main approaches to managing multiple database backups, and we’ll look at the pros and cons of each approach.

Export/Import SqlBak job in a JSON file

December 17, 2021September 14, 2021 by Ivan Gusev

Starting from SqlBak app version 3.2.9, you can export a job to a JSON file and then import it using the SqlBak.Job.Cli.exe utility. This functionality is needed primarily for automated deployment of the SqlBak application and backup jobs creation. A simple tutorial on how to do this is described in the following blog post: How to deploy SqlBak app automatically.

SqlBak.Job.Cli.exe reference manual

December 7, 2021September 1, 2021 by Ivan Gusev

The sqlbak.job.cli.exe utility is a programming interface for working with the SqlBak application. It is located in the root directory where the application is installed.

This tool can be used to register the application, manage connections to DBMS, and import jobs from JSON configurations.

How to deploy SqlBak app automatically

December 17, 2021August 25, 2021 by Omelchenko Alexander

When SqlBak is installed on a large number of servers, the deployment can be automated in 3 steps:

Download and install the SqlBak app
Connect the SqlBak app to sqlbak.com and to a DBMS
Add a backup job from a JSON file

How to backup SQL Server databases to multiple destinations

November 18, 2021August 19, 2021 by Omelchenko Alexander

Storing backups only on a local disk is not a good practice, because you risk losing them if the disk becomes corrupted. It is recommended, therefore, that you send backups to multiple destinations to always be able to restore your databases. In this blog post, we will show how to create regular SQL Server backups and automatically send some of them to a local folder and some to the cloud (Azure Storage, for example) via SqlBak.

How to backup SQL Server databases on Windows

December 29, 2021August 10, 2021 by Ivan Gusev

This article looks at different ways to back up SQL Server, from classic and conventional to exotic and situational.

But first, a few words of theory.

Automated SQL Server Backups to Amazon S3 on Windows

November 19, 2021July 19, 2021 by Omelchenko Alexander

Problem

The BACKUP DATABASE command syntax allows performing backups by specifying a drive, a network folder or Azure storage as the destination. Although it is not possible to set an Amazon S3 bucket as a backup save point, you can transfer the file to S3 using a batch script or a third-party utility.

MySQL Maintenance Automation

June 24, 2021 by Omelchenko Alexander

For the MySQL database to work quickly and without interruptions, it is necessary to perform maintenance jobs from time to time. This mostly just means running a few commands, but let’s address first things first.

PostgreSQL Maintenance Automation

June 17, 2021 by Omelchenko Alexander

One of the primary responsibilities of the DBA is to create regular backups. However, maintenance of the database is not limited to this.

The mechanisms that enable a relational database to run fast are based on a complex storage system that degrades over time. It leads to a general database slowdown.

How to automatically upload MySQL backup to FTP on Linux

November 25, 2021May 17, 2021 by Omelchenko Alexander

The first thing a DBA should do after deploying a database is to ensure that backups are created regularly.

But storing a backup file on the same server where the MySQL server is located would be a big mistake. Therefore, you should create a backup and put it out of the server on which MySQL is located. The simplest solution would be to transfer it to another server via FTP.