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.
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. More…
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. More…
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:
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:
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. More...
If the following error message happens:
[DST-1:1003#53] Destination error: Failed to open "\\networkpath\backupfolder" destination connection. > The network path was not found
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'.
During the backup you can face the following warning:
[Warning] [JOB-BAK:2006#11008]. The previous full backup of <database name> database was created with a different application (non-SQLBackupAndFTP). You may not able to restore the database automatically using SQLBackupAndFTP.
In rare cases, some operations in SQLBackupAndFTP don’t fit standard timeouts and fail. For this reason, in version 12.3.3 we added a possibility to define custom timeout values by creating C:\ProgramData\Pranas.NET\SQLBackupAndFTP\Service\Timeouts.xml with the following contents: More…