Just as you can export your backup job configuration, you can also import it.
When using the Import configuration tool, you'll be prompted for the location of your configuration file.
Next, you'll be asked whether you're copying your backup job configuration from one machine to another, or permanently moving it.
•I'm copying it - Use this option if you are leaving the existing SQL Backup Master installation (the one you exported from) running.
•I'm moving it - Use this option if you are permanently moving the SQL Backup Master configuration to a new machine (and retiring the existing instance).
•Cancel - Cancel the import operation.
If you're not sure which option to use, select the "I'm copying it" option.
Important: When you import a backup job configuration, any existing backup job configuration will be permanently overwritten.
When you elect to copy (rather than move) your SQL Backup Master configuration, the import process will take steps to ensure that the current instance of SQL Backup Master doesn't interfere with any existing instance. For example, you wouldn't want multiple SQL Backup Master instances trying to perform backup pruning operations on the same set of database backup files.
When you elect to move (rather than copy) your SQL Backup Master configuration, it indicates that you're permanently migrating that configuration from one machine to another. In this case, the new instance will essentially pick up where the other left off by taking over database backup pruning operations, etc.