Capturing ZRM versus InnoDB Hot Version for MySQL
Are there any significant benefits of InnoDB Hot Backup vs ZRM Snapshots in terms of disruption to the workspace, compressed backup file size and backup / restore speed in medium to large InnoDB database?
I understand that InnoDB's approach is more reliable, faster, doesn't cause significant shutdown on startup, etc.
source to share
If you want to avoid crashes on your site, the best way is to set up a slave replication server to your server and retrieve backups from it. By using this, the backup method becomes irrelevant, since the slave simply catches up with the master when replication is complete and will not interrupt the master.
You can also configure your application to use a slave to read requests to reduce the load on the master.
source to share
I am currently running with ZRM to back up a MySql server with InnoDB tables only. Based on what I've read, there shouldn't be any glitches in your application using ZRM snapshots. It does not require a read lock at any time.
I cannot comment on the size of the compressed backup files or the speed of backup / restore versus InnoDB Hot Backup b / c. I have not used both products.
Also, if you sign up to the Zmanda network, you can download some good information documents. One of them is benchmarking, which shows the backup / restore speeds using InnoDB and LVM snapshots versus other backup methods that ZRM can do.