How far away you need to copy it depends on several factors, but at least ensure it is not in the same suburb. So, ensure you are copying your backups off site. Even if it is a once a century event, do you want to run the risk? Is it likely to happen? Fortunately not, but from time to time really bad things happens: fires, earthquakes, flooding, etc. Think in terms of a major disaster such as the entire data center gone. You cannot assume that a backup that is kept locally on the same host or even in the same data center will be available when you need it.
Mysql enterprise backup restore examples how to#
There are two parts to this: can you retrieve your backups even in the worst case scenario, and do you know how to restore your backups? In a little bit, I will show what the recommended way to create an online backup in NDB Cluster is. A backup method may work when the database is idle, but not when concurrent writes are occurring. When you test your backups make sure that you make changes to the data while the backup is running. It does not work either to use mysqldump unless you keep the cluster read-only for example by putting the cluster into “single user mode” and locking all tables. With respect to MySQL NDB Cluster, I can mention that rsync of the NDB file system will not work, neither will any other method of creating a binary backup from the file system (including MySQL Enterprise Backup). It sounds pretty obvious – why would you ever use a backup solution that does not work? Obviously no one does that on purpose, but unfortunately it is too common that it has not been checked whether the backup solution is appropriate. Use a Backup Method that Works with Your Product They are not exhaustive either, but more meant as something guidelines to have in mind when designing your backups. The best practices mentioned here are by no means unique to MySQL NDB Cluster nor even databases. So, before actually creating and restoring a backup, let us look at two best practices when it comes to backups.