Database Backup Recommendations

Organizations are unique and adopt database and backup solutions according to specific requirements. This section provides an overview of several best practices to implement for external databases and to ensure backups execute in alignment with your particular needs.

External Databases

For customers using an external database, Vasion recommends separating the external database from other services and applications. Having other services running on the same server as the Virtual Appliance database could impact resources and performance and cause complications if a need arises to revert to a previous Host version, backup, or snapshot.

The Virtual Appliance Host builds require specific MySQL versions to function correctly. Customers using an external database must stay within the supported MySQL versions in the Compatibility Chart. Having an outdated MySQL version or updating past the supported versions impacts performance, and the Virtual Appliance will not work as expected.

If you are hosting the MySQL database on a separate server, during the initial configuration's Setup Database page select I will provide a MySQL8.0+ database outside of the Virtual Appliance, and complete the connection details in the provided field.

External databases simplify disaster recovery and connecting upgraded Host versions to the existing database. When hosting your own MySQL server, keep in mind that multiple databases on the server, starting with app_, need to be backed up and restored together in the event of a disaster. Because of this, it is easier to make snapshots of the MySQL server than a database backup.

Backup Considerations

The recommended best practice for the Virtual Appliance with an attached storage disk (or any VM containing relational data) is to use application-consistent backups with File System Quiescence. This approach ensures you execute backups correctly, allowing the Virtual Appliance's internal database to function properly during a backup / restore scenario. If seeking optimal restoration conditions or for critical changes like a new host or appliance upgrade, we advice to gracefully shut down the Virtual Appliance and perform a backup while powered off.

Graceful Shutdown

The best way to avoid a Virtual Appliance boot failure situation is to use a Graceful Shutdown when powering off or rebooting the virtual machine. Reference Graceful vs. Forced Shutdown. When forcing the Virtual Appliance to shut down, you are not allowing the database an opportunity to complete any final writes, which could result in data loss and unexpected database behavior.

Database Backups

Run a backup rather than a snapshot after gracefully shutting down the Virtual Appliance. The database could be in the middle of writing something when a snapshot takes place, and then with a restore, you are "jumping" to another point in time where it could lose track of what it is journaling and halt itself.

Scheduled Backups

We encourage regular backups of your MySQL database, in addition to hypervisor-based backups, to mitigate data loss. When initially setting up the Virtual Appliance, you create a database username and password that you can utilize to connect the hosted database to a database backup solution. See MySQL 8.0 Reference Manual for best practices.

While your organization determines Recovery Point Objective (RPO) and Recovery Time Objectives (RTO), we advise a minimum of daily backups rolling over 14 days via automated jobs.

Conclusion

By following these best practices, you can ensure virtual machines' successful and efficient backup with MySQL databases. Implementing these recommendations will enhance data protection, minimize the risk of data loss, and simplify disaster recovery processes. As IT admins, your proactive approach to data management ensures the continuity and reliability of your organization's systems.

For further assistance or any questions, contact the Vasion Support Team.