- Check the log of the latest backups for your database in Minion.BackupLogDetails. Compare the logged backup tuning values that were used (NumberOfFiles, Buffercount, MaxTransferSize, and Compression) against the settings you expect to be used from Minion.BackupTuningThresholds.
- Check if you have disabled dynamic tuning for that database, or for all databases. Check the DynamicTuning column in Minion.BackupSettings.
- Perhaps you have not set a threshold that includes your database at its present size. Check Minion.BackupTuningThresholds to determine that:
- rows are defined for your database (DBName, BackupType)
- the rows for your data the appropriate rows are active (IsActive=1),
- your database is larger than the threshold you’re expecting it to use (SpaceType, ThresholdMeasure, ThresholdValue). One common mistake is to omit a “floor” value of zero for a particular database; this causes that database to use the MinionDefault values in Minion.BackupTuningThresholds, instead.
FAQ: Why isn’t MB using my backup tuning thresholds? Print
Created by: Sean McCown
Modified on: Thu, Jul 12, 2018 at 10:23 AM
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.