You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Coder...@googlegroups.com
在备份之前,先看看专业选手提出的问题,看完并去搞清楚自已的环境,对大家都很重要。
Does the backup require shutting down MySQL? If not, what is the
impact on the running server? Blocking, I/O load, cache pollution, etc?
What technique is used for the backup? Is it mysqldump or a custom
product that does something similar? Is it a filesystem copy?
Does the backup system understand that you cannot back up InnoDB by simply copying its files?
Does the backup use FLUSH TABLES, LOCK TABLES, or FLUSH TABLES WITH READ LOCK? These all interrupt processing.
What other effects are there on MySQL? I’ve seen systems that do a
RESET MASTER, which immediately breaks replication. Are there any FLUSH
commands at all, like FLUSH LOGS?
How does the system guarantee that you can perform point-in-time recovery?
How does the system guarantee consistency with the binary log, InnoDB logs, and replication?
Can you use the system to set up new MySQL replication slaves? How?
Does the system verify that the backup is restorable, e.g. does it run InnoDB recovery before declaring success?
Does anyone stand behind it with support, and guarantee working,
recoverable backups? How strong is the legal guarantee of this and how
much insurance do they have?