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.
Continue reading Solved: [JOB-BAK:2006#11008] Previous Full backup of a database was created with a different application
If any live server goes offline, an administrator has to be notified. Many companies use some third-party services to do that. But what if your SQL Server service crashed for some reason? Will you be notified right away or will find out after many lost sales and transactions? What if SQLBackupAndFTP itself crashed (while extremely rare, but everything happens) – how would you know your backups are not being done?
Service down alerts option in SQLBackupAndFTP covers all of these cases. If you enable it from the main screen (see the image on the right), an email will be sent to you in the following cases:
- If your server is down or
- If your SQL Server or MySQL is down or
- If the SQLBackupAndFTP service is down
If you need to email to multiple recipients – as usual, just separate it by a comma. You need a paid plan with a Full-Service subscription to use this option.
When you encounter an issue with SQLBackupAndFTP, to understand the problem better our support team may ask you to send us the log file. This post explains how to enable the log and send it to us. Continue reading How to send Log to developers
Even though Azure SQL Database provides built-in backup, you may still want to create a local copy of your Azure SQL database. This could be handy for example when you want to keep database backup copy for free longer than allowed by Microsoft Azure built-in tools which are usually 7 to 35 days, depending on your service tier. Here we will explain in detail how to backup Azure SQL Database to a Local Machine.
Continue reading How to backup Azure SQL Database to Local Machine
You can run scheduled backups of a remote SQL server using SQLBackupAndFTP. The standard BACKUP DATABASE command would not work on a remote SQL Server, so scripts would be the only option. Scripts are not as good as *.bak files because they are larger, do not support differential backups, and should be used only if you do not have an option to create *.bak files. If you want to know more – read a good explanation of why remote SQL backups are such a pain. Continue reading How to backup remote SQL Server database using SQLBackupAndFTP
This step-by-step guide helps a user having a Microsoft Azure account to create Microsoft Azure SQL Server on Linux (Ubuntu) (free license) and to use the SQL Server on Ubuntu with an SSH terminal. Continue reading How to Deploy Azure SQL Server on Ubuntu (Free Lisense)
We were scammed out of a few thousand dollars last month by a fake “affiliate”. Here’s how. Continue reading How we fell for an affiliate scam
By default SQLBackupAndFTP stores backups in file names like DatabaseNameYYYYMMDDHHMM.zip (eg Pubs201801011120.zip). But you can also use custom file names if you have such needs Continue reading Customize backup file name
If you have an active Full-Service subscription, then by default your mail server is set to Automatic (it is actually sent through our servers) and you don’t need to configure anything. But if you use a free version of SQLBackupAndFTP, or your subscription has expired or you just want to configure your own mail servers – below are the instructions on how to do so. Continue reading How to send SQL Backup confirmations through my GMail, Hotmail or Yahoo account