Several settings tables – including Minion.BackupSettings, Minion.BackupSettingsPath, and Minion.BackupTuningThresholds – provide a MinionDefault / All row to provide settings for databases that do not have specific settings defined. In this way, there is a base level default that allows Minion Backup to function immediately upon installation.

We made a design decision to “keep in the scope” once any database-specific settings were defined. In other words, once the configuration context is at the database level, it stays at the database level. Therefore, if you define a database-specific row, you must be sure that all backup types are represented for that database.

The reasoning behind this rule is this: It takes a conscious act (inserting a row) to change settings for a specific database. So, we don’t want the system to “fall back” on default values, possibly countermanding the intended configuration for that particular database.

For more information, see “Backup tuning threshold precedence” in the in-product help (Minion.HELP).