SQL Backup Master Help

Online Documentation

Azure Storage SQL database backup destination

SQL Backup Master supports the use of Microsoft Azure Storage for database backup purposes.

To use Azure Storage as a backup destination, you must have a Microsoft Azure account. If you don't already have a Microsoft Azure account, you can visit their website in order to create one.

To create an Azure Storage backup destination within SQL Backup Master, click the Add toolbar button in the Destinations section of the Database Backup Editor window. When prompted to choose a destination, select Azure Blob Storage and click the Select button.

Account Settings

In order to upload database backup files on your behalf, SQL Backup Master requires the following information:

  • Account and access key - These can be found in the "Access Keys" area of your Azure storage account.
  • Container - You can use an existing storage container that you've already created (through the Azure portal) or enter the name of a new container and it will be created automatically.
  • Endpoint - By default, SQL Backup Master will use the standard Azure Cloud service endpoint (core.windows.net). Here you can select an alternate sovereign cloud endpoint (Azure China Cloud, Azure German Cloud, Azure US Government Cloud) or type a custom endpoint suffix, if needed.
  • API version - The Azure Blob Storage service API version to use. Leave this set to [Latest] (the default) unless an older service version is required for compatibility reasons.
  • Access tier - The Azure Blob Storage access tier (Hot, Cool, Cold, or Archive) to apply to uploaded backup files. Leave this set to [Default] to use your storage account's default tier. Access tiers differ in cost and retrieval terms – please review Azure pricing before selecting an option here. In particular, note that backups stored in the Archive tier cannot be downloaded (restored) until they have been rehydrated to an online tier.

Important: SQL Backup Master will not use your Azure Storage authentication information for any purpose other than those directly required by the application (e.g. uploading, downloading, listing, and cleanup of database backup files). This information is stored (associated with the backup job) in encrypted form, and is never transmitted to any other external party.

Optional Settings

The following optional settings are also available:

  • Remote dir - By default, SQL Backup Master will upload database backup files into the root of your Azure Storage container. Here, you can specify a directory name (e.g. "SQL Backups" or something similar) to use instead. If the directory doesn't already exist, it will be created. You can also specify multiple sub-directories by separating them with a forward slash (e.g. "Apps/SQL Backups").
  • Emergency destination - When this option is enabled, the associated backup destination will be used only if all other backup destinations fail.
  • Enabled backup types - Controls which backup types (Full, Differential, Transaction Log) are sent to this destination. At least one type must remain enabled.

Note that all file transfers to and from Azure Blob Storage are always performed over secure (HTTPS) connections.

Cleanup

Each time SQL Backup Master successfully uploads a database backup to a destination, it executes a clean-up procedure.

This allows you to automatically remove database backup files that are older than a specified number of days and/or hours.

Important: Cleanup operations for a given destination will only affect the database backup files associated with that destination.