MySQL Point

Backing up MySQL tables have a mixed night mare for me has always been. When it comes to the Win32 version is a client application, which had a claim that we were existing customers of Saturn, smearing our brain too. Finally, all conditions were met.
The requirements were that all triggers Proceedures and functions, and a table Defenition, permissions, data must be saved. The backup and restoration should be at maximum efficiency. Triggers are not activated if the restoration is complete.
Taking into account all the above points, it was finally decided, with a suggested solution, proceed as follows. The structure of the tables were analyzed using SHOW CREATE TABLE and law to create a specific markup with a table, formatted to change a load of data in the file, and a series of tables.
Given tables with mixed types, which are only InnoDB tables, and other MyISAM, InnoDB, all tables to InnoDB tables are converted after the data have been filled if there is evidence (it should) and even primary key auto_increment, are constructed after the data is completed. The data are taken in a CSV file with select into outfile. The triggers are drawn from the data folder as files and copied to a temporary folder.
The point where we break our heads were the functions and procedures, based on mysql connector/v5 we had with delimiter unsupported, and finally what we were doing, the proc table in the MySQL database dump with the same basic method was. All the resulting files with some meta-information with a zipper.
If the recovery has been developed, we were faced with another problem that the TRG not simply drop the files selected, the trigger, but we needed to start the MySQL server.
Finally, everything is good and the customer is satisfied. Backups are a full backup. But for the progressive, it would be preferable to activate the service replication and mysqlbinlog use. exe.
We at Saturn is inspiring and leading people in more open source solutions.