soulen3
commented
5 years ago holland bk --maint
Holland 1.1.12 started with pid 4137
--- Starting backup run ---
Creating backup path /var/spool/holland/default/20190208_120722
Estimating size of mysqldump backup
Estimated Backup Size: 671.52KB
Using Historic Space Estimate: Checking for information in /var/spool/holland/default/newest/backup.conf
Last backup used 163.14KB
Adjusting estimated size to last backup total * 1.1: 179.46KB
Starting backup[default/20190208_120722] via plugin mysqldump
Requested maintenace backup, set 'file-per-database' to False
* Finding and excluding invalid views...
* Invalid and excluded views will be saved to /var/spool/holland/default/20190208_120722/invalid_views.sql
Using mysqldump executable: /usr/bin/mysqldump
mysqldump version 10.2.21
Using mysqldump option --flush-privileges
Using mysqldump option --routines
Using mysqldump option --events
Using mysqldump option --max-allowed-packet=128M
Using gzip compression level 1 with args
Executing: /usr/bin/mysqldump --defaults-file=/var/spool/holland/default/20190208_120722/my.cnf --flush-privileges --routines --events --max-allowed-packet=128M --lock-all-tables --all-databases
Final on-disk backup size 162.77KB
24.24% of estimated size 671.52KB
Backup completed in 0.14 seconds
Released lock /etc/holland/backupsets/default.conf
--- Ending backup run ---
This allows users to create a one off backups without purging existing backups. This will also cause the mysqldump plugin to run with
file-per-database = false. This could be useful for user's that want to dump and load their databases without effecting existing backups.