I’ve been giving presentations at work each week about MySQL DBA topics. An hour of speaking about the things one does on a daily basis is rather fun, and hopefully spreads the work about how efficient MySQL is to administer and setup, as well as optimize and troubleshoot vs MSSQL and Oracle – for which we also have weekly classes.
Recently I’ve been covering backup and recovery methods, which brings me to my next point – the talkback scripts I have been integrating into my Monolith application. These scripts are wrappers for mysqldump that do extensive error checking for file completion, directory pruning to rotate out old backups per the backup retention period policy, and then report back via email and to a separate database for tracking purposes.
Here is the create table for the reporting aspect. Note: this is part of the Monolith 1.2 release which is still in beta. Stay tuned for the release that includes this, as well as remote backup, graphing for many MySQL utilization properties, alerting, and this section: the talkback local backup scripts.
mysql> show create table hosts_incoming_backup_state\G
*************************** 1. row ***************************
Table: hosts_incoming_backup_state
Create Table: CREATE TABLE `hosts_incoming_backup_state` (
`id` bigint(20) NOT NULL auto_increment,
`host_id` bigint(20) NOT NULL,
`process_status_id` varchar(255) NOT NULL,
`file_name` varchar(255) NOT NULL,
`file_size` bigint(64) NOT NULL,
`exec_time` bigint(32) NOT NULL,
`exec_compress` bigint(32) NOT NULL,
`Creation_time` datetime NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=latin1
1 row in set (0.00 sec)
