In SQL Backup Master, destinations represent the storage services to which database backup files are uploaded when a database backup executes.
You are free to specify as many destinations as you wish for a given backup job. Database backup files (created when the job executes) will be sent to each enabled destination, which can provide a useful degree of redundancy (e.g. if one destination upload fails, others will still be attempted).
When multiple backup destinations are specified, a database backup (as a whole) will be considered as having failed only if all destination uploads fail. If only one destination upload fails, the job will be flagged as having completed with errors. In either case, specific details about what (if anything) failed will be available in the backup logs.
To add a backup destination, click the Add toolbar button within the Destinations section of the Database Backup Editor window. You can also use the toolbar buttons to Remove, Enable, or Disable selected destinations.
Important: Removing a backup destination will prevent SQL Backup Master from helping you to recover any database backups that may have been uploaded to it in the past - though you can always still recover such backups manually.
When a SQL Backup Master backup job executes, backup files will be sent to destinations in the order in which they appear in the Destinations listing on screen.
You can use the Up and Down toolbar buttons to control the order in which destinations are processed.
The remainder of this help chapter will discuss the following specific backup destination types:
•Google Storage (S3 compatible)
•Backblaze (S3 compatible)
•Wasabi (S3 compatible)