DBA::Backup::mysql MySQL server extension for DBA::Backup
Download

DBA::Backup::mysql Ranking & Summary

DBA::Backup::mysql Tags

database Perl module MySQL backup MySQL backup database backup

DBA::Backup::mysql Description

MySQL server extension for DBA::Backup The DBA::Backup::mysql module is not used directly. It is a server extension for the DBA::Backup module. See the instalation directions for more information.NOTICE! This is currently a broken partial port from the origal working MySQL specific module. I hope to have the port finished and a functional version uploaded soon. Email me or the list for more information.The mailing list for the DBA modules is perl-dba@fini.net. See http://lists.fini.net/mailman/listinfo/perl-dba to subscribe.mysql_flush_logsUses mysqladmin refresh to flush all logs and tables.mysql_rotate_logsRotates the binary update, error and any extra mysql logs specified in the conf file. Rotation of binary and error logs is not optional on runs when the databases get backed up. Error and binary logs are kept as incrementals. Other logs are just appended, and are cleared and restarted once over a certain size (as defined in conf)._rotate_error_log() The mysql error logs don't operate the same way as the other logs. As of mysql 4.0.10, every flush-logs command will cause the error log to rotate to a file with an "-old" suffix attached. This is regardless of the file's size. Mysql shutdown/startup will *not* rotate the error log to the -old file. Any previous -old file is deleted. This function attempts to restore some sanity to how mysql treats the error log. Call this function after the flush-logs command. We will take new -old file and append it to the end of our own file, (different name) and delete the -old file. We'll then call the usual _rotate_generic_log function on it._cycle_bin_logs() Issues command to mysqld to finish writing to the current binary update log and start writing to a new one. We then push all of the bin-logs (except for the newest one) into /00/. The flush logs command causes mysqld to close the old (already renamed) general query and slow query logs and reopen the logs of the usual file name. It also causes mysqld to flush the binary update log and begin writing to a new binlog file. It does not affect the error log, only a restart of mysqld will start a new error log. The flush hosts command will clean up the hosts cache._backup_databases() Backup all databases on the server DBMS which are mentioned explicitly or as a pattern in the section in the config file. This function will dump all specified databases to .sql.gz files in the directory /new/. If there were no errors during backup, _rotate_dump_dirs will then rename it /00/. If this function encounters errors during backup, the partial dumps to /new/ will remain until the next time this function is executed. At that time, the contents of /new/ will be destroyed and new dumps will be placed there. At no time are binary update logs ever placed in /new/. Return with the number of errors encountered during backup. Requirements: · Perl

DBA::Backup::mysql Related Software