Most of the options are self-explanatory and are covered in detail in the User Guide. Go straight to Backup → Create Backup → Schedule Backup, and you will be presented with the following dialog:ĭepending on the cluster type, the options might be different, as shown in the following screenshots for PostgreSQL and MongoDB: With ClusterControl, scheduling is pretty straightforward. We have covered this chapter in detail in our whitepaper, The DevOps Guide to Database Backups for MySQL and MariaDB. The list of questions could be longer depending on your backup and restoration policy. Generally, by answering those questions, we can come up with an appropriate backup strategy. Do you trust backup storage? Encryption might be a good idea to protect your data.How to ensure the integrity of the created backup? Remember, a backup is not a backup if it’s not restorable.What if the backup server is down during the backup time? Should it failover the backup to another available host? Skipping a backup due to a maintenance window is usually not a good idea.Better compression requires higher CPU usage. Decide whether compression is needed and the compression level you can afford. How much free space do you have to store your backup? Backups tend to eat a lot of space.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |