[MDEV-20703] mariabackup creates binlog files in server binlog directory on --prepare --export step Created: 2019-10-01 Updated: 2020-08-25 Resolved: 2019-10-01 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Backup |
| Affects Version/s: | 10.2, 10.3, 10.4 |
| Fix Version/s: | 10.2.28, 10.3.19, 10.4.9 |
| Type: | Bug | Priority: | Major |
| Reporter: | Vladislav Lesin | Assignee: | Vladislav Lesin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
If mariabackup is executed with the following options:
and "path_to/my.cnf" switches on binary logs, then it will create binary logs in the directory, pointed out in "log-bin" option. If "path_to/my.cnf" is also used by the server, such behaviour can cause issues. The general issue is if "--export" mariabackup option is used, mariabackup starts the server in bootstrap mode to generate *.cfg files for the certain innodb tables. The started instance of the server reads options from the file, pointed out in "--defaults-file" mariabackup option. |
| Comments |
| Comment by Vladislav Lesin [ 2019-10-01 ] |
| Comment by Vladislav Lesin [ 2019-11-15 ] |
|
When "--export" mariabackup option is used, mariabackup starts the server in If the server uses the same config file as mariabackup, and binlog is The fix is to add "--skip-log-bin" in mysld options when the server is If mariabackup upgrade is not desirable, the workaround is to run |