maria-discuss team mailing list archive
Mailing list archive
Re: Page Compression in production and backup strategies
We use a slave to take backups from. So, stop the slave, take the backup using your tool of choice, restart the slave. Or, if you need the slave for some read only type uses perhaps, we use mylvmbackup to take a hot backup on the slave without needing to shut down mariadb slave. mylvmbackup is a free script, works well, and, requires lvm and uses snapshots. So, it’s a decent free choice for backups. The backup is easily restored, it’s just a tar archive. We use lz4 compression for great speed in the compression and minimal impact on the slave. It’s easy to restore a slave backup and even make it the master.
> On Apr 10, 2017, at 12:44 PM, Tim Kersten <tim@xxxxxxxx> wrote:
> Hi folks,
> Does anyone here use page compression (
> https://mariadb.com/kb/en/mariadb/compression/ ) in production? (Or know
> folks who do?)
> What prompted my question was seeing that XtraBackup is not supported
> when using page compression. Given the popularity of the XtraBackup, I'm
> left wondering if there's some other backup strategy people use
> (especially since it's also used to sync and provision slaves), or if
> page compression is simply not used by folks who have master/slave
> setups, or perhaps don't require backups?
> Searching has not been helpful in my finding the answer, other than a
> pull request ( https://github.com/percona/percona-xtrabackup/pull/200 )
> by Jan Lindstrom from last year.
> Hoping you can help,
> best regards,
> Mailing list: https://launchpad.net/~maria-discuss
> Post to : maria-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-discuss
> More help : https://help.launchpad.net/ListHelp