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.
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
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
If you backup large SQL Server databases with the help of SQLBackupAndFTP then we want to give you some useful recommendations that may speed up the backup process. Continue reading Recommendation on how to Backup Large Databases with SQLBackupAndFTP
Working with SQL Server you face a lot of different error messages. Some of them can be solved in a minute, others required more time. In this blog post, we are going to talk about error messages like “BACKUP LOG cannot be performed because there is no current database backup.” Here is a full error message:
Msg 4214, Level 16, State 1, Line 1 BACKUP LOG cannot be performed because there is no current database backup. Msg 3013, Level 16, State 1, Line 1 BACKUP LOG is terminating abnormally.
All users who’re working with SQL Server sooner or later face with the following error message:
Msg 4305, Level 16, State 1, Line 1 The log in this backup set begins at LSN 42000000037600001, which is too recent to apply to the database. An earlier log backup that includes LSN 42000000034400001 can be restored. Msg 3013, Level 16, State 1, Line 1 RESTORE LOG is terminating abnormally.
The best way to protect your database is to make schedule backups. You can do it with the help of SQLBackupAndFTP, SSMS, or T-SQL Commands. But when you try to restore your database you can receive some errors. In this article, we will show how to solve the next error: “The database was backed up on a server running version”. You can get this error message during the restoration process. Here is the text of the error message 3169:
Msg 3169, Level 16, State 1, Line 1 The database was backed up on a server running version 13.00.0801. That version is incompatible with this server, which is running version 12.00.4213. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally.
In this post, we are planning to talk about how to make SQL Server backup system databases. The easiest way is to use the simple tool – SQLBackupAndFTP. Planning the backup process should really be one of the points that are crucial in the life of any DBA.
Such simple procedure will definitely save you tons of time and effort in the future. Continue reading SQL Server Backup System Databases
If you are looking for a tool to backup and restore SQL database then use simple tool SQLBackupAndFTP. The most typical jokes you’ll discover when mentioning about one particular important responsibility for a DBA goes like this – a Database Administrator requires one of two things, a great backup or an ideal resume. It’s real. If you’re not performing backups and making sure that you can recover databases from those backups, you’re exposing yourself and your company to information loss. Continue reading Backup And Restore SQL Database
If you have a database in the OFFLINE state and these databases are scheduled to be backed up, their backup will fail and the whole backup job will be shown as Failed. Same when you use Database Mirroring, you may have databases in Restoring state and they can’t be backed up either. If you have such databases included in your backup job, you may want to skip them if they are in an Offline or Restore state and show the whole job as Success, not Failure. Continue reading How to skip databases in Offline state in SQLBackupAndFTP