Automating SQL Server Backups on Windows: Why You Need It and How to Do It

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.

Continue reading Automating SQL Server Backups on Windows: Why You Need It and How to Do It

How to Automate MySQL Database Backups in Windows

Preservation of data is an essential part of any business. Losing a database, such as a customer list, could effectively be the end of a company. The primary way to protect your data is to regularly back it up.

In this article, we will explain how to automate regular backups for MySQL on Windows. If you use Linux, check out this article: How to Automate MySQL Database Backups in Linux.

Continue reading How to Automate MySQL Database Backups in Windows

How to clone SQL SERVER database to a Test Environment

It doesn’t matter if a company is large or small, almost every database administrator needs to maintain a copy of the production databases in a test environment for testing and development needs.

All you need to do for this is to copy the databases from the production server to a test server, and this can be done in different ways. Let’s take a look at them. Continue reading How to clone SQL SERVER database to a Test Environment

How to automate maintenance of your databases

Maintenance of your databases is as important as regular backups. Once scheduled backups are set, the thought may appear that your data is safe and sound and it is, until a problem appears.

As a rule, databases don’t crash completely, but there may be a sharp decrease in performance because of server laсk of disk space or any other issues that can corrupt databases. That’s why it’s highly recommended not only to perform regular backups of your databases but also maintain them. Continue reading How to automate maintenance of your databases

How to backup and restore Amazon RDS SQL Server

Amazon RDS SQL Server is a cloud database from Amazon, one of its differences from classic SQL Server is the way it performs backups. RDS SQL Server does not support the T-SQL BACKUP DATABASE construction but instead offers several other approaches such as restore point-in-time, snapshots, native backup to S3, and Export Data-tier Application.

Here are ways to perform a backup and restore:

  1. Snapshot creation
  2. Native backup to S3
  3. Export bacpac\dacpac
  4. Via SQLBackupAndFTP

Continue reading How to backup and restore Amazon RDS SQL Server

Scheduled Restore. How to Set Up Log Shipping

Log Shipping is SQL Server technology that is available in both the Standard and Enterprise editions. The technology may be useful in solving the following problems:

  1. Creation of read-only servers to perform heavy SQL queries and reduce the load on the primary server
  2. Creating backup servers that can be quickly put into operation in the case of a primary server failure
  3. Creating a secondary (slave) server, where data is updated with a fixed delay

Continue reading Scheduled Restore. How to Set Up Log Shipping

[JOB-BAK:1301#1] Failed to backup database. There is no destination selected to keep Full database backup type

If you get the following error message during a backup:

[JOB-BAK:1301#1] Failed to backup <database name> database with "Full" backup type: Failed to backup <database name> database. There is no destination selected to keep Full database backup type. Continue reading [JOB-BAK:1301#1] Failed to backup  database. There is no destination selected to keep Full database backup type 

[DST-1:1001#103] Destination error: Could not find a part of the path

Typically, the following error message:

Destination error: Could not find a part of the path 'y:\1'.
Trying again...
Destination error: #[DST-1:1001#103] Failed to connect to the Folder destination. > Failed to create folder "y:\1". > Could not find a part of the path 'y:\1'.

Continue reading [DST-1:1001#103] Destination error: Could not find a part of the path