View Source

{page-title}{excerpt:hidden=false}Slaves are hard workers.{excerpt}
 
\\
\\
Replication Can be Paused on Slave to Allow Point-in-time backups. Long backup operations can proceed without disrupting other servers. Backup Disk I/O isolated away from customer facing servers.  A challenge some deployments experience is that for larger databases or especially those that are write intensive is that long pauses in replication required for backup using tradition tools like mysqldump or mysqlhotcopy can be problematic for the replication. 

!mysql-replica-slave-backup.jpg!\\
\\
| {color:#cc0000}Category{color} | [Legacy|TP:Categories of MySQL Backup Software] |
| Archive Type | Disk \\ |
| MySQL Storage Engines Supported | Replication Required \\ |
| Supported O/S | All \\ |
| Binlog Backup & Restore | {color:#00cc00}Yes{color} |
| {color:#000000}Zero Business Interruption (Online Backups){color} | {color:#00cc00}Yes{color} |
| Granular (Table Level) Restore \\ | {color:#cc0000}No{color}  |
| Easy to Use Graphical User Interface \\ | {color:#cc0000}No{color} |
| Complete Server Protection (Backup All Data or just MySQL?) \\ | {color:#cc0000}No{color} |
| Backup Type \\ | [Full (Incremental with Binary Logs)|TP:Backup Method - Full Backup] \\ |
| {color:#cc3300}Backup Window Length{color} \\ | {color:#cc3300}Long{color} {color:#cc3300}Replication Pauses Can be Problematic{color}\\ |
| {color:#00cc00}Server Disk I/O and Load Impact{color} \\ | {color:#00cc00}No impact on live servers\!{color}\\ |
\\