The Database Dump Engines In Akeeba Backup

Database dump engines

• Native MySQL Backup Engine: This engine will take a backup of your MySQL database using nothing but PHP functions in order to accomplish that.

• Native MySQL Backup Engine

MySQL Compatibility
This option controls the MySQL version compatibility when creating the database SQL dump file.The available options are:

• If you are backing up tables with large chunks of binary data or if you have very large chunks of text stored in the         database, the default value – 1000 rows – may cause a PHP memory or MySQL buffer exhaustion.
• Number of rows per batch:
• Size for split SQL dump files : Akeeba Backup is able to split your MySQL database dump to smaller files. This allows for an improved compression ratio and also helps avoid several problems with certain cheap hosts which put a restriction on the maximum size a file generated by PHP code can have.
• Dump PROCEDUREs, FUNCTIONs and TRIGGERs: By default, Akeeba Backup will only back up database tables and VIEWs.
• Max packet size for extended INSERTs: 

1. If the previous setting is enabled, this setting defines the maximum length of a single INSERT statement. Most MySQL servers have a configured limit of maximum statement length and will not accept an INSERT statement over 1Mb.
2.  When this is not checked, Akeeba Backup will create one INSERT statement for each data row of each table.
3. .When this option is enabled, the dump engine will create a single INSERT statement for multiple rows of data, reducing the overhead and resulting into significantly smaller backup archives.

• MySQL 4.1: Akeeba Backup will request from your database server to provide definitions (CREATE commands) in a MySQL 4.1 friendly format.
• Default: This is the recommended option.
• Blank out username/password: When enabled, Akeeba Backup will not include the username and password of database connections in the backup.
• Generate extended INSERTs: If you get memory outage errors during the table backup, it is advisable to lower this setting. This is especially true if    your MySQL and PHP combination does not allow a cursor to be effectively created and all data has to be transferred  in PHP’s memory.
• No dependency tracking: When this option is enabled, Akeeba Backup’s database dump engine will no longer try to figure out table and VIEW dependencies.
• Blank out username/password: When enabled, Akeeba Backup will not include the username and password of database connections in the backup.
• Generate extended INSERTs:

1.  When this is not checked, Akeeba Backup will create one INSERT statement for each data row of each table.
2. When you have lots of rows with insignificant amount of data, such as banner and click tracking logs, the overhead of the INSERT statement is much higher than the actual data.
3. When this option is enabled, the dump engine will create a single INSERT statement for multiple rows of data, reducing the overhead and resulting into significantly smaller backup archives.

• Max packet size for extended INSERTs: If the previous setting is enabled, this setting defines the maximum length of a single INSERT statement.
• Size for split SQL dump files: Akeeba Backup is able to split your MySQL database dump to smaller files. This allows for an improved compression ratio and also helps avoid several problems with certain cheap hosts which put a restriction on the maximum size a file generated by PHP code can have.
• Number of rows per batch: Dumping table data happens in “batches”, i.e. a few rows at a time. This parameter defines how many rows will be fetched from the table at any given time.
• Dump PROCEDUREs, FUNCTIONs and TRIGGERs: By default, Akeeba Backup will only back up database tables and VIEWs. If your host supports this, you can also back up and restore advanced aspects of your database: stored procedures, stored functions and triggers.

• Author
• Recent Posts

Document Team

Hi,
We're document team, we write document for all products from our company. You can reach our Document Portal. If you have any questions or problem during using our products, feel free drop comment, we will come to help you shortly.

Latest posts by Document Team (see all)

• JS Jobs Data Dictionary: How to Add New Entity? - January 3, 2017
• JS Jobs Categories: How to Add New Categories? - December 30, 2016
• JS Jobs Message System: Front End Messages - December 30, 2016