MySQL Database Advanced Settings - Automatic Backup Scheduler for MySQL
Automatic Backup Scheduler for MySQL
> Help Document
> Task Wizard
> MySQL Database Advanced Settings
MySQL Database Advanced Settings
Advanced Settings contains Source Settings ( Source Server ), Destination Settings ( Destination Server or File ), InnoDB, Statements, Insert, Master and Slave and Others. We advise you to use the default values.
Reset to default
- Source Settings: It only works for the source server.
- Flush tables before starting: Flush tables in server before backing up or restoring. Check the option to maintain data consistency. Please uncheck it, if you want to allow others access the source server when backing up or restoring.
- Lock tables before starting: Locks all tables across all databases. This is achieved by taking a global read lock for the duration of the whole backing up or restoring. Check the option to maintain data consistency. Please uncheck it, if you want to allow others access the source server when backing up or restoring.
- Sorts each table's rows by primary key: Sorts each table's rows by primary key, or first unique key, if such a key exists. Useful when dumping a MyISAM table to be loaded into an InnoDB table, but will make the dump itself take considerably longer.
- Quote names within '`' characters: Quote table and column names with backticks (`).
- Set connection character set: The MySQL server automatically set the character set for connect the characters. It's used for nonEnglish ( German, French, Italian, Russian, Chinese, Japanese, Korean, etc. ).
- SET TIME_ZONE as UTC: SET TIME_ZONE = '+00:00' to allow it of TIMESTAMP data when a server has data in different time zones or data is being moved between servers with different time zones.
- Flush MySQL log files before starting: Flush MySQL logs file in server before backing up or restoring. Please note that if you export many databases at once, the MySQL logs will be
flushed for each database exported.
- Net buffer length: The buffer size for TCP / IP and socket communication.
- Max allowed packet: The maximum packet length to send to or receive from server.
- Single transaction ( InnoDB ): Creates a consistent snapshot by exporting all tables in a single transaction. Works ONLY for tables stored in storage engines which support multiversioning ( currently only InnoDB does ); the dump is NOT guaranteed to be consistent for other storage engines. While a Single transaction dump is in process, to ensure a valid exported file ( correct table contents and binary log position ), no other connection should use the following statements: ALTER TABLE, DROP TABLE, RENAME TABLE, TRUNCATE TABLE, as consistent snapshot is not isolated from them. Option automatically turns off Lock tables before starting.
- Continue even if an error occurs during running: Continue even if we get an SQL error.
- SELECT...FROM...WHERE: Export only the selected records base on the WHERE statement. For example, `id` > 100 AND name LIKE "Mike %".
- Destination Settings: It only works for the destination server, including SQL files and MySQL server.
- Add CREATE DATABASE statement: Add a CREATE DATABASE statement before each exporting to the output.
- Add LOCK TABLES statement: Add the LOCK TABLES and UNLOCK statements around INSERT statements to the output.
- Add DELETE all records statement: Add a DELETE all records statement before each create to the output.
- Add DROP TABLE statement: Add a DROP TABLE statement before each create to the output.
- Add SET NAMES default_character_set: Add the 'SET NAMES default_character_set' statements to the output.
- Add SET SQL_NOTES: Add the SET SQL_NOTES statements to the output.
- Add SET UNIQUE_CHECKS ( InnoDB ): Add the 'SET UNIQUE_CHECKS' statements for exporting the InnoDB databases.
- Add SET AUTOCOMMIT ( InnoDB ): Add the 'SET AUTOCOMMIT' statements for exporting the InnoDB databases.
- Add SET FOREIGN_KEY_CHECKS ( InnoDB ): Add the 'SET FOREIGN_KEY_CHECKS' statements for exporting the InnoDB databases.
- Fields terminated by: Fields in the output file are terminated by the given string. The default character is comma (,).
- Fields enclosed by: Fields in the output file are enclosed by the given character. The default character is double quote (").
- Fields optionally enclosed by: Fields in the output file are optionally enclosed by the given character. The default character is forward quote (').
- Fields escaped by: Fields in the output file are escaped by the given character. The default character is backslash (\).
- Lines terminated by: Lines in the output file are terminated by the given string. The default character is line breaks (\r\n).
- Use complete INSERT statements: Use complete INSERT statements to the output ( INSERT [INTO] <table> [column] VALUES [data_values] ).
- Use INSERT DELAYED statements: Insert rows with INSERT DELAYED syntax.
- Use INSERT IGNORE statements: Insert rows with INSERT IGNORE syntax.
- Use REPLACE instead of INSERT statements: Use REPLACE syntax instead of INSERT statements. REPLACE works exactly like INSERT, except that if an old row in the table has the same value as a new row for a PRIMARY KEY or a UNIQUE index, the old row is deleted before the new row is inserted.
- Surround the INSERT statements with ALTER TABLE table_name DISABLE KEYS: Add the DISABLE KEYS statements to avoid the primary keys and foreign keys check when restoring.
- Use multiple-row syntax some rows per INSERT statements: Use multiple-row INSERT syntax that include several VALUES lists.
- Master and Slave :
- Make a slave server from the master server: Export a SQL script to create a MySQL slave server from the master server.
- Add 'STOP SLAVE' and 'START SLAVE' statements: Add the 'STOP SLAVE' and 'START SLAVE' statements to the output.
- Make a new slave server from the original slave server: Export a SQL script to create a new slave server from the original slave server.
- Include master host and port: Add 'MASTER_HOST=<host>, MASTER_PORT=<port>' to the output.
- Delete master logs after running: Delete logs on master after backing up.
- Allow creation of column names that are keywords: Allow creation of column names that are keywords ( e.g. TABLE ).
- Dump binary columns ( BINARY, VARBINARY, BLOB, BIT ) using hexadecamal notation: Dump binary strings (BINARY, VARBINARY, BLOB) in hexadecimal format ( e.g 0xFE62696E... ).
- Surround all of statements with comment ( /*!40100...*/ ): Surround all of statements with comment ( /*!40100...*/ ) in the output.
- Add FLUSH PRIVILEGES statement: Emit a FLUSH PRIVILEGES statement after backing up or restoring the mysql database. This option should be used any time the dump contains the mysql database and any other database that depends on the data in the mysql database for proper restore.
: Reset all of the Advanced Settings to the default values.
- Task - Back up MySQL databases to the SQL files
- Task - Back up MySQL databases to the other server
- Task - Back up a MySQL database to the other database
- Task - Restore MySQL databases from the backup files
- Task - Restore MySQL databases from the other server
- Task - Restore a MySQL database from the other database
- Task - Execute SQL Script
- Page - MySQL Server
- Page - Source Server and Database
- Page - Destination Server and Database
- Page - Select Databases
- Page - Select Source Items
- Page - Add Backup Files
- Page - Recovery Databases
- Page - Backup Files
- Page - Upload Backup Files
- Page - Execute SQL script before starting and after ending
- Page - Enter SQL Script
- Page - Task Scheduler
- Options - Backup File Settings
- Options - Compression Options
- Options - Back up Tablespaces
- Options - SMTP Options
- Protocol - SSL Protocol
- Protocol - SSH Tunneling
Copyright © 2017 Database Think Software. All rights reserved.