Ok, so I wanted to look into the new compression options of MEB 3.10.
And I would like to share my tests with you. Remember, they’re just this, tests, so please feel free to copy n paste and obtain your own results and conclusions, and should I say it, baselines, in order to compare future behaviour, on your own system.
An Oracle Linux 6.3 virtual machine with 3Gb RAM, 2 virtual threads, on a 1x quad core, windows laptop. Not pretty, but hey.
So, these tests are solely about backup. I’ll do restore when I get some *more* time.
In addition to my recent post, I just had to go into using the –use-tts for specific tables and selective backup sets.
As all my schemas were employeesn, I thought it would be a good idea to run:
mysqlbackup -uroot --socket=/tmp/mysql.sock --backup-dir=/home/mysql/MEB/restore \
--with-timestamp --use-tts --include=employees* backup
In this post I go into some performance metrics and time spent on using MySQL Enterprise Backup instead of mysqldump, and seeing how far I could go with some parallel configuration.
Here’s a look at using MySQL Enterprise Backup in a specific example:
Consider a Backup Policy
– Full Backup of the environment.
– Complemental Incremental backups & online BinLogs.
And the Restore:
– Logical Restore.
– Online, Zero impact.
– Partial, single database, group of tables.