To create an Azure Storage backup destination, click the Add toolbar button in the Destinations section of the Database Backup Editor window. When prompted to choose a destination, select Azure Storage and click the Select button.
In order to upload database backup files on your behalf, SQL Backup Master requires the following information:
•Account name and key - These can be found on the "Manage Access Keys" page of your Microsoft Azure account.
•Container name - 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 default (national) Azure Storage service endpoint. Here you can select an alternate endpoint (e.g. for China, Germany, etc.), if needed.
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, download, listing, and clean up 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.
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").
•Enable secure (HTTPS) transfers - When enabled, will use a secure HTTPS socket for file transfers.
•Emergency destination - When this option is enabled, the associated backup destination will be used only if all other backup destinations fail.
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.
Important: Cleanup operations for a given destination will only affect the database backup files associated with that destination.