SQLBackupAndFTP is a versatile tool specifically developed for database backup and restoration. It enables users to create backups and restore them within the same DBMS. It also offers the capability to back up Azure SQL databases and restore them in SQL Server, and vice versa. To help you migrate data from Azure SQL to SQL Server, we have prepared a comprehensive step-by-step guide on configuring backup and restore jobs. Continue reading How to Import Azure SQL Databases to SQL Server
SQLBackupAndFTP is a utility designed for backing up and restoring databases. It not only allows you to create backups and restore them within a single DBMS, but also provides the functionality to backup SQL Server databases (local or remote) and restore them in Azure SQL, and vice versa. Below is a step-by-step guide on how to configure backup and restore jobs to migrate data from SQL Server to Azure SQL.
We all know creating backups is half the battle. Finding the right place for storage is the other half. Today, let’s see how SQLBackupAndFTP and SFTP To Go can collaborate to solve both tasks.
Continue reading Simplifying Data Protection with SQLBackupAndFTP and SFTP To Go
To perform MySQL Server incremental backups, binary logs should be enabled and correctly set. Otherwise, you will see one of the following error messages:
Failed to backup “mysql” database with “Full” backup type: [DBMS-MYSQL:11015#1] Unexpected binary log format. Current value: “MIXED”, expected value: “ROW”. Log in to the DBMS using the MySQL official client or other tools and run the statement to update the binary log format: set global binlog_format = ‘ROW’;
Failed to backup “mysql” database with “Incremental” backup type: [DBMS-MYSQL:11014#1] Binary log is not enabled. Current value of “log_bin” variable: “OFF”. Expected value: “ON”.
A script can be run via the built-in Windows Task Scheduler tool. It can be found in the “Administrative Tools” section, or by clicking Win+R and typing
taskschd.msc. Open the scheduler and in the “Actions” section select Create Task… Continue reading How to Schedule a Script via Windows Task Scheduler
To find these files, please follow these steps:
- Press win+r
- Find MySQL service Continue reading Where to find my.ini, mysql.exe, mysqld.exe, mysqlbackup.exe on Windows
Making a full database backup is very easy with
mysqldump . Details are available in this article. However, such backups are a heavy load on the database because they require a lot of space and take a long time to create. This is not acceptable for a large production database. Therefore, instead of FULL database backups, you can do incremental database backups.
Incremental backups do not contain all database data but only the data that changed since the previous backup. In this case, to restore the data, you will need the entire chain of backups. Continue reading MySQL Incremental Backups on Windows
To backup MySQL Server via SQLBackupAndFTP, you have to establish a connection via TCP/IP. In other words, SQLBackupAndFTP connects to a database via port 3306.
Assume you need to clone your server and you have an image, for example, an AMI (Amazon Machine Image) in AWS with installed SQLBackupAndFTP Free edition. Once you deploy this image on several servers and apply your license key to activate SQLBackupAndFTP, that license key will be applied to all your servers. When you decide to remove your license from one of the servers, the license will be removed from all of them. Also, you can face the issue that the license will not work if you activate a license for one server on all your cloned servers. Continue reading Command Line Arguments to Manage an Installation
A backup is a copy of data taken and stored elsewhere so that you can restore it in case of a database breakdown. The most common causes of a breakdown include the following:
- Hardware issue: The data in the database can get corrupted due to errors in the physical drives. However, it is not always physical damage to the server from the outside. Disks wear out, resulting in data read and write errors.
- Software issue: As a rule, data is written to the database by a program, in which errors may occur and lead to data corruption after updates.
- Human issue: A person with access might unintentionally damage the data. For example, they might delete data that was not supposed to be deleted.
- Hacker issue: If attackers infiltrate your system, then they will, first of all, encrypt your database and demand a ransom for decryption.