Export configuration
SQL Backup Master provides the ability to export program configuration.
This feature is useful when you need to copy (or move) your SQL Backup Master configuration to another machine, or if you simply want to create a portable backup of your settings.
See the import configuration help topic for further details.
Master password (v8.5 and later)
Beginning with v8.5, an exported configuration is saved as a password-protected .sbmconfig file. When you export, you'll be asked to choose a master password (minimum 12 characters). The export is encrypted with this password, so the same password is required to import the file – on this machine or any other.
.sbmconfig file itself as sensitive, since anyone with both the file and the password can read its contents.Why export/import is required to move configuration
Also beginning with v8.5, the secrets in your saved configuration (cloud storage credentials, database and account passwords, and stored authorization tokens) are encrypted in a way that is bound to the machine that created them. As a result, you can no longer migrate settings by copying the underlying configuration files between machines – the encrypted secrets won't load on a different host. The password-protected export is the supported way to move (or back up) your configuration. For a fuller explanation, including disaster-recovery considerations, see Configuration Backup and Recovery.
What's Being Exported?
The resulting export configuration file includes backup job, scheduled report, and global settings configuration data. It does not include cloud authorization tokens – for security reasons, OAuth-based destinations (Dropbox, Google Drive, OneDrive, Box, etc.) must be re-authorized after the configuration is imported on the target machine.