MySQL database backup plan
Note that mysqlbackup is not a hot backup solution. For databases the size of your one, there really is no debate; see the related Q &amp; A Mysql backup strategies?

As Shlomi Noach (GitHub's MySQL guy) says in his answer, Percona's XtraBackup is your go-to choice. It is also worth reading MySQL Backup and Restore Best Practices by Krzysztof Ksiazek.

By the way, no backup strategy on earth will protect you from devs/DBAs deleting records/dropping tables, that's why you should be using incremental backups; maybe LVM snapshots or flush logs. However, incremental backups are also performed by XtraBackup. See also Example Backup and Recovery Strategy in the MySQL reference manual.

On a more general note, broad approaches to this issue are discussed in:


Database Backup and Recovery Best Practices by Ali Navid Akhtar, Jeff Buchholtz, Michael Ryan, and Kumar Setty
Backup and Recovery Best Practices by Omelchenko Alexander


In any case, on a production system, devs (or DBAs for that matter) should not be wandering through the filesystem and/or database deleting stuff ad libitum. Any and all changes on production should have been performed at least twice on test/UAT or similar systems before being implemented in prod! This is best practice.