Connect to your Azure SQL databases
and send backups to
Any Azure SQL
Supports Single and Elastic Pool databases
On Any Linux
Supports all popular Linux distributions (Ubuntu, CentOS, Debian, etc.), Docker and Raspberry Pi
On Any Windows
Compatible with any version of Windows and any Windows Server
Set a backup schedule
Create a backup schedule specifying when and how often the backups should be created.
Set the backups retention period
Store the backups for as long as you need. You are only limited by the available space in your storage.
If a failure occurs, the data can be restored with the click of a button.
- Zip and 7Zip compression
- Rest API
- Connection and configuration of new backup jobs via CLI
- Automatic restore to another Azure SQL
- Command-line interface to run the backups through a batch file
- Maintenance jobs
- Email notifications
- Local folders backup
How it works
Install an app
Install a lightweight app on your Windows or Linux server and connect to your database and SqlBak account. Then forget about it – it will run as a background service.
Schedule a backup job online
Create a new backup job on SqlBak.com. Set encryption, compression and notifications. Select any of your cloud storages to send your backups there. Schedule it.
Manage backups on multiple servers
Connect to any number of servers and see all your backups on a single page.
Your backups are secure
The backups are protected
Your backups are encrypted and uploaded to your storage directly from your server, bypassing SqlBak.com
The credentials are safe
Your database connection credentials are encrypted and stored on your server, not on SqlBak.com
We are the creators of SQLBackupAndFTP - the original SQL Server backup utility with over a million installations since 2008
Frequently Asked Questions
How does SqlBak make Azure SQL backups?
SqlBak makes Export Data-tier Application. The output is a BACPAC file. To ensure transactional consistency, SqlBak can create a temporary snapshot of a database.
Why should I create backups if Azure already does them?
There are several reasons:
- Azure stores backups only for 7 days. If you need to roll back to an earlier date, then you cannot do this through the built-in backup mechanism.
- Azure keeps backups on its own, and there is no way to download them. While convenient, it is safer to store backups separately from the database.
- Azure does not allow you to restore backups somewhere other than Azure. Via SqlBak you can restore Azure database backup to the SQL Server.
Does SqlBak support databases that are located in the Elastic Pool?
Yes. However, the information that a database was in the Elastic Pool is not saved. Therefore, during the restore process, the database will be restored to the elastic pool only if a database with the same name already exists there.
How can the backups that were created via SqlBak be restored?
It is very easy to do. All you need is to select a backup that should be restored from a list and press one button. SqlBak downloads all the needed backups and restores them. Here's a simple guide on how to restore a database.
Can the backups be sent to different destinations?
Yes, this is the correct way to store the backups. Don't put all your eggs in one basket. SqlBak makes it very easy to set up. See How to backup SQL Server databases to multiple destinations. In addition, you can mark a destination as an emergency one in SqlBak. In this case, the backups will be uploaded to it only if the backups could not be transferred to the main destination.
Is it possible to backup local folders along with databases?
Yes, while setting up a backup job, you can select any number of local folders for which the backups will be performed along with the databases.
Can the Azure SQL databases be automatically restored to another server?
Sure, it can be achieved by configuring the "Restore tasks" in your backup job. After the restore, you can run a SQL script in the restored database, for example, to delete confidential data. That option is very useful for setting up a test server.