Zoë Kron via discuss <[email protected]> writes: > To conclude a good working solution: > > The data dir is on an LVM. Binlog location is set to the same dir but > with ".bin" as subfolder. > There you can do LVM Snapshots. > > - innodb_flush_log_at_trx_commit=1 > - sync_binlog = 1 (if binlog is enabled)
Agree. > - sync_master_info = 1 (if slave) If you are using GTID on the slave (Master_use_gtid=slave_pos|current_pos, the default), then you shouldn't need sync_master_info=1, the slave position is stored in an innodb table. (Though sync_master_info=1 is still fine of course, unless it ends up hurting your performance.) > If I tar.gz the whole Snapshot I effectively need about the same size > to be able to sync it off. > Which for one or two TB is not the end of the world. For a 100 TB > Datadir this is not good > anymore. > > What is the last puzzle-piece? Do you use restic? rsync? rclone? > Incremental sync? If you're fine with a .tar.gz, then you can use the option for tar to output the file to stdout, and pipe that directly into eg. ssh to send it to a remove host without taking any local disk storage: tar zcf - your_directory/ | ssh your_remote_host 'cat > backup.tar.gz' Hope this helps, - Kristian. _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
