Home

MySQL Enterprise Backup User`s Guide (Version 3.12.1)

1. 118 Legacy Partial Backup Options Besides the legacy options some other options are also discussed below but the information is only for using the options together with the legacy partial backup options For an overview of partial backups and usage examples for these legacy options see Making a Partial Backup with the Legacy Options e include REGEXP This option is for filtering InnoDB tables for backup The InnoDB tables fully qualified names are checked against the regular expression specified by the option If the REGEXP matches db_name table_name the table is included The regular expression syntax used is the extended form specified in the POSIX 1003 2 standard For example include mydb t 12 matches the tables t1 and t2 in the database mydb mysqlbackup throws an error when the option is used without a regular expression being supplied with it This option only applies to InnoDB tables created with the MySQL option innodb_file_per_table enabled which is the default setting for MySQL 5 6 and after in which case the tables are in separate files that can be included or excluded from the backup All tables in the InnoDB system tablespace are always backed up When no InnoDB table names match the specified regular expression an error is thrown with a message indicating there are no matches Default Backs up all InnoDB tables Note E This option does not filter non InnoDB tables for which options li
2. ccce cece ce eeeeeee cece ee ee ae ee eee ee sete ee aa aaa ee eeeeeeeeaaaaaaeeeeeeeeeaeaaaaees 46 4 13 Selective Extract of Single Directory ccceceeeeeee ee eeeeeeee cece tees aaaaeeeeeeeeeeeeaeaaeaeeeeeeeeeeaeaaeneeeeeees 47 4 14 Dealing with Absolute Path Names 0 cccceeeeceeceeeeeeeeeeeeeeaeaaeeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaaaeneeeeeeeees 47 4 15 Single File Backup to a Remote Host c cceeceeeeeee ee ee eee eeee sees ee ee aa ea teense eeeeeeaaaaaeeeeseeeeeeaeaaeaees 47 4 16 Single file Backup to a Remote MySQL Server cceceeeeeeeeeeeeeeeeeeeeeeeaaeeeeeeeeeeeeeeaaaaeeeeeeeeeees 48 4 17 Stream a Backup Directory to a Remote MySQL Server ccccececeeeeeeeeeeeeeeeeeaeeaeeeeeeeeeeeeaeaaeaees 48 4 18 Creating a Cloud Backup On Amazon S3 0 ccececece ee eeeeeeee eter eee e ee aa eee eeeeeeeeceaaaaeeeeeeeeeeeeaaaaenees 49 4 19 Creating a Cloud Backup on an OpenStack Object Storage ccceeeeeeeeeee esac ae eeeeeeeeeeeeeeaaeaeeees 49 4 20 Extract an Existing Image from Amazon S3 Cloud Storage to Backup Directory s 49 4 21 Optimistic Backup Using the Option optimist ic time YYMMDDHHMMSS wiceeceeeeeeeeeteeeeeeeeeeeeeeeaes 50 4 22 Optimistic Backup Using the Option opt imistic time now wieeeeececcssceeeeeeeeeeeeeaeeaeeeeeeeeeeeeaeaaeeees 50 4 23 Optimistic Backup Using the opt imistic busy tables Option 0 eceeeeeeeeeeeeeeeeeeneeeeeeeeees 50 4 24 Optimistic and Partia
3. ccceeeceeeeeeeeeeeeeeeeeeeeeaaaaeeeeeeeeeeeeaeaaanees 170 E 9 REZ LICENSE twice ieee ede ae ea ec ee eee ated eee ee ANN 170 E 10 RegEX Spencer Library License ccceceeeseeeeeeeeeeeece ae ee eeeeeeeeeeeeaaaaeeeeeeeeeeeeaaaaeeeeeneeeees 171 E 11 RFC 3174 US Secure Hash Algorithm 1 SHA1 License 0 ccceeeeeeeeeeeeeeeaeeneeeeeeeeeees 171 RUAA ETE aT cass leit sxe Ace E E EE E O EA ET A E E E E TA 172 MySQL Enterprise Backup Glossary 0 ccecceeeeeeeeeee eter eee ee te eter tesa stts ttrt ttnt attt tt turnt nn tatn nn rnrn annann nennt 173 143 144 Appendix A Frequently Asked Questions for MySQL Enterprise Backup This section lists some common questions about MySQL Enterprise Backup with answers and pointers to further information Questions e A 1 145 Does MySQL Enterprise Backup work with MySQL Server version x y 2 e A 2 145 What is the big ibdata file that is in all the backups e A 3 145 Can back up non InnoDB data with MySQL Enterprise Backup A 4 146 What happens if the apply log step is interrupted e A 5 146 Why is the option defaults file not recognized e A 6 146 Can back up a database on one OS platform and restore it on another one using MySQL Enterprise Backup A 7 146 What if have included the binary log or relay log in my backup but do not want to restore it Questions and Answers A 1 Does MySQL Enterprise Backup work with MySQL
4. cccceceeeeeeeeeeeeeeeee seas eaeeeeeeeeeeeeaeaaeaaeeeeeeeeeseaaaaaeneeeeeeeeeaea 137 The following sections describe the command line options for the different modes of operation of mysqlbackup The table below list all the command options for mysqlbackup Use the hyperlinks at the option names to jump to the detailed descriptions for the options Note R The command options can also be specified in configuration files see explanations in Chapter 14 Configuration Files and Parameters mysqlbackup follows the MySQL standard practice for handling duplicate options whether specified in a configuration file on the command line or both Options are processed first from configuration files then from the command line If an option is specified more than once the last instance takes precedence Table 13 1 List of All Options Format Description Introduced backup dir The directory to store the backup data backup image Specifies the path name of the backup image The name of the checksum algorithm used for validating Daki innodb_checksum_algorithnoDB tablespaces backup_innodb_data_file_path Specifies Innodb system tablespace files path and size in backup as Backup base directory for all InnoDB data files in the backup_innodb_data_home_dir system tablespace backup_innodb_log_file_size The size in bytes of each InnoDB backup log file Number of InnoDB log files in backup backup_
5. During hot and warm backups information about the structure of the database is retrieved automatically through a database connection For a cold backup you must specify file locations through configuration files or command line options 1 2 The mysqlbackup Client When using the MySQL Enterprise Backup product you primarily work with the mysqlbackup client Use it to perform different types of backup and restore operations as well as tasks that are otherwise performed by backup scripts such as creating a timestamped subdirectory for each backup compressing the backup data and packing the backup data into a single file for easy transfer to another server For information about the various mysqlbackup commands and command line options see Part Ill mysqlbackup Command Reference 1 3 Overview of Backup Performance and Capacity Considerations In your backup strategy performance and storage space are key aspects You want the backup to complete quickly with little CPU overhead on the database server You also want the backup data to be compact so you can keep multiple backups on hand to restore at a moment s notice Transferring the backup data to a different system should be quick and convenient All of these aspects are controlled by options of the mysqlbackup command Sometimes you must balance the different kinds of overhead CPU cycles storage space and network traffic Always be aware how much time it takes to restore
6. 105 Server Repository Options Typically you do not need to specify this option because its value is retrieved automatically using the database connection Its value is derived as follows e If innodb_data_home_dir is not specified it inherits the value of datadir e If innodb_data_home_dir is a relative path the path is located relative to that is underneath the datadir value e An innodb_data_home_dir of refers to the root directory e If innodb_data_home_dir is an absolute path its value is used as is innodb_data_file_path VALUE Specifies InnoDB data file names and sizes Examples ibdatal 32M ibdata2 32M autoextend abs path ibdatal 32M autoextend innodb dir ibdatal 32M autoextend When a database connection exists the value is retrieved automatically and overrides any value you specify This parameter together with innodb_data_home_dir determines where the InnoDB data files Such as ibdatal ibdata2 and so on reside in server repository Typically you do not need to specify this option because its value is retrieved automatically using the database connection If no database connection is available you must specify it Whether the initial file name begins with a character or not the files are located relative to the innodb_data_home_dir value innodb_log_group_home_dir PATH Specifies where InnoDB logs reside within the server repository Usually the same as dat adir but can be different
7. A ARM file Metadata for ARCHIVE tables Contrast with ARZ file Files with this extension are always included in backups produced by the mysqlbackup command of the MySQL Enterprise Backup product See Also ARZ file ARZ file Data for ARCHIVE tables Contrast with ARM file Files with this extension are always included in backups produced by the mysqlbackup command of the MySQL Enterprise Backup product See Also ARM file Antelope The code name for the original InnoDB file format It supports the redundant and compact row formats but not the newer dynamic and compressed row formats available in the Barracuda file format If your application could benefit from InnoDB table compression or uses BLOBs or large text columns that could benefit from the dynamic row format you might switch some tables to Barracuda format You select the file format to use by setting the innodb_file_format option before creating the table See Also Barracuda compression file format apply The operation that transforms a raw backup into a prepared backup by incorporating changes that occurred while the backup was running using data from the log See Also log prepared backup raw backup B bz file When mysqlbackup performs a compressed backup for a server that has binary logging enabled it transforms each binary log file and relay log file for a slave server in a replication setting to a binary or relay log file name bz file The bz files
8. B backup 173 backup directory 173 backup option 88 backup repository 174 backup and apply log option 88 backup dir option 107 backup dir to image option 94 backup image option 122 backup my cnf 174 backup my cnf file 7 backup to image option 88 121 backups cold 5 compressed 6 39 44 54 112 controlling overhead performance and scalability 123 encrypted 71 full 34 hot 5 incremental 6 35 113 InnoDB tables only 85 logical 6 message logging 130 monitoring 75 optimistic 49 parallel 6 partial 40 115 physical 6 prepared 7 53 preparing to restore 53 progress report 131 raw 7 53 scheduled 51 single file 6 45 streaming 6 47 to cloud 48 to tape 48 73 troubleshooting 75 uncompressed 6 43 verifying 32 warm 5 backup_content xml 7 backup_content xml file 78 backup_create xml 7 backup_create xml file 78 BACKUP_HISTORY table 76 BACKUP_PROGRESS table 76 backup_variables txt file 7 Barracuda 85 174 benchmarking 65 binary log 58 174 binlog 174 bz file 173 C changelog 151 changes release notes 151 cloud backups 48 cloud access key id option 136 cloud aws region option 136 cloud identity url 137 cloud object 136 cloud password 137 cloud region 137 cloud tempauth url 137 cloud tenant 137 cloud user id 136 counter container 136 cloud bucket option 136 cloud object key option 136 cloud pr
9. Its value is derived as follows e If innodb_log_group_home_dir is not specified it inherits the value of datadir e If innodb_log_group_home_dir is a relative path the path is taken to be relative to that is underneath the datadir value e If innodb_log_group_home_dir is an absolute path its value is used as is innodb_log_files_in_group N Specifies the number of InnoDB log files before being rotated Typically you do not need to specify this option because its value is retrieved automatically using the database connection If no database connection is available you must specify it When a database connection exists the value is retrieved automatically and overrides any value you specify 106 Backup Repository Options e innodb_log_file_size SIZE Specifies maximum single InnoDB log file size before switching to next log file Example 20M Typically you do not need to specify this option because its value is retrieved automatically using the database connection If no database connection is available you must specify it When a database connection exists the value is retrieved automatically and overrides any value you specify e innodb_page_size SIZE Specifies the page size for all InnoDB tablespaces Typically you do not need to specify this option because its value is retrieved automatically using the database connection If no database connection is available you must specify it Wh
10. dir and thus store the single file backup under backup dir or if the with timestamp option is used under a subdirectory created under backup dir which bears the timestamp in its name For restoring a backup directory Use backup dir to specify the location of the backup directory from which data will be restored to the server For restoring a single file backup including incremental compressed encrypted and cloud backups When using copy back and apply log to restore a single file backup use backup dir to supply a temporary folder to store the temporary data of the restore operation The directory specified by backup dir should be empty f a non empty directory is used the restore operation will still be carried out but the restore data might be corrupted For restoring an incremental backup to a single file you can use incremental backup dir for the same purpose backup_innodb_data_home_dir PATH The directory under which the backup s InnoDB data files are to be stored Specify the option if you want to put the data files at somewhere other than the default location which is backup dir datadir If the value of the parameter is different from backup dir datadir itis stored into the backup my cnf file as innodb_data_home_dir for information so that mysqlbackup can understand the structure of the backup when it performs various operations on the backup Together with backup_innodb_data_
11. A 3 Can I back up non InnoDB data with MySQL Enterprise Backup While MySQL Enterprise Backup can back up non InnoDB data like MYISAM tables the MySQL server to be backed up must support InnoDB i e the backup process will fail if the server was started up with the innodb OFF or skip innodb option and the server must contain at least one InnoDB table 145 A 4 What happens if the apply log step is interrupted If mysqlbackup is interrupted during the apply log or apply incremental backup stage the backup data is OK The file operations performed by those options can be performed multiple times without harming the consistency of the backup data Just run the same mysqlbackup command again and when it completes successfully all the necessary changes are present in the backup data A 5 Why is the option defaults file not recognized When you specify the defaults file option it must be the first option after the name of the command Otherwise the error message makes it look as if the option name is not recognized A 6 Can I back up a database on one OS platform and restore it on another one using MySQL Enterprise Backup See Section C 1 Cross Platform Compatibility for details A 7 What if have included the binary log or relay log in my backup but do not want to restore it If you want to skip the restore of the binary log relay log or both during a restore use the skip binlo
12. Creates a subdirectory underneath the backup directory with a name formed with the timestamp of the backup operation It is useful for maintaining a single backup directory containing many backup snapshots put under different subdirectories Default no timestamped subdirectory is created To reuse the same backup directory for a new backup without using this option either remove the previous backup files manually or for a single file backup specify the force 103 option to overwrite the old backup file The following parameters provide information on the original structure of the data on the backed up server for future operations on the backup but do not affect the structure of the backup itself backup_innodb_log_files_in_group N The number of InnoDB log files in a log group on the restored server See the description for innodb_log_files_in_group in the MySQL server manual The value for this parameter saved as innodb_log_files_in_group in the backup my cnf file is derived as follows e Use the backup_innodb_log_files_in_group value from command line or configuration file if specified e Else use the innodb_log_files_in_group value from the backed up server if it is an online backup e Else use the innodb_log_files_in_group value from the mysqlbackup command line or configuration file backup_innodb_log_file_size SIZE The maximum single InnoDB log file size in backup before switching to ne
13. backup dir na mysqlbackup defaults file home pekka my cnf incremental start lsn 2654255716 with timestamp incremental backup dir incr images backup image incremental_imagel bi backup to image On how to restore your database using the incremental backups see Section 5 2 3 Restoring an Incremental Backup Next steps e Ona regular schedule determined by date or amount of database activity take more incremental backups e Optionally periodically start the cycle over again by taking a full uncompressed or compressed backup Typically this milestone happens when you can archive and clear out your oldest backup data 4 3 3 Making a Compressed Backup To save disk space you can compress InnoDB backup data files by using the compress option of mysqlbackup Compression lets you keep more sets of backup data on hand and save transmission time when sending the backup data to another server The downside includes the extra CPU overhead during the backup itself and the extra time needed for the restoration process for uncompressing the data The backup compression feature works only for InnoDB tables After the InnoDB tablespace files are compressed during backup they receive the ibz extension To avoid wasting CPU cycles without saving additional disk space compress does not attempt to compress tables that were already compressed on the server see Enabling Compression for a Table neve
14. for information about creating compressed backups Compression involves a tradeoff between backup performance and restore performance In an emergency the time needed to uncompress the backup data before restoring it might be unacceptable There might also be storage issues if there is not enough free space on the database server to hold both the 65 Single File Backups compressed backup and the uncompressed data Thus the more critical the data is the more likely that you might choose not to use compression accepting a slower larger backup to ensure that the restore process is as fast and reliable as possible Single File Backups The single file backup by itself is not necessarily faster than the traditional type of backup that produces a directory tree of output files Its performance advantage comes from combining different steps that you might otherwise have to perform in sequence such as combining the backup data into a single output file and transferring it to another server See Section 12 5 Single File Backup Operations for the options related to single file backups and Section 4 3 5 Making a Single File Backup for usage instructions InnoDB Configuration Options Settings Prior to MySQL 5 5 it was common practice to keep the redo logs fairly small to avoid long startup times when the MySQL server was killed rather than shut down normally In MySQL 5 5 and higher the performance of crash recovery is sign
15. meta 140219 11 22 45 mysqlbackup INFO Total files as specified in image 44 mysqlbackup INFO datadir tpch tabnorm7 ibd Validated mysqlbackup INFO datadir tpch tabnorm8 ibd Validated mysqlbackup INFO datadir tpch tabnorm9 ibd Validated 140219 11 22 45 mysqlbackup INFO Validate operation completed successfully 140219 11 22 45 mysqlbackup INFO Backup Image validation successful mysqlbackup INFO Source Image Path logs img bi mysqlbackup completed OK This is a sample output for a checksum mismatch in the header mysqlbackup ERROR Checksum mismatch Computed checksum Checksum in image mysqlbackup ERROR Problem verifying checksum of Image Path meb backups image mbi mysqlbackup ERROR Backup image validation failed This is a sample output for an image containing corrupted ibd files mysqlbackup ERROR datadir db2 bigtabl ibd has corrupt page number 64 page number from page header 64 mysqlbackup ERROR datadir fdb2 bigtabl ibd is corrupt and bas 10 corrupt pages mysqlbackup ERROR datadir db2 tl ibd has corrupt page number 4 page number from page header 0 mysqlbackup ERROR datadir dbo ti ibd 12s corrupt and has 5 corrupt pages mysqlbackup ERROR datadir ibdatal has corrupt page number 63 page number from page header 63 mysqlbackup ERROR datadir ibdatal has corrupt page number 7 page number from page header 7 mysqlbackup ERROR datadir ibdatal is corrupt and
16. xi Legal Notices Documentation Accessibility For information about Oracle s commitment to accessibility visit the Oracle Accessibility Program website at http www oracle com pls topic lookup ctx acc amp id docacc Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support For information visit http www oracle com pls topic lookup ctx acc amp id info or visit http Awww oracle com pls topic lookup ctx acc amp id trs if you are hearing impaired This documentation is NOT distributed under a GPL license Use of this documentation is subject to the following terms You may create a printed copy of this documentation solely for your own personal use Conversion to other formats is allowed as long as the actual content is not altered or edited in any way You shall not publish or distribute this documentation in any form or on any media except if you distribute the documentation in a manner similar to how Oracle disseminates it that is electronically for download on a Web site with the software or on a CD ROM or similar medium provided however that the documentation is disseminated together with the software on the same medium Any other use such as any dissemination of printed copies or use of this documentation in whole or in part in another publication requires the prior written consent from an authorized representative of Oracle Oracle and or its a
17. Eric Young should be given attribution as the author of the parts of the library used This can be in the form of a textual message at program startup or in documentation online or textual provided with the package Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions are met 1 Redistributions of source code must retain the copyright notice this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution 3 All advertising materials mentioning features or use of this software must display the following acknowledgement This product includes cryptographic software written by Eric Young eay cryptsoft com The word cryptographic can be left out if the routines from the library being used are not cryptographic related 4 If you include any Windows specific code or a derivative thereof from the apps directory application code you must include an acknowledgement This product includes software written by Tim Hudson tjh cryptsoft com THIS SOFTWARE IS PROVIDED BY ERIC YOUNG AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL
18. Without specifying the defaults file option the restore can still be performed as long as the related InnoDB parameters for the backed up and the target server match you are going to receive some warnings though from mysqlbackup e datadir supplies the location of the data directory for restoring the data e backup image provides the path of the single file backup e backup dir provides the location of an empty folder to store some temporary files created during the restore procedure mysqlbackup defaults file home admin backups backup my cnf datadir var lib mysql backup image home admin backups my mbi backup dir home admin backup tmp copy back and apply log MySQL Enterprise Backup version 3 12 1 Linux 2 6 18 274 e15 i686 2014 11 12 Copyright c 2003 2014 Oracle and or its affiliates All Rights Reserved mysqlbackup INFO Starting with following command line mysqlbackup defaults file home admin backup my cnf datadir var lib mysql backup image home admin backups my mbi backup dir home admin backup tmp copy back and apply log mysqlbackup INFO IMPORTANT Please check that mysqlbackup run completes successfully At the end of a successful copy back and apply log run mysqlbackup prints mysqlbackup completed OK mysqlbackup INFO Backup Image MEB version string 3 12 1 2014 11 12 141204 13 10 39 mysqlbackup INFO MEB logfile created at home admin backup tmp
19. alex blob only innodb backup many lines of output mysqlbackup Scanned log up to lism 2666737471 mysqlbackup Was able to parse the log up to lsn 2666737471 mysqlbackup Maximum page number for a log record 0 mysqlbackup Compressed 147 MB of data files to 15 MB compression 89 44 Making a Single File Backup 101208 17 18 04 mysqlbackup Full backup completed The backup directory for the database test is shown below The ibz files are compressed per table data files ls sqldata backup test alexl ibz alex2 ibz alex3 ibz pope RDZ The databases and databases list file options of mysqlbackup let you back up non InnoDB tables only from selected databases rather than across the entire MySQL instance To filter InnoDB tables use the include option instead With databases you specify a space separated list of database names with the entire list enclosed in double quotation marks With databases list file you specify the path of a file containing the list of database names one per line Some or all of the database names can be qualified with table names to only back up selected non InnoDB tables from those databases If you specify this option make sure you include the same set of databases for every backup especially incremental backups so that you do not restore out of date versions of any databases 4 3 5 Making a Single File Backup To avoid having a large number of backup files
20. and it is unlikely to be always fulfilled when it is otherwise 52 Chapter 5 Recovering or Restoring a Database Table of Contents 5 1 Preparing the Backup to be Restored cccccceeeeeeeeeeeee cece ee eeeeeeeeee ee aaaaeeeeeeeeeeeeaaaaeeneeseeeeeeaeaaeaees 53 5 2 Performing a Restore Operation 0ccccccceeeceeeeeeeeeeeeeee ee eaeeeeeeeeeeeeeeaaaaeeeeeeeeeeeaaaaeeeeeeeeeeeeaeaaeaees 54 5 2 1 Restoring a Compressed Backup cccceceeeeeeeeeeeeeeeeeeeaeeaeeeeeeeeeeeeaeaaeeneeeeeeeeeaeaaeanegeeeees 55 5 2 2 Restoring an Encrypted Backup Image ceeeceeenneeeeee ee eeeeeeaaeeeeeeaaeeeeeeaaeeeeeeaaeeeeeeaaieeees 56 5 2 3 Restoring an Incremental Backup cccccececeeeeeeeeeeeeeeae aaa eeeeeeeeeeaeaaeaeeceeeeeeeeeaaaaeeeeeseeeees 56 5 2 4 Restoring Backups Created with the use tts Option 2 0 0 cceeeeececneeeeeeseeeeeeeaaeeees 57 5 2 5 Restoring a Backup from Cloud Storage to a MySQL Servet cccceceeeeeeeeeeeeeeeeeeaeaaeeees 58 5 3 Point in Time Recovery from a Hot Backup ccccceceeeeeeeeeeeeeeeeeeeaaaaeeeeeeeeeeeeaeaaeeeeseeeeeeaeaaaeees 58 5 4 Restoring a Backup with a Database Upgrade or Downgrade eceeeeeeeee cece ener eeeeeeeeeeeeaeeeeeenaes 59 The ultimate purpose of backup data is to help recover from a database issue or to create a clone of the original database in another location typically to run report queries or to create a new replication slave
21. or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing If this is software or related documentation that is delivered to the U S Government or anyone licensing it on behalf of the U S Government then the following notice is applicable U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently dangerous applications including applications that may create a risk of personal injury If you
22. zlib general purpose compression library Copyright C 1995 2004 Jean loup Gailly and Mark Adler zlib h interface of the zlib general purpose compression library Verson amnor wily Ica ZOOS Copyright C 1995 2005 Jean loup Gailly and Mark Adler zlib h interface of the zlib general purpose compression library Wewssion e255 Apr Whelan ZOO Copyright C 1995 2010 Jean loup Gailly and Mark Adler This software is provided as is without any express or implied warranty In no event will the authors be held liable for any damages arising from the use of this software Permission is granted to anyone to use this software for any purpose including commercial applications and to alter it and redistribute it freely subject to the following restrictions 1 The origin of this software must not be misrepresented you must not claim that you wrote the original software If you use this software in a product an acknowledgment in the product documentation would be appreciated but is not required 2 Altered source versions must be plainly marked as such and must not be misrepresented as being the original software 3 This notice may not be removed or altered from any source distribution Jean loup Gailly jloup gzip org Mark Adler madler alumni caltech edu 172 MySQL Enterprise Backup Glossary These terms are commonly used in information about the MySQL Enterprise Backup product
23. 1 ibobk so on Linux and Unix systems and ORASBT DLL on Windows systems When you specify sbt 1ib path you can use a different filename for the library in addition to specifying the path e Specify any other product specific settings that are normally controlled by environment variables using the sbt environment option To restore MySQL data from tape 73 Backing Up to Tape with Oracle Secure Backup e Specify the backup image sbt name parameter of mysqlbackup as part of the restore operation Use the same name value as during the original backup This single parameter retrieves the appropriate data from the appropriate tape device e Optionally use the sbt 1ib path option using the same values as for the backup operation e Specify any other product specific settings that are normally controlled by environment variables using the sbt environment option For product specific information about Oracle Secure Backup see the Oracle Secure Backup documentation Example 9 1 Sample mysqlbackup Commands Using MySQL Enterprise Backup with Oracle Secure Backup Uses libobk so or ORASBT DLL in standard places mysqlbackup port 3306 protocol tcp user root password backup image sbt backup shoeprod 2011 05 30 backup dir backup backup to image Associates this backup with storage selector shoeprod mysqlbackup port 3306 protocol tcp user root password backup image sbt backup sho
24. 1og operations the number of read threads is always 1 regardless of this option setting See Section 7 1 Optimizing Backup Performance and Section 7 2 Optimizing Restore Performance for advice about recommended combinations of values for read threads process threads and write threads for various hardware configurations such as RAID or non RAID storage devices 124 Performance Scalability Capacity Options process threads num_threads Command Line Format process threads NUMBER Permitted Values Type numeric Default 6 Min 1 Value Max 15 Value Specifies the number of threads to use for processing data such as compressing or uncompressing backup files Default currently 6 This default applies to these kinds of operations ext ract and backup lt is ignored when you use any of the options incremental with redo log only apply incremental backup copy back or backup dir to image If you specify a value of 0 it is silently adjusted to 1 The maximum is 15 if you supply a negative value it is silently adjusted to 15 For appl y 1og operations the number of process threads is always 1 regardless of this option setting See Section 7 1 Optimizing Backup Performance and Section 7 2 Optimizing Restore Performance for advice about recommended combinations of values for read threads process threads and write threads for
25. 3 arrange in a manner consistent with the requirements of this License to extend the patent license to downstream recipients Knowingly relying means you have actual knowledge that but for the patent license your conveying the covered work in a country or your recipient s use of the covered work in a country would infringe one or more identifiable patents in that country that you have reason to believe are valid If pursuant to or in connection with a single transaction or arrangement you convey or propagate by procuring conveyance of a covered work and grant a patent license to some of the parties receiving the covered work authorizing them to use propagate modify or convey a specific copy of the covered work then the patent license you grant is automatically extended to all recipients of the covered work and works based on it A patent license is discriminatory if it does not include within the scope of its coverage prohibits the exercise of or is conditioned on the non exercise of one or more of the rights that are specifically 161 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 granted under this License You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software under which you make payment to the third party based on the extent of your activity of conveying the wo
26. 3 GNU Standard C Library libstdc License cece eeeceeeceeeeeeeeeee tees aaeeeeeeeeeeeeaeaaee E 4 Google Controlling Master Thread I O Rate Patch License 0 ccseeeeeeeeeeeeeeaeeneeees E 5 Google SMP Patch License cesarean aano aaa i aa ia anai aa E6 LZ4 LICGNSS sericis ERNA AEE ERR NSRR E 7 OpenSSL Vi OMICENSS ennen a A E E R E 8 Percona Multiple I O Threads Patch License cccceeeeeeeeeee cece ae eeeeeeeeeeeeeeaaeaeeeees E9 REZ Mf e lnc proio a ceo nr eer ceer ae reerrer ee ern mereeer ee rrerr er rrcern S E 10 RegEX Spencer Library License cccccccceeeeeeeeeeeeeeaeeaeeeeeeeeeeeaeaaaaeeeeeeseeaeaaaaaes E 11 RFC 3174 US Secure Hash Algorithm 1 SHA1 License ccceseeeeeeeeeeeeneeeeeees MySQL Enterprise Backup User s Guide Version 3 12 1 Index E12 Zi LICENSE AE ETE E E E AE E L A ATT E T A E MySQL Enterprise Backup Glossary seseseeseeiseesestsntirriettsttrtttttttasttntrtnnttssttnnrnnnnnstsnnnnnnnt vi List of Tables 1 1 Files in a MySQL Enterprise Backup Output Directory 00 cceccceeeeeeeeeneeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeeees 4 1 Information Needed to Back Up a Database cece eeeeee tree cette reese tees eeaeeeeeeeaaeeeeaaaaeeeeaaaees 13 A histo Al Option Scions ia hee Pad ves led Gaia ae 2s aaah PAARE EaR TAa PEATA ADEK EDET lags vii viii List of Examples 4 1 Making an Uncompressed Partial B
27. 5 to 3 11 Note R For any restore that involves a server upgrade or downgrade see the important discussion in Section 5 4 Restoring a Backup with a Database Upgrade or Downgrade C 4 Compatibility Notes for Specific MySQL Versions This section lists any performance related features and settings in specific MySQL Server versions that affect various aspects of the backup process MySQL 5 6 Some new MySQL 5 6 features introduce changes in directory layout and file contents for InnoDB tables Backing up servers that use these features requires MySQL Enterprise Backup 3 8 1 or higher e innodb_page_size configuration option e innodb_undo_directory innodb_undo_logs and innodb_undo_tablespaces configuration options 149 MySQL 5 6 e innodb_checksum_algorithm configuration option DATA DIRECTORY Clause of the CREATE TABLE statement which produces a isl file in the database directory and stores the ibd file in a user specified location e Online DDL See MySQL Enterprise Backup 3 9 Release Notes for details on the fixes and enhancements related to these MySQL 5 6 features 150 Appendix D MySQL Enterprise Backup Release Notes Release notes for MySQL Enterprise Backup are published separately See MySQL Enterprise Backup 3 12 Release Notes 151 152 Appendix E Licenses for Third Party Components Table of Contents EA CURL peur LICENSE is ccct seek cover
28. 6 Making an Optimistic Backup Optimistic backup is a feature introduced in MySQL Enterprise Backup 3 11 for improving performance for backing up and restoring huge databases in which only a small number of tables are modified frequently During a hot backup of a huge database say in the order of terabytes huge redo log files could be generated on the server when the backup is in progress As the redo log files grow faster than they can be processed by mysqibackup the backup operation can actually fail when mysqlbackup Cannot catch up with the redo log cycles and LSNs get overwritten by the server before they are read by mysqlbackup Moreover the apply log step for preparing a backup for restoration can take a very long time as mysqlbackup has huge ibbackup_logfile files created from the big redo log files to apply to the backup The problems are intensified when the I O resources available for reading and writing the redo logs are scarce during the backup and restoration processes 49 Making an Optimistic Backup Optimistic backup relieves the problems by dividing the backup process into two internal phases which are transparent to the users 1 Optimistic phase In this first phase tables that are unlikely to be modified during the backup process referred to as the inactive tables below identified by the user with the opt imistic time option or by exclusion with the opt imistic busy tables option are backed up wit
29. Compatibility Information for MySQL Enterprise Backup Table of Contents C 1 Cross Platform Compatibility 0 0 0 0 ccc eeeeee cece cette eter eee e a i a a 149 C 2 Compatibility with MySQL Versions ccccceee cece ee ee eee eee eeee ents seca aa eaeeeeeeeeeeeaaaaeeeeeeeeeeeeaeaaeeees 149 C 3 Compatibility with Older MySQL Enterprise Backup 0 ccceeeeeeeeeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaaaeenees 149 C 4 Compatibility Notes for Specific MySQL Versions ccccceeceeeeeeee tees eee eeeeeeeeeeeeaeaaeteeeeeeeeeaeaaes 149 This section describes information related to compatibility issues for MySQL Enterprise Backup releases C 1 Cross Platform Compatibility MySQL Enterprise Backup is cross platform compatible when running on the Linux and Windows operating systems backups on a Linux machine can be restored on a Windows machine and vice versa However to avoid data transfer problems arising from letter cases of database or table names the variable lower_case_table_names must be properly configured on the MySQL servers For details see Identifier Case Sensitivity C 2 Compatibility with MySQL Versions MySQL Enterprise Backup 3 12 supports MySQL 5 5 and 5 6 C 3 Compatibility with Older MySQL Enterprise Backup MySQL Enterprise Backup 3 12 can be used to restore backups created for MySQL 5 5 and 5 6 by any older MySQL Enterprise Backup versions that support those server versions that is MySQL Enterprise Backup 3
30. March 2009 this license document but changing it is not allowed Preamble The GNU General Public License is a free copyleft license for software and other kinds of works The licenses for most software and other practical works are designed to take away your freedom to share and change the works By contrast the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program to make sure it remains free software for all its users We the Free Software Foundation use the GNU General Public License for most of our software it applies also to any other work released this way by its authors You can apply it to your programs too When we speak of free software we are referring to freedom not price Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software and charge for them if you wish that you receive source code or can get it if you want it that you can change the software or use pieces of it in new free programs and that you know you can do these things To protect your rights we need to prevent others from denying you these rights or asking you to surrender the rights Therefore you have certain responsibilities if you distribute copies of the software or if you modify it responsibilities to respect the freedom of others For example if you distribute copies of such a program whether gratis or for a fee you
31. Notes mysqlbackup to find those files and include them in the backups The copying of these files are skipped during a backup or a restore when the skip relay log option is used Backup image file A single file backup produced by the backup to image option with a name specified by the backup image option If your backup data directory consists only of zero byte files with a single giant data file in the top level directory you have a single file backup You can move the image file without losing or damaging the contents inside it then unpack it with mysqlbackup using the extract option and specifying the same image name with the backup image option Although some extra files such aS backup my cnf and the meta subdirectory are present in the backup directory these files are also included in the image file and do not need to be moved along with it Any other files in the database subdirectories under the datadir directory that is under backup dir datadir data base name Copied from the database subdirectories under the MySQL data directory By default any unrecognized files in the database subdirectories under the MySQL data directory are copied to the backup To omit such files specify the only known file types option meta directory A subdirectory that stores files with metadata about the backup Created under the backup directory by mysqlbackup All files listed bel
32. OPTIONS INCREMENTAL BACKUP OPTIONS PARTIAL BACKUP RESTORE OPTIONS SINGLE F ILE BACKUP OPTIONS PERFORMANCE SCALABILITY CAPACITY OPTIONS MESSAGE LOGGING OPTIONS PROGRESS REPORT OPTIONS ENCRYPTION OPTIONS CLOUD STORAGE OPTIONS backup to image mysqlbackup STD OPTIONS backup image IMAGE backup dir PATH MESSAGE LOGGING OPTIONS PROGRES S REPORT OPTIONS ENCRYPTION OPTIONS CLOUD STORAGE OPTIONS image to backup dir mysqlbackup STD OPTIONS backup dir PATH backup image IMAGE MESSAGE LOGGING OPTIONS PROGRESS REPORT OPTIONS ENCRYPTION OPTIONS CLOUD STORAGE OPTIONS backup dir to image mysqlbackup STD OPTIONS backup image IMAGE src entry PATH MESSAGE LOGGING OPTIONS ENCRYPTION OPTIONS CLOUD STORAGE OPTIONS list image mysqlbackup STD OPTIONS backup image IMAGE backup dir PATH src entry PATH dst entry PATH MESSAGE LOGGING OPTIONS PROGRESS REPORT OPTIONS ENCRYPTION OPTIONS CLOUD STORAGE OPTIONS extract mysqlbackup STD OPTIONS SERVER REPOSTTORY OPTIONS 93 Single File Backup Operations backup image IMAGE backup dir PATH MESSAGE LOGGING OPTIONS PARTIAL BACKUP RESTORE OPTIONS PROGRESS REPORT OPTIONS ENCRYPTION OPTIONS CLOUD STORAGE OPTIONS copy back and apply log image to
33. Section 13 9 Single File Backup Options On the OSB side you can schedule MySQL Enterprise Backup jobs by specifying a configurable command that calls mysqlbackup You control OSB features such as encryption by defining a storage selector that applies those features to a particular backup and passing the name of the storage selector to OSB using the MySQL Enterprise Backup parameter sbt database name storage selector To back up MySQL data to tape e Specify the backup image sbt name parameter of mysqlbackup to uniquely identify the backup data The sbt prefix sends the backup data to the MMS rather than a local file and the remainder of the argument value is used as the unique backup name within the MMS e Specify the sbt database name parameter of mysqlbackup to enable the OSB operator to configure a storage selector for backups from this MySQL source This parameter refers to a storage selector defined by the OSB operator not to any MySQL database name By default mysqibackup supplies a value of MySQL for this MMS parameter The argument to this option is limited to 8 bytes e If you have multiple media management programs installed to select the specific SBT library to use specify the sbt lib path parameter of the mysqlbackup command If you do not specify the sbt lib path parameter mysqlbackup uses the normal operating system paths and environment variables to locate the SBT library which is named
34. THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND 169 Percona Multiple I O Threads Patch License ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE The license and distribution terms for any publically available version or derivative of this code cannot be changed i e this code cannot simply be copied and put under another distribution license including the GNU Public License E 8 Percona Multiple I O Threads Patch License The following software may be included in this product Percona Multiple I O threads patch Copyright c 2008 2009 Percona Inc All rights reserved Redistribution and use of this software in source and binary forms with or without modification are permitted provided that the following conditions are met Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the dist
35. apply log The restoration process requires the database server to be already shut down except for restorations of backups created with the use tts option see explanations below The process copies the data files logs and other backed up files from the backup directory back to their original locations and performs any required post processing on them For any restore operation the options datadir innodb_log_files_in_group innodb_log_file_size and innodb_data_file_path must be specified either in the target server s configuration file in the file specified by the defaults file option or as command line options 54 Restoring a Compressed Backup Example 5 4 Shutting Down and Restoring a Database mysqladmin user root password shutdown mysqlbackup defaults file usr local mysql my cnf backup dir export backups full copy pack Note R The restored data includes the backup_history table where MySQL Enterprise Backup records details of each backup The table allows you to perform future incremental backups using the incremental base history last_backup option Important A When performing a full restore for example when the backup data is used to set up a new MySQL server or used to replace all data of an existing MySQL server make sure the target data directories are all clean containing no old or unwanted data files this might require manual removal of files at the locations specified by
36. apply log operation will be performed on the backup directory That means the backup taken will be altered during the process and users might want to make an extra copy of the backup directory before proceeding with the restoration in order to prevent the loss of backup data in case something goes wrong Also note that e Backups created with the skip unused pages option cannot be restored using copy back and apply log e For image backups taken with MySQL Enterprise Backup 3 8 2 or earlier per table ibd files pointed to by isi files in a backup are restored by copy back and apply 1log to the server s data directory rather than the locations pointed to by the isl files 90 Validation Operations e Due to a known issue when restoring a compressed backup created with MySQL Enterprise Backup 3 9 or earlier and containing any InnoDB tables that were created on the server as compressed tables by using the ROW_FORMAT COMPRESSED option the KEY_BLOCK_S1IZE option or both do not use copy back and apply log instead perform an apply log first and then a copy back See entry for Bug 17992297 in the MySQL Enterprise Backup 3 10 0 changelog for details At the end of the copy back and apply log operation the file backup_variables txt is being created or updated in the data directory This file contains metadata about the restored contents and is being used by successive single step restores of increme
37. are uncompressed at the time of restore See Also binary log bz file compression compression level ibz file relay log backup The process of copying some or all table data and metadata from a MySQL instance for safekeeping Can also refer to the set of copied files This is a crucial task for DBAs The reverse of this process is the restore operation With MySQL physical backups are performed by the MySQL Enterprise Backup product and logical backups are performed by the mysqldump command These techniques have different characteristics in terms of size and representation of the backup data and speed especially speed of the restore operation Backups are further classified as hot warm or cold depending on how much they interfere with normal database operation Hot backups have the least interference cold backups the most See Also cold backup hot backup logical backup mysqldump physical backup warm backup backup directory The directory under which the backup data and metadata are stored permanently or temporarily It is used in most kinds of backup and restore operations including single file backups and restores See the description of the backup dir option on how the backup directory is used for different purposes and for different operations 173 backup repository Contrast with server repository See Also repository server repository backup my cnf A small configuration file generated by MySQL Enterpr
38. authors nor IBM Haifa Research Laboratories make any representation about the suitability of this software for any purpose It is provided as is without express or implied warranty E 4 Google Controlling Master Thread I O Rate Patch License The following software may be included in this product Google Controlling master thread I O rate patch 166 Google SMP Patch License CopyLachG Cc 20 097 Coole miner All rights reserved Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions Are mets Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution Neither the name of the Google Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT NCIDENTAL SPECIAL
39. backup dir Unpacks a single file backup to a full backup directory structure You specify the paths to both the image file and the destination directory for the unpacking For usage examples see Section 4 3 5 Making a Single File Backup backup dir to imag Packs an existing backup directory into a single file The value for the backup image parameter should either be stands for standard output or an absolute path outside of the backup dir directory Specify a backup image value of standard output to stream an existing backup directory structure to a tape device or a command that transfers the backup to another server For usage examples see Section 4 3 5 Making a Single File Backup list image Display the contents of a single file backup Lists all files and directories in the image The src ent ry name Can be used to list a specific file or directory if the name is a directory all its files and subdirectories inside the image are recursively listed For usage examples see Section 4 3 5 Making a Single File Backup Note N The list image operation can be performed on a cloud backup only if the cloud proxy supports HTTP range headers extract Unpacks an individual file or directory from a single file backup It is useful for troubleshooting or for restorations that do not require the full set of backup data The resulting file or directory goes into the current directory or into
40. backup dir if specified All files and directory contents in the image with absolute path names are extracted into the same absolute paths on the local system For usage examples see Section 4 3 5 Making a Single File Backup The src entry path option can be used for selective extraction of a single file or single directory in image Specify the path as it appears in the image The dst entry path option along with src entry path option can be used to extract a single file or single directory into a user specified file or directory respectively If the src ent ry option is used but dst entry option is omitted then the selected file or directory is extracted to the same path in the local file system The default destination for the extract is the current working directory It can be overridden by the backup dir option All the files with relative pathnames in the image are extracted to pathhnames relative to the destination directory 94 Single File Backup Operations If the image contains some entries with absolute pathnames those entries are extracted to the same absolute pathnames even if backup dir option is specified The dst ent ry option must be used to relocate an absolute pathname copy back and apply log See description for copy back and apply log in Section 12 3 Restore Operations 95 96 Chapter 13 mysqlbackup Command Line Options Table of Contents 13
41. backup using a different OS user ID or a different umask setting than applies to the original files you might need to run commands such as chown and chmod on the backup data See Section B 1 Limitations of MySQL Enterprise Backup for details Size of InnoDB redo log files Calculated from the values of the innodb_log_file_size and Only needed if you perform incremental backups using the 28 Grant MySQL Privileges to Backup Administrator Information to Gather Where to Find It How Used innodb_log_files_in_group incremental with redo configuration variables Use the log only option rather than the technique explained for the incremental option The incremental with redo size of the InnoDB redo log and log only option the rate of generation for redo data dictate how often you must perform incremental backups Rate at which redo data is Calculated from the values of the Only needed if you perform generated InnoDB logical sequence number incremental backups using the at different points in time Use incremental with redo the technique explained for the log only option rather than the incremental with redo incremental option The log only option size of the InnoDB redo log and the rate of generation for redo data dictate how often you must perform incremental backups 4 1 2 Grant MySQL Privileges to Backup Administrator For most backup oper
42. both the datadir and innodb_data_file_path options otherwise add the force 103 option to the restore command to overwrite the old data The same cleanup is not required for restoring backups created with the use tts option in which case other requirements described in Section 5 2 4 Restoring Backups Created with the use tts Option apply though and usually not necessary for restoring a partial backup You can combine the apply log and the copy back operations as well as a number of other operations depending on the kind of backup you are restoring into a single step by using the copy back and apply log option instead Example 5 5 Restoring a Backup Directory using copy back and apply log mysqlbackup defaults file usr local mysql my cnf backup dir export backups full copy back and apply log Example 5 6 Restoring a Single file Backup using copy back and apply log mysqlbackup defaults file lt backupDir gt backup my cnf uroot backup image lt image_name gt backup dir lt backupTmpDir gt datadir lt restoreDir gt copy back and apply log The backup dir option specifies the temporary directory into which the backup image will be extracted Note R Due to a known issue Bug 20485910 restoring a partial image backup created with MySQL Enterprise Backup 3 11 or earlier requires using the force option The following subsections describes a number of different scenarios for rest
43. by the shell wildcard mechanism See Also exclude include partial backup relay log A record on a slave server for the events read from the binary log of the master and written by the slave I O thread The relay log like the binary log consists of a set of numbered files containing events that describe database changes and an index file that contains the names of all used relay log files For more information on relay log see The Slave Relay Log The relay log on a server is backed up by default See Also binary log replication replication A common configuration for MySQL deployments with data and DML operations from a master server synchronized with a set of slave servers With MySQL Enterprise Backup you might take a backup on one server and restore on a different system to create a new slave server with the data already in place You might also back up data from a slave server rather than the master to minimize any slowdown of the overall system See Also master slave repository We distinguish between the server repository and the backup repository See Also backup repository server repository restore The converse of the backup operation The data files from a prepared backup are put back into place to repair a data issue or bring the system back to an earlier state See Also backup prepared backup row format The disk storage format for a row from an InnoDB table As InnoDB gains new capabilities such as compression new
44. by which users should make sure the same plugins are defined in the same manner on the target server for restoration 78 Using the MySQL Enterprise Backup Manifest e image_files xml1 information about the files in a single file backup Only produced for backups taken with the backup to image and backup dir to image commands A management tool might use the paths recorded in this file to plan or automate the unpacking of a single file backup using the image to backup dir or extract commands or to remap the paths of extracted files with the srce entry and dst entry options 79 80 Part Ill mysqlbackup Command Reference Table of Contents VAY SS PO SCID ceset aT A E ee N EA nad a aA na AE aden ehh aea a Eaa erage 85 te mysglbackup COMMANGS ssrin arn aaa a A eaa E a a r araida 87 12 1 Backup Operations 0 ccccccececeneeneeee eter tees eee tect eee e ee ni datnan aaia iniaa iaai aiaa daa Eai 87 12 2 Apply Log Operations ssnin doirinn anaia aa aa a aa aaa 88 12 3 Restore Operations 2 0 00 cece cece cece ce aaun ranean ena aa i aa ei eaaa EA aiaia 89 12 4 Validation Operations sensorinen aa a REAA R R E Eiaa 91 12 5 Single File Backup Operations cccccccceeeeeeee cece ee ee eee ee ee esse tees ae aaa eeeeeeeeeeaeaaaaneeeeeeeeeaeaaed 93 13 mysgqibackup Command Line OPN siccccteiicdcwntaiccestoayedeearaecaseindecdewnd abeddeltavedewanaddssatndesdeantadadeata 97 13 4 Standa
45. cloud region 137 The Keystone region for the user specified by cloud user 3 12 0 id cloud secret access key AWS secret access key cloud service Cloud service for data backup or restoration cloud tempauth url 137 The URL of the identity service for authenticating user 3 12 0 credentials with Swift s TempAuth authentication system cloud tenant 137 The Keystone tenant for the user specified by cloud user 3 12 0 id cloud trace Print trace information for cloud operations cloud user id 136 User ID for accessing Swift 3 12 0 comments Specifies comments string comments file Specifies path to comments file compress compress level Create backup in compressed format Specifies the level of compression compress method Specifies the compression algorithm connect if online Use connection only if available connect_timeout Connection timeout in seconds 98 Format Description Introduced databases databases list file Legacy Specifies the list of non InnoDB tables to back up Legacy Specifies the pathname of a file that lists the non InnoDB tables to be backed up datadir Path to mysql server data directory debug Print debug information decrypt Decrypt backup image written in an MEB Secure File default character set Set the default character set defaults extra file Read this file after
46. conditions are not met in your database application use the only innodb or only innodb with frm option to back up only InnoDB tables or use the no locking option to back up non InnoDB files Note that MyISAM frm and other files copied under the no locking setting cannot be guaranteed to be consistent if they are updated during this final phase of the backup For a large database a backup run might take a long time Always check that mysqlbackup has completed successfully either by verifying that mysqlbackup returned exit code 0 or by observing that mysqlbackup has printed the text mysqlbackup completed OK e mysqlbackup is not the same as the former MySQL Backup open source project from the MySQL 6 0 source tree The MySQL Enterprise Backup product supersedes the MySQL Backup initiative Schedule backups during periods when no DDL operations involving tables are running See Section B 1 Limitations of MySQL Enterprise Backup for restrictions on backups at the same time as DDL operations Network Performance For data processing operations you might know the conventional advice that Unix sockets are faster than TCP IP for communicating with the database Although the mysqlbackup command supports the options protocol tcp protocol socket and protocol pipe these options do not have a significant effect on backup or restore performance These processes involve file copy operations rather
47. containing a single InnoDB table and associated indexes Compressed form of InnoDB data files from the MySQL data directory Used for tables created using the innodb_file_per_table option Because the original files might change while the backup is in progress the apply log step applies the same changes to the corresponding backup files Produced instead of ibd files in a compressed backup The ibdata files representing the InnoDB system tablespace also receive this extension in a compressed backup The ibz files are uncompressed during the apply log or copy back and apply log step frm Hold metadata about all MySQL tables The database is put into a read only state while these files are copied These files are copied without changes MYD MyISAM table data The database is put into a read only state while these files are copied These files are copied without changes MYT MyISAM index data The database is put into a read only state while these files are copied These files are copied without changes CSM Metadata for CSV tables These files are copied without changes The backup_history and backup_progress tables created by mysqlbackup use the CSV format so the backup always includes some files with this extension CSV Data for CSV tables These files are copied without changes The backup_history and backup_progress tables created by mysqlbackup us
48. data files Used in restore operations to reproduce the same layout as when the backup was taken ibbackup_ibd_files Records names of the ibd files and their space IDs during an incremental backup This file is created during an incremental backup During a restore the information in the file is used to delete the tables from the full backup that has been removed between the time of the full backup and the time of the incremental backup ibbackup_logfile A condensed version of the ib_logfile files from the MySQL data directory The InnoDB log files ib_logfile are fixed size files that are continuously updated during the database s operation For backup purposes only the changes that are committed while the backup is in progress are needed These changes are recorded in ibbackup_logfile and used to re create the ib_logfile files during the apply log phase ibbackup_redo_log_only Created instead of the ibbackup_logfile for incremental backups taken with Files that Are Backed Up File Name Pattern or Extension Relation to Original Data Files Notes the incremental with redo log only option ib_logfile Created in the backup directory by mysqlbackup during the apply log phase after the initial backup These files are not copied from the original data directory but rather re created in the backup directory during the apply log phase after
49. dir SMEB_BACKUPS_DIR backupdir include tables sales exclude tables sales hardware backup 41 Making a Partial Backup Taking a backup of all tables in the sales reps database but excludes the table with the name euro asia special characters like spaces or dashes are supported by the partial backup options since release 3 12 1 mysqlbackup host localhost user mysqluser protocol TCP port 3306 backup dir SMEB_BACKUPS_DIR backupdir include tables sales reps exclude tables sales reps euro asia backup Backing up all InnoDB tables but not frm files mysqlbackup defaults file home pekka my cnf only innodb backup You can also make compressed single image and other kinds of selective backups by using the appropriate command options Next Steps Make a note of the LSN value in the message at the end of both full and incremental backups for example mysqlbackup Was able to parse the log up to lsn LSN_number You specify this value when performing incremental backups of changes that occur after this full backup Apply the log to the uncompressed backup files so that the full backup is ready to be restored at any time You can move the backup data to a different server first to avoid the CPU and I O overhead of performing this operation on the database server After applying the log periodically take incremental backups which are much faster
50. ign ZO ARE O marys 204 12 55 04 my sqlbackup 4 buffers each of size 16777216 N E N N zi a e a aA FOS POS POs FO POs sql POS POS POS EOS POS FOs FO Full Image Backup operation starts with following threads hreads 1 write threads FO System tablespace file format is Antelope HOS Siceicame io COP eulil aimee ia ES Found checkpoint at 1lsn 1631766 Starting log scan from lsn 1631744 CopyAmiGuelocmrs beg copied lsh T6gl 766 Copying var lib mysql ibdatal Antelope file format Copying var lib mysql mysql innodb_index_stats ibd Antelope file form Copying var lib mysql mysql innodb_table_stats ibd Antelope file form Copying var lib mysql mysql slave_master_info ibd Antelope file forma Antelope file fo Copying var lib mysql mysql slave_worker_info ibd Antelope file forma Copying var lib mysql test2 tbl ibd Antelope file format Copying var lib mysql mysql slave_relay_log_info ibd Completing the copy of innodb files SCAU Same ice Cojo Wainer wea Wes lt Preparing to lock tables Connected to mysqld server Stantingrto lock ra Itlntalhicutecloikesemr All tables are locked and flushed to disk Completed the copy of binlog files Opening backup source directory var lib mysql Starting to backup all non innodb files in Adding database directory datadir mysql Adding database directory datadir performance_schema Completing the copy of all
51. incremental backups it creates except when they are created with the use tts option you can restore your database to its state at an arbitrary time txr in between a full backup and an incremental backup or in between two incremental backups To do so 1 Binary logging must be enabled in MySQL before taking the full backup that serves as the base for this restore operation 2 Using the full and incremental backups that were created before tz restore the database to a time as close to tg as possible and note that time let us call it ts Make sure the restored database is in a consistent state This can be achieved by for example using the copy back and apply log command for backup restore 58 Restoring a Backup with a Database Upgrade or Downgrade 3 Roll forward the database to its state at the desired time tz using the binary log 11 file s included in the incremental backup that covers tz Use the mysqlbinlog utility to extract from the binary log 11 file s all the SQL activities that happened in between the t s which you noted in step 2 above and tz specifying those times with the start datetime and stop datetime options and pipe the output to the mysql client to be replayed on the server mysqlbinlog start datetime ty _ stop datetime p binlog 000005 binlog 000006 binlog 000007 iMG U MeO e An alternative is to identify the beginning and endpoint of the extraction not by the s
52. jobs take e The MySQL Enterprise Monitor rules MySQL Enterprise Backup Failed MySQL Enterprise Backup Succeeded MySQL Enterprise Backup Lock Time Excessive Incremental MySQL Enterprise Backups Not Enabled and Last Full MySQL Enterprise Backup Too Old alert you to issues related to backup jobs The monitoring capability requires MySQL Enterprise Backup 3 5 3 and higher and MySQL Enterprise Monitor 2 3 4 and higher For information about these MySQL Enterprise Monitor features see the MySQL Enterprise Monitor User s Guide 10 2 Error codes of MySQL Enterprise Backup 75 Working Around Corruption Problems The return code of the MySQL Enterprise Backup mysqlbackup process is 0 if the backup or restore run succeeds If the run fails for any reason the return code is 1 10 3 Working Around Corruption Problems Sometimes the operating system or the hardware can corrupt a data file page in a location that does not cause a database error but prevents mysqlbackup from completing mysqlbackup Re reading page at offset 0 3185082368 in sqldata mts ibdatal5 mysqlbackup Re reading page at offset 0 3185082368 in sqldata mts ibdatal5 mysqlbackup Error page at offset 0 3185082368 in sqldata mts ibdatal5 seems corrupt A corruption problem can have different causes Here are some suggestions for dealing with it The problem can occur if the MySQL server is too busy Before trying other solutions you might want
53. large database a backup run might take a long time Always check that the mysqlbackup command has been completed successfully by verifying that mysqlbackup has returned the exit code 0 or by observing that mysqibackup has printed the text mysqlbackup completed OK mysqlbackup is not the same as the former MySQL Backup open source project from the MySQL 6 0 source tree The MySQL Enterprise Backup product supersedes the MySQL Backup initiative Schedule backups during periods when no DDL operations involving tables are running See Section B 1 Limitations of MySQL Enterprise Backup for restrictions on creating backups in parallel with the DDL operations 86 Chapter 12 mysqlbackup commands Table of Contents 12 1 BaCkUp Operatlons irern dooce tenet cabs duenecexsavedaaadgenecmenesecabs E A 87 12 2 Apply Log Operations vrceisesicecessniycccas bec na oii aeaa Gasabbeet ceaat Wud E AAAA AAA E eens 88 12 3 Restore Operation Sisina T acaesaed sau suis deaeynebenssatisl sash snabeeusateeideetaebeeees 89 12 4 Validation Operations w xecccsscc rect besweddessieosetannau tease zevactannebvedesdheeensanhanee aAa sa seloddest ataa 91 12 5 Single File Backup Operations ccecceeeeeeeeeeeee cece eae ee eeee sees ee aa eae eeeeeeeeeeaeaaaeneeeeeeeeeaeaaaaneeeeeees 93 These are commands for the major operations for mysqibackup Only one of them can be specified for each mysqlbackup invocation and unlike the comman
54. meta MEB_2014 12 04 13 10 datadir var lib mysql innodb_data_home_dir var lib mysql innodb_data_file_path ibdatal 12M autoextend innodb_log_group_home_dir var lib mysql innodb_log_files_in_group 2 innodb_log_file_size 50331648 innodb_page_size 16384 innodb_checksum_algorithm innodb datadir home admin backup tmp datadir innodb_data_home_dir home admin backup tmp datadir innodb_data_file_path ibdatal 12M autoextend innodb_log_group_home_dir home admin backup tmp datadir innodb_log_files_in_group 2 innodb_log_file_size 50331648 innodb_page_size 16384 innodb_checksum_algorithm innodb mysqlbackup INFO Creating 14 buffers each of size 16777216 141204 13 10 39 mysqlbackup INFO Copy back and apply log operation starts with following threads 33 Backup Scenarios and Examples re 204 204 204 204 204 204 204 204 204 204 204 204 204 204 204 204 204 204 204 mysql mS is i SS Ss is SS se eS Se Ss Ss Ss Ss mysql 41204 1 re mysql 41204 mysql mysql mysql 41204 mysql 41204 41204 41204 nnoDB nnoDB backup INFO backup INFO ad threads 6 process threads 1 write threads 13 10 39 mysqlbackup INFO Copying database directory meta 13 10 39 mysqlbackup INFO Copying datadir ibdatal 13 10 39 mysqlbackup INFO Copying datadir mysql innodb_index_stats ibd 13 10 39 mysqlbackup INFO Copying datadir
55. meta subdirectory Default All entries are extracted dst entry PATH Command Line Format dst entry PATH Permitted Values Type path name Used with single file backups to extract a single file or directory to a user specified path Use of this option requires specifying the src entry option This option specifies the destination path for the entry selected from the backup image by src entry The entry could point to a single file or single directory For example to retrieve the comments file from a backup image and store it as tmp my comments txt use a command like the following mysqlbackup src entry meta comments txt dst entry tmp my comments txt backup image var myimage bki extract Similarly to extract all the contents of the meta directory in a single file backup as data my meta use a command like the following mysqlbackup src entry meta dst entry data my meta backup image var myimage bki extract The specified path is a simple path name without any wildcard expansion or regular expressions Default By default original pathnames are uke to create files in the local file system Performance Scalability Capacity Options e sbt database name NAME Command Line Format sbt database name NAME Permitted Values Type string Default MySQL For tape backups this option can be used as a hint to the Media Manag
56. must pass on to the recipients the same freedoms that you received You must make sure that they too receive or can get the source code And you must show them these terms so they know their rights Developers that use the GNU GPL protect your rights with two steps 1 assert copyright on the software and 2 offer you this License giving you legal permission to copy distribute and or MOCHE iea For the developers and authors protection the GPL clearly explains that there is no warranty for this free software For both users and authors sake the GPL requires that modified versions be marked as changed so that their problems will not be attributed erroneously to authors of previous versions Some devices are designed to deny users access to install or run modified versions of the software inside them although the manufacturer can do so This is fundamentally incompatible with the aim of protecting users freedom to change the software The systematic pattern of such abuse occurs in the area of products for individuals to use which is precisely where it is most unacceptable Therefore we have designed this version of the GPL to prohibit the practice for those products If such problems arise substantially in other domains we stand ready to extend this provision to those domains in future versions of the GPL as needed to protect the freedom of users Finally every program is threatened constantly by software patents States shou
57. mysqlbackup automatically copies the frm files during a backup operation and restores the files during a restore operation Data from MyISAM and Other Storage Engines mysqlbackup also backs up the MYD files MYI files and the frm files associated with the MyISAM tables Files with other extensions that are backed up are shown in this list 16 Generated Files Included in the Backup tables the MySQL server to be backed up must support InnoDB i e the backup process will fail if the server was started up with the innodb OFF or skip innodb option and the server must contain at least one InnoDB table Note R While MySQL Enterprise Backup can back up non InnoDB data like MYISAM MyISAM tables and these other types of files cannot be backed up in the same non blocking way as InnoDB tables can They are backed up using the warm backup technique changes to these tables are prevented while they are being backed up possibly making the database unresponsive for a time but no shutdown is required during the backup Note R To avoid concurrency issues during backups of busy databases you can use the only innodb or only innodb with frm option to back up only InnoDB tables and associated data Generated Files Included in the Backup The backup data includes some new files that are produced during the backup process These files are used to control later tasks such as verifying and restoring the backup d
58. no connection connect if online Most other connection parameters used by the mysql command are recognized but silently ignored Unknown connection parameters cause mysqlbackup to stop 104 Server Repository Options The following connections options are specific to mysqlbackup no connection The no connection option supersedes the other connection options and uses file level operations to perform the backup When you use this option you must specify in the configuration file or on the command line many options whose values are normally retrieved automatically through the database connection Warning O This option also turns on the no history logging and no locking options which might result in inconsistencies in non InnoDB data if the tables are modified during the backup operation It might also affect subsequent incremental backups see the description for the incremental base option for details connect if onlin By default a database connection is used for backup operations both during the initial stage to retrieve source repository configuration and to lock tables while copying non InnoDB data This option allows mysqlbackup to make connection attempts in both phases but continues even if the connection cannot be established If a connection cannot be established the processing is the same as with the no connection option This option can be useful in emergency situations for example
59. paths for InnoDB data files in the backup with this option you must set the backup_innodb_data_home option to empty string in addition to using an absolute path for this option When the parameter is not specified it inherits the value from the value of the innodb_data_file_path option on the backed up server If both the source and destination of the backup attempt to use the same absolute paths that resolves to the same files the backup is cancelled The value of the parameter is stored into the backup my cnf file as innodb_data_file_path for information so that mysqlbackup can understand the structure of the backup when it performs various operations on the backup backup_innodb_log_group_home_dir PATH The directory under which the backup s InnoDB logs will be stored Specify this option only if you want to put the logs at somewhere other than the default location which is backup dir datadir If the value of the parameter is different from backup dir datadir itis stored in the backup my cnf file as innodb_log_group_home_dir for information so that mysqlbackup can understand the structure of the backup when it performs various operations on the backup Note that while you can specify a directory for saving the logs the names of the log files are fixed and not reconfigurable This parameter is applicable only for backup operations during a restore the InnoDB log files are restored under the data directory specified b
60. permit incorporating your program into proprietary programs If your program is a subroutine library you may consider it more useful to permit linking proprietary applications with the library If this is what you want to do use the GNU Lesser General Public License instead of this License But first please read lt http www gnu org philosophy why not lgpl html gt GCC RUNTIME LIBRARY EXCEPTION Version Soil Sil March 2009 Copyright 2009 Free Software Foundation Inc lt http fsf org gt Everyone is permitted to copy and distribute verbatim copies of this license document but changing it is not allowed his GCC Runtime Library Exception Exception is an additional ermission under section 7 of the GNU General Public License version GPLv3 It applies to a given file the Runtime Library hat bears a notice placed by the copyright holder of the file tating that the file is governed by GPLv3 along with this Exception GP tor Gy ey isl When you use GCC to compile a program GCC may combine portions of certain GCC header files and runtime libraries with the compiled program The purpose of this Exception is to allow compilation of non GPL including proprietary programs to use in this way the header files and runtime libraries covered by this Exception 0 Definitions A file is an Independent Module if it either requires the Runtime Library for execution after a Compilation Process or makes use of
61. process is cancelled If you also use the suspend at end option the utility specified by xec when locked is executed after the suspension is lifted 138 Chapter 14 Configuration Files and Parameters You can specify mysqlbackup options either on the command line or as configuration parameters inside a configuration file This section describes the use of configuration files In general mysqlbackup follows the mysqi style of processing configuration options mysqlbackup and client group options are passed as command line options Any command line options that you specify override the values from the configuration file and in the case of duplicate options the last instance takes precedence mysqlbackup also reads options in the mysqld group to detect parameters related to the source repository when no connection to mysqld is available The underscore characters in parameter names can be replaced with dashes and treated as synonyms similar to mysqld parameters that use this same convention See Using Options on the Command Line in the MySQL Reference Manual for details The documentation typically lists the names with underscores to match the output of the SHOW VARIABLES statement Options Files mysqlbackup reads the location of the MySQL data to back up from in order of priority The connection information from the running database whenever possible Thus in most cases you can avoid specifying most options
62. process slower The tradeoff between backup time and restore time You might choose a set of options resulting in a slightly slower backup if those options enable the restore to be much faster See Section 7 2 Optimizing Restore Performance for performance information for the restore process Full or Incremental Backup After taking a full backup subsequent backups can be performed more quickly by doing incremental backups where only the changed data is backed up For an incremental backup specify the incremental or incremental with redo log only option to mysqibackup See Section 13 7 Incremental Backup Options for information about these options For usage instructions for the backup and apply stages of incremental backups see Section 4 3 2 Making a Differential or Incremental Backup and Example 5 3 Applying an Incremental Backup to a Full Backup Compressed Backup Compressing the backup data before transmitting it to another server involves additional CPU overhead on the database server where the backup takes place but less network traffic and less disk I O on the server that is the final destination for the backup data Consider the load on your database server the bandwidth of your network and the relative capacities of the database and destination servers when deciding whether or not to use compression See Section 4 3 3 Making a Compressed Backup and Section 13 6 Compression Options
63. right directories for the new slave Edit the my cnf file of the new slave and put skip slave start event_scheduler off and sql_log_bin 0 under the mysqld section Start the new slave server Connect to the slave server with the mysq1 Client When a server using the GTID feature is backed up mysqlbackup produces a file named backup_gtid_executed sql inside the meta folder under the backup directory The file contains a SQL statement that sets the GTID_PURGED configuration option on the slave On a new slave issue the following command if GTIDs are enabled SET GLOBAL GTID_PURGED f65db8e2 0ela 11e5 a980 080027755380 1 3 It also contains a commented out CHANGE MASTER command for initializing the slave Uncomment the command and add any needed connection and authentication parameters to it for example Use the following command if you want to use the GTID handshake protocol CHANGE MASTER TO MASTER_HOST 127 0 0 1 MASTER_USER muser MASTER_PASSWORD mpass MASTER_PORT 18675 Execute the file with the mysqi client mysql gt source path to backup_gtid_executed sql backup_gtid_executed sql Set the statuses of any events that were copied from the master to SLAVESIDE_DISABLED For example mysql gt UPDATE mysgql event SET status SLAVESIDE_DISABLED Remove the skip slave start event_scheduler off and sql_log_bin 0 entries you added to the my cnf file of the slave in step 2 Restar
64. row formats are introduced to support the resulting improvements in storage efficiency and performance 182 Each table has its own row format specified through the ROW_FORMAT option To see the row format for each InnoDB table issue the command SHOW TABLE STATUS Because all the tables in the system tablespace share the same row format to take advantage of other row formats typically requires setting the innodb_file_per_table option so that each table is stored in a separate tablespace S SBT Acronym for system backup to tape See Also system backup to tape selective backup Another name for partial backup See Also partial backup selective restore selective restore Another name for partial restore See Also partial restore selective backup server A MySQL instance controlled by a mysqla daemon A physical machine can host multiple MySQL servers each requiring its own backup operations and schedule Some backup operations communicate with the server through a connection See Also connection instance server repository Contrast with backup repository See Also backup repository repository single file backup A backup technique that packs all the backup data into one file the backup image for ease of storage and transfer The streaming backup technique requires using a single file backup See Also image streaming slave In a replication configuration a database server that receives updates from a master ser
65. separate and independent works which are not by their nature extensions of the covered work and which are not combined with it such as to form a larger program in or on a volume of a storage or distribution medium is called an aggregate if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation s users beyond what the individual works permit Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate 6 Conveying Non Source Forms You may convey a covered work in object code form under the terms of sections 4 and 5 provided that you also convey the machine readable Corresponding Source under the terms of this License in one of these ways a Convey the object code in or embodied in a physical product including a physical distribution medium accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange b Convey the object code in or embodied in a physical product including a physical distribution medium accompanied by a written offer valid for at least three years and valid for as long as you offer spare parts or customer support for that product model to give anyone who possesses the object code either 1 a copy of the Corresponding Source for all the software in the product that is covered by this License on a 157 GNU General Public License Ve
66. shows how to perform a full backup verify it and then restore it to a server 4 2 1 Backing Up an Entire MySQL Instance In the following example we back up an entire MySQL instance to a single file using the backup to image command which appears at the end of the sample command We specify some of the connection information for the database using the user and host options and with the password option tell the MySQL server to prompt for a user password The location and filename for the single file backup is specified using the backup image option and the location for an empty folder to store temporary files is supplied with the backup dir option The output echoes all the parameters used by the backup operation including several that are retrieved automatically using the database connection The unique ID for this backup job is recorded in special tables that mysqlbackup creates inside the MySQL instance allowing you to monitor long running backups and view information on previous backups The final output section repeats the location of the backup data and provides the LSN values that you might use when you perform an incremental backup next time over the full backup that has just been made mysqlbackup user root password host 127 0 0 1 backup image home admin backups my mbi backup dir home admin backup tmp backup to image MySOL Enterprise Backup version 3 12 1 Linux 2 6 18 274 615 1686 2014 11 1
67. size of the backup will be larger when comparing with an ordinary backup Therefore users should be careful in identifying which tables are inactive and which are busy when trying to perform an optimistic backup Note R An optimistic backup cannot be performed for an incremental backup or a backup using transportable tablespaces TTS The following examples illustrate how to make an optimistic backup Example 4 21 Optimistic Backup Using the Option optimistic time YYMMDDHHMMSS In this example tables that have been modified since the noon of May 16 2011 are treated as busy tables and backed up in the normal phase of an optimistic backup and all other tables are backed up in the optimistic phase mysqlbackup defaults file etc my cnf optimistic time 110516120000 backup Example 4 22 Optimistic Backup Using the Option optimistic time now In this example all tables are treated as inactive tables and backed up in the optimistic phase of an optimistic backup mysqlbackup defaults file etc my cnf optimistic time now backup Example 4 23 Optimistic Backup Using the optimistic busy tables Option In this example tables in mydatabase that are suffixed by mytables in their names are treated as busy tables and backed up in the normal phase of an optimistic backup and all other tables are backed up in the optimistic phase mysqlbackup defaults file etc my cnf optimistic busy tables mydatabase mytables backup 5
68. smaller backup files with size reduction influenced by the compression level setting Suitable for keeping multiple sets of non critical backup files For recent backups of critical data you might leave the data uncompressed to allow fast restore speed in case of emergency MySQL Enterprise Backup can apply compression to the contents of InnoDB tables during the backup process turning the ibd files into ibz files Compression adds CPU overhead to the backup process and requires additional time and disk space during the restore process See Also backup compression level ibd file ibz file InnoDB restore compression level A setting that determines how much compression to apply to a compressed backup This setting ranges from 0 none 1 default level when compression is enabled to 9 maximum The amount of compression for a given compression level depends on the nature of your data values Higher compression levels do impose additional CPU overhead so ideally you use the lowest value that produces a good balance of compression with low CPU overhead See Also compression configuration file The file that holds the startup options of the MySQL server and related products and components Often referred to by its default file name my cnf on Linux Unix and OS X systems and my ini on Windows systems The MySQL Enterprise Backup stores its default configuration settings in this file under a mysqlbackup section For convenienc
69. stdout file FILENAME fifo FIFONAME table variable Command Line Format show progress destinations Permitted Values Type enumeration Valid stderr Values oe aout Eal file FILENAM fifo FIFONAM GI table variable The option instructs mysqibackup to periodically output short progress reports known as progress indicators on its operation 131 Progress Report Options The argument of the option controls the destination to which the progress indicators are sent e stderr Progress indicators are sent to the standard error stream The report is embedded in a time stamped mysqlbackup INFO message For example 130607 12 22 38 mysql backup INFO Progress 191 of 191 MB state Completed e stdout Progress indicators are sent to the standard output stream A single newline character is printed after each progress indicator e file FILENAME Progress indicators are sent to a file Each new progress report overwrites the file and the file contains the most recent progress indicator followed by a single newline character e fifo FIFONAME Progress indicators are sent to a file system FIFO A single newline character is printed after each progress indicator Warning If there is no process reading the FIFO the mysqlbackup process hangs at the end of the execution e table Progress indicators are sent to the mysql backup_progress table Th
70. tables in a MySQL database or some of the databases in a MySQL instance Contrast with full backup Related mysqibackup options are include tables xclud tables use tts only known file types and only innodb See Also backup database full backup partial restore table partial restore A restore operation that applies to one or more tables or databases but not the entire contents of a MySQL server The data being restored could come from either a partial backup or a full backup Related mysqlbackup options are include tables xclude tables and renam See Also database full backup partial backup restore table physical backup A backup that copies the actual data files For example the MySQL Enterprise Backup command produces a physical backup because its output contains data files that can be used directly by the mysqld server Contrast with logical backup See Also backup logical backup point in time The time corresponding to the end of a backup operation A prepared backup includes all the changes that occurred while the backup operation was running Restoring the backup brings the data back to the state at the moment when the backup operation completed See Also backup prepared backup restore prepared backup The set of backup data that is entirely consistent and ready to be restored It is produced by performing the apply operation on the raw backup See Also apply raw backup 181 progress
71. take an incremental backup specify the incremental or incremental with redo log only along with the incremental backup dir option All InnoDB data modified after the specified LSN is copied in the incremental backup Depending on whether incremental or incremental with redo log on1y Is used other options are required or recommended e incremental Specifies that the associated backup or backup to image operation is incremental Also requires either the incremental base option or the combination of the start l1sn and incremental backup dir options Only InnoDB tables are backed up incrementally By default all non InnoDB and frm files are included into the incremental backup and in their fullness To exclude non InnoDB data in an incremental backup use the only innodb option 7 incremental with redo log only Specifies that an incremental backup is to be created using only the redo log This alternate type of incremental backup has different performance characteristics and operational limitations comparing to backups created with the incremental option see Creating Incremental Backups Using Only the Redo Log for a discussion on their differences 113 Incremental Backup Options To use this option you also need to specify the incremental base option or a combination of the start lsn and incremental backup dir options Just like with the incremental option only
72. the initial backup using the changes recorded in the ibbackup_logfile file Renamed version of each isl file from the backed up server A isi file is created when you specify the location of an InnoDB table using the syntax CREATE TABLE DATA DIRECTORY to act like a symbolic link pointing to the tablespace file See Creating a File Per Table Tablespace Outside the Data Directory for details The b1 files might or might not be turned back into is1 files during the copy back operation If the specified directory does not exist on the server where the backup is restored mysqlbackup attempts to create it If the directory cannot be created the restore operation fails Thus if you would like to use the DATA DIRECTORY clause to put tables at different locations or to restore to a server with a different file structure where the corresponding directories cannot be created edit the b1 files before restoring to point to directories that do exist on the destination server If the directory on the target server pointed to by a b1 file already contains ibd files the force 103 option is required when you restore the backup Timestamped directory such as 2011 05 26_13 42 02 Created by the with timestamp option All the backup files go inside this subdirectory Use the with timestamp option to easily keep more than one set of backup data under the same main backup d
73. the log files in the right directories for the new slave 2 Edit the my cnf file of the new slave and put skip slave start and event_scheduler off under the mysqld section 3 Start the new slave mysqld version gt 5 1 It prints the latest MySQL binary log position the backup knows of InnoDB Last MySQL binlog file position 0 128760128 file name hundin bin 006 Note that InnoDB only stores the binary log position information to its tablespace at a transaction commit To make InnoDB aware of the current binary log position you must run at least one transaction while binary logging is enabled 4 Use the CHANGE MASTER SQL command on the slave to initialize it properly For example CHANGE MASTER TO MASTER_LOG_FILE hundin bin 006 MASTER_LOG_POS 128760128 5 Set the statuses of any events that were copied from the master to SLAVESIDE_DISABLED For example mysql gt UPDATE mysgql event SET status SLAVESIDE_DISABLED 6 Remove the line skip slave start and event_scheduler off entries you added to the my cnf file of the slave in step 2 61 Backing up and Restoring a Slave Database 7 Restart the slave server Replication starts For servers using GTIDs supported by MySQL Server 5 6 and after 1 8 Take a backup of the master transfer it to a GTID enabled slave use mysqlbackup with the apply log option to prepare it and put the restored backup and the log files in the
74. to keep track store and transport mysqlbackup can create a backup in a single file format It can also pack an existing backup into a single file unpack the single file back to the original backup directory structure list the contents of a single file backup verify the contents of a single file backup against embedded checksums or extract a single file into a directory tree For the syntax of the relevant mysqlbackup options see Section 13 9 Single File Backup Options Because the single file backup can be streamed or piped to another process such as a tape backup or a command like scp you can use the technique to put the backup onto another storage device or server and avoid significant storage overhead on the original database server To create a single file backup use the backup to image command The following examples illustrate how to perform a single file backup and other related operations Example 4 3 Single File Backup to Absolute Path This command creates a single backup image on the given absolute path It still requires backup dir which is used to hold temporary output status and metadata files mysqlbackup backup image backups sales mbi backup dir backup tmp backup to image Example 4 4 Single File Backup to Relative Path This command specifies backup image with a relative path underneath the backup directory The resulting single file backup is created as backups sales mbi mysqlbackup backu
75. use this software or hardware in dangerous applications then you shall be responsible to take all appropriate fail safe backup redundancy and other measures to ensure its safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International Inc AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices UNIX is a registered trademark of The Open Group This software or hardware and documentation may provide access to or information about content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services unless otherwise set forth in an applicable agreement between you and Oracle Oracle Corporation and its affiliates will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services except as set forth in an applicable agreement between you and Oracle
76. when the database server goes down during the backup operation 13 3 Server Repository Options These repository options specify various parameters related to the database server from which the data is backed up or to which a backup is restored These options are used only with the following operations Backup creation operations backup backup and apply log backup to image Restore operations copy back copy back and apply log When a database connection is available during a backup the parameters describing the source repository are ignored overridden by the corresponding values retrieved from the database connection For information about how these options are specified for the MySQL server click the option names to see the descriptions in the MySQL Reference Manual datadir PATH This is the datadir value used by the MySQL instance The frm files reside here inside subdirectories named after the databases inside the instance When a database connection exists the value is retrieved automatically and overrides any value you specify This is a crucial parameter for both the MySQL server and MySQL Enterprise Backup innodb_data_home_dir PATH Specifies the directory where InnoDB data files reside Usually the same as dat adir but can be different This parameter together with innodb_data_file_path SIZE determines where the InnoDB data files such as ibdatal ibdata2 and so on are situated within the MySQL server
77. work as a whole that a is included in the normal form of packaging a Major Component but which is not part of that Major Component and b serves only to enable use of the work with that Major Component or to implement a Standard Interface for which an implementation is available to the public in source code form A Major Component in this context means a major essential component kernel window system and so on of the specific operating system if any on which the executable work runs or a compiler used to produce the work or an object code interpreter used to run it 155 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 The Corresponding Source for a work in object code form means all the source code needed to generate install and for an executable work run the object code and to modify the work including scripts to control those activities However it does not include the work s System Libraries or general purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work For example Corresponding Source includes interface definition files associated with source files for the work and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require such as by intimate data communication or control flow between tho
78. zlib ZLIB v1 2 3 This is in between the other two supported algorithms in terms of both speed and compression ratio ZLIB was the only compression algorithm available for MySQL Enterprise Backup versions prior to 3 10 112 Incremental Backup Options Default Iz4 Explicitly specifying a value for the option through a configuration file or command line automatically enables the compress option compress level LEVEL Command Line Format compress level LEVEL Permitted Values Type numeric Default 1 Min 0 Value Max 9 Value Specifies the level of compression ranging from 0 to 9 O disables compression 1 is fastest compression and 9 is highest and slowest compression The option is only meaningful for compression using the ZLIB or LZMA algorithm it is ignored when any other algorithms are selected by the compress method option Default 1 lowest and fastest compression Explicitly specifying a non zero value through a configuration file or command line automatically enables the compress option uncompress When used with the apply log or copy back and apply log operation uncompresses the compressed backup before applying the InnoDB log 13 7 Incremental Backup Options For an overview of incremental backups and usage examples for these options see Section 4 3 2 Making a Differential or Incremental Backup To
79. 0 Making a Back Up of In Memory Database Data When you use both the optimistic time and optimistic busy tables options and they come into conflict on determining which tables are to be busy tables opt imistic busy tables takes precedence over optimistic time For example Example 4 24 Optimistic and Partial Backup Using both the optimistic busy tables and optimistic time Options In this example tables in mydat abase that are suffixed by mytables in their names are treated as busy tables and backed up in the normal phase even if they have not been modified since May 16 2010 the time specified by opt imistic time mysqlbackup defaults file etc my cnf optimistic busy tables mydatabase mytables optimistic time 100516 backup 4 3 7 Making a Back Up of In Memory Database Data The xec when locked option of mysqlbackup lets you specify a command together with the desired command arguments to run near the end of the backup while the database is still locked This command can copy or create additional files in the backup directory For example you can use this option to back up MEMORY tables with the mysqldump command storing the output in the backup directory To delay any redirection or variable substitution until the command is executed enclose the entire option value within single quotes 4 3 8 Making Scheduled Backups Maintaining a regular backup schedule is an important measure for prevent
80. 0 2 cee eeeeecteeeee cee eeeeeeaaeeeeeeaaeeees 51 4 3 8 Making Scheduled Backups cccceceeceeeeeeeeeeeeeeaeaaeaeeeeeeeeeeaeaaaaeeeeeeeeeeaeaaaaneeseeees 51 4 4 Making Backups with a Distributed File System DFS or Storage Access Network SAN 52 5 Recovering or Restoring a Database 2000 cece reenter e eee e eee ee ee ENEAN EENAA EKARA 53 5 1 Preparing the Backup to be Restored 2 00 eeececeeeeeeeceeeeeee ae eeeeeeaaeeeeeeaaeeeeeeaaeeeeeeaaeeeeeeaaaeees 53 5 2 Performing a Restore Operation 0cccccceeeeeeeceeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeneeeeeeeees 54 5 2 1 Restoring a Compressed Backup cccceeeceeeeeeeeeeeeeeeeeaeeaeeeeeeeeeeeeaeaaeneeeeeeeeeaeaaea 55 5 2 2 Restoring an Encrypted Backup Image cc eeeeecenneeeeeeeeeeeeeeaaeeeeeeaaeeeeeeaaaeeeeaaeeeees 56 5 2 3 Restoring an Incremental Backup ccccceeeeeeeeeeeeeeeeeaeeaeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaenees 56 5 2 4 Restoring Backups Created with the use tts OPTION 00 cece cece seeeeeeeeeeeeeeees 57 5 2 5 Restoring a Backup from Cloud Storage to a MySQL Server cecceeeeeeeeeeeeeeeeee eee 58 5 3 Point in Time Recovery from a Hot Backup cceceeeeeeeeeeeeeeeeeeeeeeeaeaaeaeeeeeeeeeeaeaaaaneneeeees 58 5 4 Restoring a Backup with a Database Upgrade or Downgrade cccceeeeeeeeeeeeeeeeeaeeeeeeees 59 6 Using MySQL Enterprise Backup with Replication ccccceeec
81. 10 5 Using the MySQL Enterprise Backup Manifest This file is not modified once created You can prevent this file from being generated by specifying the disable manifest option comments txt Produced by the comments or comment s file option The comments are specified by you to document the purpose or special considerations for this backup job gtid_executed sql Signifies the backup came from a server with GTIDs enabled GTIDs are a replication feature in MySQL 5 6 and higher See Replication with Global Transaction Identifiers for details When you back up a server with GTIDs enabled using mysqlbackup the file named backup_gtid_executed sql is created in the meta folder under the backup directory Edit and execute this file after restoring the backup data on a slave server see Section 6 1 Setting Up a New Replication Slave for details server my cnf Contains values of the backed up server s global variables that are set to non default values Use this file or server all cnf to start the target server for restoration During a copy back or copy back and apply log operation the server repository options values e g datadir innodb_data_home_dir etc in the file are modified if the command makes changes to them through the command options However during an apply incremental backup operation the values already saved in the file take precedenc
82. 1631744 nd lsn 1631766 start checkpoint 1631766 13 10 44 lem 16 backup INFO L 13 10 44 mysql Doing recovery backup INFO PROGEASE am jercemce 12345 6 7 8 S IO di 12 13 14 15 16 17 18 19 20 2 22 23 24 25 2ORMrA 29 3 nno nno nno bac 31766 mysql ast bac scanned up to log sequence number 1631766 DB Starting an apply batch of llog records to the databace lt DB Setting log file size to 50331648 DB Setting log file size to 50331648 kup INFO We were able to parse ibbackup_logfile up to MySQL binlog file position 0 120 file name mysqld bin 000004 120 kup INFO The first data file is var lib mysql ibdatal and the new created log files are at var lib mysql 13 10 44 ALS Qt A mysql mysql bac bac kup INFO Apply log operation completed successfully kup INFO Full Backup has been restored successfully mysqlbackup completed OK Now the original database directory is restored from the backup and you can restart the database server 4 3 Backup Scenarios and Examples 4 3 1 Making a Full Backup Most backup strategies start with a complete backup of the MySQL server from which you can restore all databases and tables After you have created a full backup you might perform incremental backups which are smaller and faster for the next several backup tasks You then make a full backup periodically to begin the cycle again For sample commands for making a fu
83. 2 Copyright c 2003 2014 Oracle and or its affiliates All Rights Reserved mysqlbackup INFO Starting with following command line mysqlbackup user root password host 127 0 0 1 backup image home admin backups my mbi backup dir home admin backup tmp backup to image mysqlbackup INFO Enter password mysqlbackup INFO MySQL server version is 5 6 17 log mysqlbackup INFO Got some server configuration information from running server IMPORTANT Please check that mysqlbackup run completes successfully At the end of a successful backup to image run mysqlbackup prints mysqlbackup completed OK 141204 12 54 55 mysqlbackup INFO MEB logfile created at home admin backup tmp meta MEB_2014 12 04 12 54 55_ 30 Backing Up an Entire MySQL Instance var lib mysql db_log_group_home_dir db_log_files_in_group db_log_file_size 50331648 16384 db_checksum_algorithm db_undo_directory var lib mysql db_undo_tablespaces 0 128 db_data_file_path ibdatal 12M autoextend var lib mysql 2 innodb Ba m m 4 S PP RR RRR RRR HR HR HRB KB HKRHK HEB mS 1 1 ES ES SS fy home admin backup tmp datadir db_log_group_home_dir 2 54 58 mysqlbackup 2 54 58 mysqlbackup Copying meta file home admin backup tmp backup my cnf Copying meta file home admin backup tmp meta backup_create xml INFO Creating 2 54 58 mysqlbackup d
84. 204 12 55 08 mysqlbackup INFO MySQL binlog position filename mysqld bin 000004 position 120 Start LSN 1631744 End LSN 8 LESI7OG mysqlbackup completed OK 4 2 2 Verifying a Backup To verify that your backup has been successful restore the backup data on a different server and run the MySQL daemon mysqld on the new data directory You can then execute SHOW statements to verify the database and table structures and execute queries to verify further details of the database See Section 4 2 3 Restoring a Database at its Original Location for basic steps for restoring a backup and see Chapter 5 Recovering or Restoring a Database for more detailed instructions Running the mysqld daemon on the restored data requires a valid configuration file which you specify with the defaults file option of the mysqld command You can reuse most of the settings from the original my cnf file of the backed up MySQL instance combined with the settings from the backup my cnf file which was created in the temporary directory you specified with backup dir when you created a single image backup see Section 4 2 1 Backing Up an Entire MySQL Instance and contains a small subset of parameters required by mysqlbackup Create a new configuration file by concatenating the two files mentioned above into a new one and use that file on the server on which you perform the verification Edit the file to make sure the dat adir param
85. 4 Standard OPTIONS xccsseedsiesaccastenevieag A T E R E 102 13 2 Connection OPONS ressasiar aiias eunan AEA ANA a AEEA A aE AE aA AAEL EREA EA AARAA 104 13 3 Server Repository Options csser rnnr iaa aei aaia kaadaa aadi 105 13 4 Backup Repository Options wessssscecctsseecodstssaeveh ante vedsab ee ccebaansonesbiveesesaehcvedaahieecebieneredsbasensebacnceedsd 107 13 5 Metadata Options rre temne A E A 111 13 6 Compression Options vss cecvetsesiededseneeceessayeden ae AE A AAAA abodes lads eceshuebalveaidsnessbeledeabdeesebeds 112 13 7 Incremental Backup Options 0 cccceeeeee ee aeeeeeeeee eres ee eae ete eeee sees ee aaaaeeeeeeeeeeeeaaaaaeneeeeeeeeeaeaaea 113 13 8 Partial Backup and Restore Options 0 ccccceeeceeeeeeeeeeee tees aa eeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaaaeeeeeseeeeeeaaa 115 13 9 Single File Backup Options 00 ccecceeeeeeae ee eeeeeeee ee ee ee aa eee ee teense seca aaaaaaeeeeeeseaaaaaaeeeeeeseeaeaaaaaes 121 13 10 Performance Scalability Capacity Options 0 ccc cece eeeeeeee cece ae eeeeeeeeeeee ee aeaaeeeeeeeeeeeeaeaaeeaes 123 13 11 Message Logging Options i taissr inasnan aai a ee eeee A E a EAEE Ea 130 13 12 Progress Report OptiOns msiiserrsseiiisninuaninn iagi aai aaea Ea e Aaa aA Na ASRA 131 13 19 Enciyptiom OPIONS garcterencdect jaceecarzenvdcatsgdveiaveravdced EEEE E 134 13 14 Cloud Storage Options ssisasinssn nennu o iia aa O a Eea EEEE A Aaa 135 13 15 Options for Special Backup Types
86. 471 mysqlbackup Was able to parse the log up to lsn 2666737471 mysqlbackup Maximum page number for a log record 0 101208 17 17 45 mysqlbackup Full backup completed The backup directory contains only backups of ibstest and ibtest09 tables Other InnoDB tables did not match the include pattern test ib Notice however that the tables ibtestila ibtest1lb ibtestilc ibtestild are in the backup even though they are not visible in the directory shown below because they are stored in the system tablespace ibdatai file which is always included in the backup With the only innodb option ls sqldata backup test ibstest0 ibd ibtest09 ibd With the only innodb with frm related option ls sqldata backup test ibstest0 frm ibtest09 frm ibstest0 ibd ibtest09 ibd Example 4 2 Making a Compressed Partial Backup We have configured MySQL so that every InnoDB table has its own tablespace We make a partial backup including only those InnoDB tables whose name starts with alex or blob The contents of the database directory for test database is shown below ls sqldata mts test alexl frm alex2 ibd blobt3 frm ibstest0O ibd ibtestlla frm ibtestlld frm alexl ibd alex3 frm blobt3 ibd iptestoO fam sallotesiedeliion tram alex2 frm alex3 ibd ibstestO frm ibtest09 ibd ibtestllc frm We run mysqlbackup with the compress and include options mysqlbackup defaults file home pekka my cnf compress include
87. 992 1993 1994 1997 Henry Spencer All rights reserved This software is not subject to any license of the American Telephone and Telegraph Company or of the Regents of the University of CRONNI Permission is granted to anyone to use this software for any purpose on any computer system and to alter it and redistribute it subject to the following restrictions 1 The author is not responsible for the consequences of use of this software no matter how awful even if they arise from flaws in it 2 The origin of this software must not be misrepresented either by explicit claim or by omission Since few users ever read sources credits must appear in the documentation 3 Altered versions must be plainly marked as such and must not be misrepresented as being the original software Since few users ever read sources credits must appear in the documentation 4 This notice may not be removed or altered E 11 RFC 3174 US Secure Hash Algorithm 1 SHA1 License The following software may be included in this product RFC 3174 US Secure Hash Algorithm 1 SHA1 RFC 3174 US Secure Hash Algorithm 1 SHA1 Copyright C The Internet Society 2001 All Rights Reserved This document and translations of it may be copied and furnished to others and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared copied published and distributed in whole or in part without restriction of an
88. An Incremental backup is enabled with one of the two options incremental and incremental with redo log only option See Creating Incremental Backups Using Only the Redo Log for their differences When creating an incremental backup you have to indicate to mysqibackup the point in time of the previous full or incremental backup For convenience you can use the incremental base option to automatically derive the necessary log sequence number LSN from the metadata stored in a previous backup directory or on the server Or you can specify an explicit LSN value using the start 1sn option providing to mysqlbackup the ending LSN from a previous full or incremental backup To prepare the backup data to be restored you combine all incremental backups with an original full backup Typically you perform a new full backup after a designated period of time after which you can discard the older incremental backup data Creating Incremental Backups Using Only the Redo Log The incremental with redo log only might offer some benefits over the incremental option for creating an incremental backup e The changes to InnoDB tables are determined based on the contents of the InnoDB redo log Since the redo log files have a fixed size that you know in advance it can require less I O to read the changes from them than to scan the InnoDB tablespace files to locate the changed pages depending on the size of your database amount of D
89. Around Corruption Problems ccccceceeeeeeeeeeeeeeeeaaeeeeeeeeeeeeeeaaeaeneeeeeeeeeaaa 10 4 Using the MySQL Enterprise Backup LOgS ccseceeeeeeeeeeeeeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaa 10 5 Using the MySQL Enterprise Backup Manifest 0 0 c cceeeeeeeaceeeeeeeeeeeeeeaeaaenneeeeeees lll mysqlbackup Command Reference cccccccccseeceeeneeeeeeseeeeeeeseeeeeeesaeeeeeesaeseeeesseeeessaaeeeessaaneeenea A Nasik Zot gill boae ul oneness eet eer emer A E rece merry ree correc errr erect 12 mysglback up COMMAMNAS sw ccssssicacsassvtotcanancenesadunenenaadavecusnedeweananaucdaes saednahlienccans Ea AEA nines 1231 BackUp Operations ieccaccsdenciesaahecneencve cans shdesaeescentan E R TER 12 2 Apply LOg Operations skroar inian uia a aE A AAE E AEE eat TEE 12 3 Restore Operations cicien naen n n aE E i a a aiae 12 4 Validation Operations wencissscccccsantencdasteseeedarsbietssauncbantenddast AAEE Aa EAR AKEE 12 5 Single File Backup Operations cccccccceeeeeeeeeeeeeeeaeeeeeeeeeeeeeaeaaeaeeeeeeeeeaeaaaaeneeeees 13 mysqlbackup Command Line Options cccccceccecesseeeeeeneeeeeesaeeeesesaeeeeeeaaeeeeesaaeeeeesaaeeeeees 13 1 Standard OptiOns xfrswi esses cocee sb cedeays ng seer a einieasesnaveden a E O aE 13 2 Connection OPTIONS siscecescacscssesasvedsaschessantiecessdagecesteiaeedeareoesstetveed ead sdecasebiaiiedsaneedeese 13 3 Server Repository Options cceccccceeeeeeeeeee cece ae ee cec
90. Copying tate Copying te Copying InnoDB data for locks system tablespace ibd files non InnoDB data te Completed some examples of progress indicators with different meters 300 of 1540 MB state Waiting for locks 400 of 1450 MB state Copying InnoDB data compression 30 The exact set of meters included in the progress indicator depends on the command and the options used for it 7 progress interval SECONDS Permitted Values Command Line Format progress interval SECONDS Type numeric Default 2 Min 1 Value Max 100000 Value Interval between progress reports in seconds Default value is two seconds The shortest interval is 1 second and the longest allowed interval is 100000 seconds 13 13 Encryption Options These options are for creating encrypted single file backups and for decrypting them See Chapter 8 Encryption for Backups for more details and usage examples for the encryption and decryption functions of MySQL Enterprise Backup EnCrype Encrypt the data when creating a backup image by a backup to image operation or when packing a backup directory into a single file with the backup dir to image command It cannot be used with the backup or backup and apply log command e decrypt Decrypt an encrypted backup image when performing an extract image to backup dir or copy back and apply log operation It is also used for performin
91. D FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT NCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE 167 LZ4 License POSSIBILITY OF SUCH DAMAGE E 6 LZ4 License The following software may be included in this product LZ4 Fast LZ compression algorithm Copano hie a2 Osh 20 lkor en Oleic tm BSD 2 Clause License http www opensource org licenses bsd license php Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions are met Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT L
92. EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE E 5 Google SMP Patch License The following software may be included in this product Google SMP Patch Google SMP patch Copyright c 2008 Google Inc All rights reserved Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions are Mie s Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution Neither the name of the Google Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AN
93. IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES 17 Interpretation of Sections 15 and 16 If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program and you want it to be of the greatest possible use to the public the best way to achieve this is to make it free software which everyone can redistribute and change under these terms To do so attach the following notices to the program It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty and each file should have at least the copyright line and a pointer to where the full notice is found lt one line to give the program s name and a brief idea of what it does gt Copyright C lt year gt lt name of author gt This program is free software you can redistribute it and or modify it under the terms of the GNU General Public License as published by the Free Software Foundation either version 3 of the License or at your option any later version This program is
94. ILY OB_DEVICE and OB_RESOURCE_WAIT_TIME You might set such variables with the mysqlbackup by specifying an option such as sbt environment 0B_MEDIA_FAMILY my_mf OB_DEVICE my_tape If the argument string contains any whitespace or special characters recognized by the command shell enclose the entire argument string in quotation marks To escape an equals sign or comma use the character For example sbt environment VAR1 multiple words VAR2 lt angle_brackets gt VAR3 2 2 4 e disable manifest Disable generation of manifest files for a backup operation which are backup_create xml and backup_content xm1 present in the meta subdirectory 13 10 Performance Scalability Capacity Options These options limit the resources used by the backup process in order to minimize backup overhead for busy or huge databases or specify behaviors d fhe process when encountering resource issues Performance Scalability Capacity Options number of buffers num_buffers Command Line Format number of buf fers NUMBER Permitted Values Type numeric Default 14 Min 1 Value Specifies the number of buffers each 16MB in size to use during multithreaded options Use a high number for CPU intensive processing such as backup particularly when using compression Use a low number for disk intensive processing such as restoring a backup This value should be at least as high as the number of
95. IMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THRORY OF PIABILI iY WHETHER EN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE vokeani Contact t momar ln Ort mcreaes LZ4 source repository http code google com p 1z4 DAA publie ferum 3 bttps oroups google com forum torum lzdc E 7 OpenSSL v1 0 License The following software may be included in this product OpenSSL v1 0 LICENSE ISSUES The OpenSSL toolkit stays under a dual license i e both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit See below for the actual license texts Actually both licenses are BSD style Open Source licenses In case of any license issues related to OpenSSL please contact openssl core openssl org OpenSSL License Copyright c 1998 2008 The OpenSSL Project All rights reserved Redistribution and use in source and binary forms with or without modification are permitted provided th
96. ITH READ LOCK operation to freeze such activity while backing up the frm files Restoring a backup can result in frm files being created changed or removed to match the state of the database at the time of the backup file format The format used by InnoDB for its data files named ibdatal ibdata2 and so on Each file format supports one or more row formats 176 See Also Antelope Barracuda ibdata file row format full backup A backup that includes all the tables in each MySQL database and all the databases in a MySQL instance Contrast with partial backup and incremental backup Full backups take the longest but also require the least amount of followup work and administration complexity Thus even when you primarily do partial or incremental backups you might periodically do a full backup See Also backup incremental backup partial backup table H history table The table mysql backup_history that holds details of completed backup operations While a backup job is running the details especially the changing status value are recorded in the progress table See Also backup progress table hot backup A backup taken while the MySQL instance and is running and applications are reading and writing to it Contrast with warm backup and cold backup A hot backup involves more than simply copying data files it must include any data that was inserted or updated while the backup was in process it must exclu
97. InnoDB tables are backed up incrementally By default all non InnoDB and frm files are included in incremental backup and in their fullness To exclude non InnoDB data in an incremental backup use the only innodb option incremental base modeiargument Command Line Format incremental base mode argument Permitted Values Type string With this option the mysqlbackup retrieves the information needed to perform incremental backups from the metadata inside the backup directory rather than from the start 1sn option It saves you from having to specify an ever changing unpredictable LSN value when doing a succession of incremental backups Instead you specify a way to locate the previous backup directory through the combination of mode and argument in the option syntax The alternatives are dir directory_path You specify the prefix dir followed by a directory path The path argument points to the directory where the data from the previous backup is stored With the first incremental backup you specify the directory holding the full backup with the second incremental backup you specify the directory holding the first incremental backup and so on history last_backup You specify the prefix history followed by last_backup the only valid argument for this mode This makes mysqlbackup query the end_isn value from the last successful non TTS backup as recorded in the backup_history table of the server inst
98. L statements from mysqldump output To minimize any impact on server performance on Linux and Unix systems MySQL Enterprise Backup writes the backup data without storing it in the operating system s disk cache by using the posix_fadvise system call This technique minimizes any slowdown following the backup operation by preventing frequently accessed data from being flushed from the disk cache by the large one time read operation for the backup data For more on techniques and tradeoffs involving backup and restore performance see Chapter 7 Performance Considerations for MySQL Enterprise Backup 1 4 Files that Are Backed Up DBA and development work typically involves logical structures such as tables rows columns the data dictionary and so on For backups you must understand the physical details of how these structures are represented by files Table 1 1 Files in a MySQL Enterprise Backup Output Directory File Name Pattern or Extension Relation to Original Data Files Notes ibdata The InnoDB system tablespace containing multiple InnoDB tables and associated indexes Because the original files might change while the backup is in progress the apply log step applies the same changes to the corresponding backup files Files that Are Backed Up File Name Pattern or Extension Relation to Original Data Files Notes abe a Dz InnoDB file per table tablespaces each
99. ML activity and size of the redo log files e Since the redo log files act as a circular buffer with records of older changes being overwritten as new DML operations take place you must take new incremental backups on a predictable schedule dictated by the size of the log files and the amount of redo data generated for your workload Otherwise the redo log might not reach back far enough to record all the changes since the previous incremental backup in which case mysqlbackup will quickly determine that it cannot proceed and will return an error Your backup script should be able to catch that error and then perform an incremental backup with the incremental option instead For example To calculate the size of the redo log issue the command SHOW VARIABLES LIKE innodb_log_file and based on the output multiply the innodb_log_file_size setting 36 Making a Differential or Incremental Backup by the value of innodb_log_files_in_group To compute the redo log size at the physical level look into the dat adir directory of the MySQL instance and sum up the sizes of the files matching the pattern ib_logfile e The InnoDB LSN value corresponds to the number of bytes written to the redo log To check the LSN at some point in time issue the command SHOW ENGINE INNODB STATUS and look under the LOG heading While planning your backup strategy record the LSN values periodically and subtract the earlier value from the cu
100. MySQL Enterprise Backup User s Guide Version 3 12 1 Abstract This is the User s Guide for the MySQL Enterprise Backup product This manual describes the procedures to back up and restore MySQL databases It covers techniques for minimizing time and storage overhead during backups and to keep the database available during backup operations It illustrates the features and syntax of the mysqlbackup command for example how to back up selected databases or tables how to back up only the changes since a previous backup and how to transfer the backup data efficiently to a different server For notes detailing the changes in each release see the MySQL Enterprise Backup 3 12 Release Notes For legal information see the Legal Notices For help with using MySQL please visit either the MySQL Forums or MySQL Mailing Lists where you can discuss your issues with other MySQL users For additional documentation on MySQL products including translations of the documentation into other languages and downloadable versions in variety of formats including HTML and PDF formats see the MySQL Documentation Library Document generated on 2015 12 12 revision 6215 Table of Contents Preface and Legal Notices ccceceeeeeeeceeeee erence eee cece eres EEEE PAEA EREET PREE ee EE RENEA EENEN NE xi Getting Started with MySQL Enterprise Backup cececeee cence eeeeeeeeeeeeaaaaeeeeeeeeeeeeaeaaeeneeeeeeeeeanaaea 1 1 Intr
101. NOTICE Copyright c 1996 2014 Daniel Stenberg lt daniel haxx se gt All rights reserved Permission to use copy modify and distribute this software for any purpose with or without fee is hereby granted provided that the above copyright notice and this permission notice appear in all copies THE SOFTWARE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM DAMAGES OR OTHER LIABILITY WHETHER IN AN ACTION OF CONTRACT TORT OR OTHERWISE ARISING FROM OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE Except as contained in this notice the name of a copyright holder shall not be used in advertising or otherwise to promote the sale use or other dealings in this Software without prior written authorization of the copyright holder E 2 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 GNU GENERAL PUBLIC LICENSE Version 3 29 June 2007 Copyright C 2007 Free Software Foundation Inc lt http fsf org gt Everyone is permitted to copy and distribute verbatim copies of 153 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31
102. OJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON UNE THEORY OND EIABIDI IES WHETHER IN CONTRACT SIMIC DIABIDITE OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE This product includes cryptographic software written by Eric Young eay cryptsoft com This product includes software written by Tim Hudson tjh cryptsoft com Original SSLeay License L Copyright Cy 1995 1998 Bric Young eGayvecryptsoft com All rights reserved This package is an SSL implementation written by Eric Young eay cryptsoft com The implementation was written so as to conform with Netscapes SSL This library is free for commercial and non commercial use as long as the following conditions are aheared to The following conditions apply to all code found in this distribution be it the RC4 RSA dines DES etc code not just the SSL code The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson tjh cryptsoft com Copyright remains Eric Young s and as such any Copyright notices in the code are not to be removed If this package is used in a product
103. P The regular expression syntax used is the extended form specified in the POSIX 1003 2 standard For example include tables mydb t 12 matches the tables t1 and t2 in the database mydb On Unix like systems quote the regular expression appropriately to prevent interpretation of shell meta characters mysqlbackup throws an error when the option is used without a regular expression being supplied with it While mysqlbackup understands the MySQL convention of quoting the database or the table name or both by backticks see Schema Object Names there is no need to include the backticks in the regular expression for include tables While the option can be used for different kinds of backups selective restore is only supported for backups created using transportable tablespace TTS that is backups created with the use tts option The option can also be used with the backup dir to image and image to backup dir commands to select tables when creating or unpacking a backup image The option cannot be used together with the legacy include databases databases list file of only innodb with frm option 115 Partial Backup and Restore Options When used together with the xclude tables option include tables is applied first meaning mysqlbackup first selects all tables specified by include tables and then excludes from the set those tables specified by xclude tables xclude tables REGEXP Com
104. PTIONS PROGRESS REPORT OPTIONS backup backup and apply log mysqlbackup STD OPTIONS 87 Apply Log Operations CONNECTION OPTIONS SERVER REPOSTIORY OPTIONS BACKUP REPOSITORY OPTIONS METADATA OPTIONS COMPRESSION OPTIONS SPECITAL BACKUP TYPES OPTIONS INCREMENTAL BACKUP OPTIONS PARTIAL BACKUP RESTORE OPTIONS SINGLE FILE BACKUP OPTIONS PERFORMANCE SCALABILITY CAPACITY OPTIONS MESSAGE LOGGING OPTIONS PROGRESS REPORT OPTIONS ENCRYPTION OPTIONS CLOUD STORAGE OPTIONS backup to image backup Backs up data to a directory This only performs the initial phase of a complete backup process The second phase is performed later by running mysqlbackup again with the appl y log command which makes the backup consistent backup and apply log A combination of backup and apply log It cannot be used for a compressed or an incremental backup backup to image Produces a single file backup rather than a directory structure holding the backup files Requires the backup image command to specify the destination file Can be used to stream the backup to a storage device or another system without ever storing the data on the database server You can specify backup image representing standard output allowing the output to be piped to another command To avoid mixing normal informational messages with backup output the help messa
105. S error codes You might need to consult your operating system documentation for the meaning and solution of these error codes The output from mysqlbackup is sent to stderr rather than stdout By default the same output is also saved to a log file in the backup_dir for use in error diagnosis See Section 13 11 Message Logging Options for details on how to configure this logging feature Incremental backups require care to specify a sequence of time periods You must record the final LSN value at the end of each backup and specify that value in the next incremental backup You must also make sure that the full backup you restore is prepared correctly first so that it contains all the changes from the sequence of incremental backups e AS mysqlbackup proceeds it writes progress information into the mysql backup_progress table When the command finishes the backup operation it records status information in the mysql backup_history table You can query those tables to monitor ongoing backup jobs see how much time has been used for various stages and check if any errors have occurred 10 1 Monitoring Backups with MySQL Enterprise Monitor With the combination of the MySQL Enterprise Backup and MySQL Enterprise Monitor products you can monitor the progress and history of backup jobs without writing your own queries or scripts e The MySQL Enterprise Monitor graphs Backup Run Time and Backup Locked Time chart how long the phases of backup
106. Server version x y z See Section C 2 Compatibility with MySQL Versions for details of compatibility between different releases of MySQL Enterprise Backup and MySQL Server A 2 What is the big ibdata file that is in all the backups You might find your backup data taking more space than expected because of a large file with a name such as ibdatal This file represents the InnoDB system tablespace which grows but never shrinks and is included in every full and incremental backup To reduce the space taken up by this file in your backup data e After doing a full backup do a succession of incremental backups which take up less space The ibdatal file in the incremental backups is typically much smaller containing only the portions of the system tablespace that changed since the full backup e Set the configuration option innodb_file_per_table 1 before creating your biggest or most active InnoDB tables Those tables are split off from the system tablespaces into separate ibd files which are more flexible in terms of freeing disk space when dropped or truncated and can be individually included or excluded from backups If your system tablespace is very large because you created a high volume of InnoDB data before turning on the innodb_file_per_table setting you might use mysqldump to dump the entire instance then turn on innodb_file_per_table before re creating it so that all the table data is kept outside the system tablespace
107. This section describes the procedures to handle those scenarios After a serious database issue you might need to perform a recovery under severe time pressure It is critical to confirm in advance e How long the recovery will take including any steps to transfer unpack and otherwise process the data e That you have practiced and documented all steps of the recovery process so that you can do it correctly in one try If a hardware issue requires restoring the data to a different server verify all privileges storage capacity and so on on that server ahead of time e That you have periodically verified the accuracy and completeness of the backup data so that the system will be up and running soon after being recovered 5 1 Preparing the Backup to be Restored Immediately after the backup job completes the backup files might not be in a consistent state because data could be inserted updated or deleted while the backup is running These initial backup files are known as the raw backup You must update the backup files so that they reflect the state of the database corresponding to a specific InnoDB log sequence number the same kind of operation takes place during a crash recovery When this step is complete these final files are known as the prepared backup During the backup mysqlbackup copies the accumulated InnoDB log to a file called ibbackup_logfile This log file is used to roll forward the backed up data files so tha
108. a an diain aieiaa 134 13 14 Cloud Storage Options 20 0 cece cece eect eeee eee e sere ee ead te eee eee ee ae aaa deeeeeeeeeeeaaaaeeeeeeeeeeeaea 135 13 15 Options for Special Backup Types 0 cccceeeeeeeeeeeeeeeeeeeeceaaeaeeeeeeeeeeeeaaaaeeeeeeeeeeeeaeaaaaees 137 14 Configuration Files and Parameters ccccccceccceeeeeeeeeee tees eae eeeeeeeeeeeeaeaaeeceeeeeeeeeaeaaaaeeneeeeseeeeaea 139 83 84 Chapter 11 mysqlbackup The mysqlbackup client is an easy to use tool for all backup and restore operations During backup operations mysqlbackup backs up All InnoDB tables and indexes including e The InnoDB system tablespace which by default contains all the InnoDB tables e Any separate data files produced with the InnoDB file per table setting Each one contains one table and its associated indexes Each data file can use either the original Antelope or the new Barracuda file format All MyISAM tables and indexes Tables managed by other storage engines e Other files underneath the MySQL data directory such as the frm files that record the structure of each table e Any other files in the database subdirectories under the server s data directory In addition to creating backups mysqlbackup can pack and unpack backup data apply to the backup data any changes to InnoDB tables that occurred during the backup operation and restore data index and log files back to their original locations or to
109. a for InnoDB related objects the data dictionary Turning on the innodb _file_per_table option causes each newly created table to be stored in its own tablespace reducing the size of and dependencies on the system tablespace Keeping all table data in the system tablespace has implications for the MySQL Enterprise Backup product backing up one large file rather than several smaller files and prevents you from using certain InnoDB features that require the newer Barracuda file format on the See Also Barracuda data dictionary file format ibdata file tablespace T TRG file A file containing trigger parameters Files with this extension are always included in backups produced by the mysqlbackup command of the MySQL Enterprise Backup product table Although a table is a distinct addressable object in the context of SQL for backup purposes we are often concerned with whether the table is part of the system tablespace or was created under the file per table setting and so resides in its own tablespace See Also backup system tablespace tablespace tablespace For InnoDB tables the file that holds the data and indexes for a table Can be either the system tablespace containing multiple tables or a table created with the file per table setting that resides in its own tablespace file See Also InnoDB system tablespace transportable tablespace A feature that allows a tablespace to be moved from one instance to another Traditio
110. a full backup The incremental backup data must be merged with the contents of the previous backup before it can be restored See Section 4 3 2 Making a Differential or Incremental Backup for usage details Related mysqlbackup options are incremental incremental with redo log only incremental backup dir incremental base and start lsh See Also full backup InnoDB The type of MySQL table that works best with MySQL Enterprise Backup These tables can be backed up using the hot backup technique that avoids interruptions in database processing For this reason and because of the higher reliability and concurrency possible with InnoDB tables most deployments should use InnoDB for the bulk of their data and their most important data In MySQL 5 5 and higher the CREATE TABLE statement creates InnoDB tables by default See Also hot backup table instance The full contents of a MySQL server possibly including multiple databases A backup operation can back up an entire instance or a partial backup can include selected databases and tables See Also database partial backup L locking See Also suspend warm backup log Several types of log files are used within the MySQL Enterprise Backup product The most common is the InnoDB redo log that is consulted during incremental backups See Also incremental backup redo log log sequence number See LSN logical backup A backup that reproduces table structure and data witho
111. ackup of InnoDB Tables ccceceeeeeeeeeeeeeeeeeeeeeeeeeaaaaeenees 43 4 2 Making a Compressed Partial Backup cccceeeeeeeeee ce ee ea eeeeeeeeeeeeaeaaeaeeeeeeeeeseaaaaeeeeseeeeeeaeaaeaees 44 4 3 Single File Backup to Absolute Path 0 ccccccececeeeceeeeeeeeeee ee ae aa ee eeeeeeeeeeeeaaaaeeeeeeeeeeeaaaaeneeeeeeeees 45 4 4 Single File Backup to Relative Path 0 cccccceeccseeeeeeeeee tees cee eeeeeeeeee ee saaaeeeeeeeeeeeeaeaaeaneeeeeeeeeaeaaea 45 4 5 Single File Backup to Standard Output 0 cccccceceeeceeeeeeeeeee ee ee aa ee eeeeeeee sees aaaaeeeeeeeeeeeaaaaeeeeeeeeeees 45 4 6 Convert Existing Backup Directory to Single Image ccceceeeeeee cee eeeeeeeeeeeeaeaaeaeeeeeeeeeeeeaaaaeenees 46 4 7 Extract Existing Image to Backup Directory cececcceeeee een eeee tena ener tena eeeeeaaeeeeeeaaeeeeeeaaeeeeeeaaaeees 46 4 8 List Single File Backup Content 0 cccceceeeeeeeeeeeeee cece ae eae eect eeee ee aa aaaaeeeeeeeeeeaaaaaaeeeeeeeeeaeaaaaees 46 4 9 Validate a Single File Backup ccccceceeeeeeeeeeeee eect ae ea ee ee ee ee ease aa aaeeeeeeeeeeeeaaaaaeeeeeeeeeeeaeaaeeeeseeeees 46 4 10 Extract Single File Backup into Current Directory cceccceeeee ce eeeeeeeeeeeeee ee aaeaeeeeeeeeeeeeaaaaneeeeees 46 4 11 Extract Single File Backup into a Backup Directory 0cccceeeeeeeeeeeeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeeees 46 4 12 Selective Extract of Single File
112. adecavs keneen EREA EEE RA AON ETA AES FAAO EAEE TEN O ETA NE REONE E 2 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3els 371 March 2009 a a a a a aaa a A aa A E 3 GNU Standard C Library libstdc License 0 cece cece cece cece cea eeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeeees E 4 Google Controlling Master Thread I O Rate Patch License 0 cccceeeeeeeeeeee eres ae eeeeeeeeeeeeaeaaee E 5 Google SMP Patch License 0 ccccceceee cence eeeeeeee ee ae ea eeteeeee sees ae aaeeeeeeeeeeeaeaaeaaeeeeeeeeeeeaaaaeeeees E 65EZ4 LICENSG tiie esi eae eit hea E eae a E7 OpenSsSk V1 0 LicOnSe ss cc5 cease becavid aE aa cd aaa aa ea bed ia EA E A A Gabel E 8 Percona Multiple I O Threads Patch License ccceeeeeeeeeeeeeee tees ee aa ee eeeeeeeeeeaeaaeeteeeeeeeeeaeaae 2 9 REZ LCOS oote deeds Gases cpus nstetiwhanendevended oe sidedstushe cegwaaae cas ahead iow diac datusteateweaae dn hte alate E 10 RegEX Spencer Library License ccecccceeceeeeeee eee e ee ae eee test sees seca aaaateeeeeeeeeaeaaaaaaeeeeeeeeaeaae E 11 RFC 3174 US Secure Hash Algorithm 1 SHA1 License cceceeeeeeeeeeeeeeeeeeeeeeeeeaneaeeeees Est Zi LICENSE E E E PE A S E EET E AE T E EA ETE E 1 CURL libcurl License The following software may be included in this product CUR ie Gliese Use of any of this software is governed by the terms of the license below COPYRIGHT AND PERMISSION
113. an interface provided by the Runtime Library but is not otherwise based on the Runtime Library GCC means a version of the GNU Compiler Collection with or without modifications governed by version 3 or a specified later version of the GNU General Public License GPL with the option of using any subsequent versions published by the FSF GPL compatible Software is software whose conditions of propagation modification and use would permit combination with GCC in accord with the license of GCC Target Code refers to output from any compiler for a real or virtual target processor architecture in executable form or suitable for input to an assembler loader linker and or execution phase Notwithstanding that Target Code does not include data in any 164 GNU Standard C Library libstdc License format that is used as a compiler intermediate representation or used for producing a compiler intermediate representation The Compilation Process transforms code entirely represented in non intermediate languages designed for human written code and or in Java Virtual Machine byte code into Target Code Thus for example use of source code generators and preprocessors need not be considered part of the Compilation Process since the Compilation Process can be understood as starting with the output of the generators or preprocessors A Compilation Process is Eligible if it is done using GCC alone or with other GPL co
114. ance that is being backed up it and keeps searching the backup history until it finds the last non TTS backup Note R If the last full or partial backup made was a TTS backup mysqlbackup skips and then returns its end_isn value with the no connection option which always turns off the recording of backup history and might cause errors for a subsequent incremental backup Warning e Do not use the history mode if the previous backup was a full backup taken using this mode of the incremental base option start lsn LSN Command Line Format start lsn LSN Permitted Values Type numeric In an incremental backup specifies the highest LSN value included in a previous backup You can get this value from the output of the previous backup operation or from the backup_history table s end_isn column for the previous backup operation Always used in combination with the incremental option not needed when you use the incremental base option not recommended when you use the incremental with redo log only mechanism for incremental backups 114 Partial Backup and Restore Options incremental backup dir PATH Specifies the location for data of an incremental backup When creating or restoring an incremental backup the option serves the same function as backup dir does for backups and restores in general and the option can in fact be used interchangeably wit
115. and minimizing the duration of the suspend stage where you run customized backup logic while the MySQL server is locked See Also cold backup hot backup InnoDB locking replication slave suspend E exclude In a partial backup to select a set of tables databases or a combination of both to be omitted from the backup Contrast with include See Also partial backup extract The operation that retrieves some content from an image file produced by a single file backup It can apply to a single file unpacked to an arbitrary location or to the entire backup reproducing the original directory structure of the backup data These two kinds of extraction are performed by the mysqlbackup options extract and image to backup dir respectively See Also image single file backup F frm file A file containing the metadata such as the table definition of a MySQL table For backups you must always keep the full set of frm files along with the backup data to be able to restore tables that are altered or dropped after the backup Although each InnoDB table has a frm file InnoDB maintains its own table metadata in the system tablespace the frm files are not needed for InnoDB to operate on InnoDB tables These files are backed up by the MySQL Enterprise Backup product These files must not be modified by an ALTER TABLE operation while the backup is taking place which is why backups that include non InnoDB tables perform aFLUSH TABLES W
116. and smaller than a full backup like these ones Making a Partial Backup with the Legacy Options Important A Information in this subsection is only for using the legacy options of include databases databases list file and only innodb with frm which will be deprecated in the upcoming issues For creating partial backups it is strongly recommended that the new options of include tables and xclude tables be used instead Note that you cannot combine the legacy and the new partial backup options in a single command MySQL Enterprise Backup can make different kinds of partial backup using the legacy partial backup options e Including certain InnoDB tables but not others This operation involves the include only innodb and only innodb with frm options e Including certain non InnoDB tables from selected databases but not others This operation involves the databases and databases list file options For syntax details on all these options see Legacy Partial Backup Options Note E Typically a partial backup is more difficult to restore than a full backup because the backup data might not include the necessary interrelated pieces to constitute 42 Making a Partial Backup a complete MySQL instance In particular InnoDB tables have internal IDs and other data values that can only be restored to the same instance not a different MySQL server Always fully test the recovery proce
117. and transmit the Software and to prepare derivative works of the Software third parties to whom the Software is furnished to do so Version 1 0 Lien ZOS to any person or and accompanying to use and to permit all subject The copyright notices in the Software and this entire statement including the above license grant disclaimer must be included in all Crit tart copies or derivative works are solel and all derivative works of the Software this restriction and the following copies of the Software in whole unless such ly in the form of machine executable object code generated by a source language processor THE SOFTWARE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE TITLE AND NON INFRINGEMENT IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY WHETHER IN CONTRACT TORT OR OTHERWISE ARISING FROM OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE Copyright C 2004 Ami Tavory and Vladimir Dreizin IBM HRL Permission to use copy modify sell and distribute this software is hereby granted without fee provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation None of the above
118. apacity Options arise Also if any binary log files are missing on the server you are backing up you should use this option to avoid mysqlbackup throwing an error for the missing files The binary log files and the binary log index file when included in a backup are always copied into the restored server s data directory during a restore operation if that is not the behavior you desire use this option to skip the restoring of the binary log skip relaylog When working with a slave server skip including the relay log files in the backup during a backup operation or skip copying the relay log files onto a server during a restore operation Relay log files together with the relay log index file and the master info and the slave info files are included by default for all kinds of online backups full incremental compressed partial single file etc of a slave server See Section 1 4 Files that Are Backed Up for details Use this option to skip backing up relay logs if resource performance or other issues arise Note E If a user runs a FLUSH LOGS statement while backup is in progress for a slave the backup process will fail Use the skip relaylog option if you expect a FLUSH LOGS statement will be run during the backup and it is not necessary to include the relay logs in the backup The relay log files and the files backed up together with them when included in a backup are always copied into the restored server
119. at MySQL uses to store indexes for a MyISAM table See Also MYD file manifest The record of the environment for example command line arguments and data files involved in a backup stored in the files meta backup_create xml and meta backup_content xml respectively This data can be used by management tools during diagnosis and troubleshooting procedures master In a replication configuration a database server that sends updates to a set of slave servers It typically dedicates most of its resources to write operations leaving user queries to the slaves With MySQL Enterprise Backup typically you perform backups on the slave servers rather than the master to minimize any slowdown of the overall system See Also replication slave media management software A class of software programs for managing backup media such as libraries of tape backups One example is Oracle Secure Backup Abbreviated MMS See Also Oracle Secure Backup my cnf The typical name for the MySQL configuration file on Linux Unix and OS X systems See Also configuration file my ini my ini The typical name for the MySQL configuration file on Windows systems See Also configuration file my cnf MyISAM A MySQL storage engine formerly the default for new tables In MySQL 5 5 and higher InnoDB becomes the default storage engine MySQL Enterprise Backup can back up both types of tables and tables from other 179 storage engines also The backup proces
120. at the following conditions are met 1 Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer 2 Redistributions in binary form must reproduce the above copyright notice 168 OpenSSL v1 0 License this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution 3 All advertising materials mentioning features or use of this software must display the following acknowledgment This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit Linkl 4 The names OpenSSL Toolkit and OpenSSL Project must not be used to endorse or promote products derived from this software without prior written permission For written permission please contact openssl core openssl org 5 Products derived from this software may not be called OpenSSL nor may OpenSSL appear in their names without prior written permission of the OpenSSL Project 6 Redistributions of any form whatsoever must retain the following acknowledgment This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit Link2 THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE OpenSSL PR
121. ata The files generated during the backup process include e backup my cnf Records the crucial configuration parameters that apply to the backup These parameter values are used during a restore operation so that the original values are used regardless of changes to your my cnf file in the meantime e meta backup_create xml Lists the command line arguments and environment in which the backup was created e meta backup_content xm1 Essential metadata for the files and database definitions of the backup data e server my cnf Contains values of the backed up server s global variables that are set to non default values e server all cnf Contains values of all the global variables of the backed up server For details about all the files in the backup directory see Table 1 1 Files in a MySQL Enterprise Backup Output Directory Single File Backups Depending on your workflow you might want to perform a single file backup rather than a directory backup which produces a separate file for every file on the original server instance A single file backup is easier to transfer to a different system to compress and to uncompress it also helps to prevent the situation in which individual files that form parts of a backup are deleted by mistake It is just as fast as a multi file backup to do a full restore restoring individual files can be slower than in a multi file backup For instructions see Section 4 3 5 Making a Single Fil
122. ation 87 options 97 overview 6 required privileges 29 using 27 mysqlbinlog command 58 mysqldump 51 180 N no history logging option 111 no locking option 126 non TTS backup 180 number of buffers option 124 O offline 180 on disk full option 127 online 180 only innodb option 117 rename option 118 only innodb option 120 only known file types option 116 opt file 7 180 optimistic backup 49 129 130 180 optimistic busy tables 130 optimistic time 129 options mysqlbackup 97 connection 104 for cloud storage 135 for compression 112 for controlling backup overhead performance and scalability 123 for controlling message logging 130 for controlling progress reporting 131 for encryption 134 for generating metadata 111 for incremental backups 113 for partial backups 115 for single file backups 121 for special types of backups 137 in configuration files 139 layout of backup files 107 layout of database files 105 modes of operation 87 options in common with mysal 102 standard options 102 Oracle Secure Backup 181 OSB 181 P page reread count option 127 page reread time option 126 par file 7 181 parallel backup 65 68 181 parallel backups 6 partial backup 40 115 181 partial restore 181 performance of backups 65 of restores 68 performance of backup operations 6 physical backup 6 181 point in time 181 point in time recovery 58 posi
123. ations the mysqlbackup command connects to the MySQL server using the credentials supplied with the user and password options The specified user needs certain privileges You can either create a new user with a minimal set of privileges or use an administrative account such as root The minimum privileges for the MySQL user with which mysqibackup connects to the server are RELOAD on all databases and tables CREATE INSERT DROP and UPDATE on the tables mysql backup_progress and mysql backup_history and also SELECT on mysql backup_history SUPER to enable and disable logging and to optimize locking in order to minimize disruption to database processing REPLICATION CLIENT to retrieve the binary log position which is stored with the backup To set these privileges for a MySQL user mysqlbackup in this example connecting from localhost issue statements like the following from the mysqi client program GRANT RELOAD ON TO mysqlbackup localhost GRANT CREATE INSERT DROP UPDATE ON mysql backup_progress TO mysqlbackup localhost GRANT CREATE INSERT SELECT DROP UPDATE ON mysql backup_history TO mysqlbackup localhost GRANT REPLICATION CLIENT ON TO mysqlbackup localhost GRANT SUPER ON TO mysqlbackup localhost The following additional privileges are required for using transportable tablespaces TTS to back up and restore InnoDB tables LOCK TABLES and SELECT for
124. b_log_files_in_group db_log_file_size 50331648 16384 db_checksum_algorithm db_undo_directory home admin backup tmp datadir db_undo_tablespaces 0 128 db_data_home_dir home admin backup tmp datadir db_data_file_path ibdatal 12M autoextend home admin backup tmp datadir 2 innodb home admin backups my mbi INFO Unique generated backup id for this is 14177156956623554 6 process sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup var lib m sqlbackup sqlbackup sqlbackup sqlbackup sqlbackup datadir innodb_data_home_dir inno inno inno inno innodb_page_size inno inno inno innodb_undo_logs datadir inno inno inno inno inno innodb_page_size inno inno inno innodb_undo_logs ckup Image Path ysqlbackup ysqlbackup 204 12 read threads 204 12 204 12 ysqlbackup INFO ysqlbackup INFO ZAOKAS WA Sisal Ey 204 12 54 58 my 204 12 54 58 my 204 12 54 58 my 204 12 54 58 my 204 12 54 59 my 204 12 54 59 my 204 12 54 59 my 204 12 55 00 my 204 12 55 00 my 204 12 55 00 my 204 12 55 00 my ZO WAS 9100 saan ZO WA S S 90 ign ZO WAeis5s SO ign ZO WAS S02 ign ZO WAS SZ sayy ZO WAS SSOZ ign 204 WAS SZ inn ubdirectories of QOL WSIS S902 inn ZO WAS SZ ign 204 I2eI5 5902 Ey ZL WAS SOZ
125. backing up tables CREATE and ALTER for restoring tables To set these privileges issue a statement like the following from the mysql client program GRANT LOCK TABLES SELECT CREATE ALTER ON TO mysqlbackup localhost 29 Designate a Location for Backup Data 4 1 3 Designate a Location for Backup Data All backup related operations either create new files or reference existing files underneath a specified directory that holds backup data referred to as the backup directory in this manual Choose in advance for this directory a location on a file system with sufficient storage which could even be remotely mounted from a different server You specify the path to this directory with the backup dir option for many mysqlbackup commands Once you establish a regular backup schedule with automated jobs it is preferable to keep each backup within a timestamped subdirectory underneath the main backup directory To make mysgqlbackup create these subdirectories automatically specify the with timestamp option each time you run mysqlbackup For one time backup operations for example when cloning a database to set up a replication slave you might specify a new directory each time or for a single file backup specify the force 103 option to overwrite the old backup file 4 2 The Typical Backup Verify Restore Cycle To illustrate the basic steps in creating and making use of a backup the following example
126. backup dir during the backup Supply then that number to mysqlbackup using the start lsn option The incremental backup then includes all changes that came after the specified LSN Since then the location of the previous backup is not very significant then you can use with timestamp to create named subdirectories automatically mysqlbackup defaults file home pekka my cnf incremental start 1sn 2654255716 with timestamp incremental backup dir incr backup backup many lines of output mysqlbackup Backup created in directory incr backup 2010 12 08_17 14 48 38 Making a Compressed Backup mysqlbackup start_lsn 2654255717 mysqlbackup incremental_base_lsn 2666733462 mysqlbackup end_lsn 2666736714 101208 17 14 58 mysqlbackup mysqlbackup completed OK To create an incremental backup image instead use the following command specifying with incremental backup dir a temporary directory for storing the metadata for the backup and some temporary files an mysqlbackup defaults file home pekka my cnf incremental start lsn 2654255716 with timestamp incremental backup dir incr tmp backup image incr backup incremental_image bi backup to image In the following example though because backup image does not provide a full path to the image file to be created the incremental backup image is created under the folder specified by incremental
127. both together must be used in the restore command for the rename option to work unless there is only one table in the backup Also the include tables or xclude tables option or both together should specify one and only one table for restore when rename is used or the restore will fail e old table nameand new_table_name can be fully qualified containing the database names in the format of db_name tb_name or not Regular expressions are not accepted for old_table_name and new_table_name e The restore fails if ol d_table_name does not match with the table specified using the include tables or xclude tables option or both together or if new_table_name already exists in the target database e The requirements listed in Section 5 2 4 Restoring Backups Created with the use tts Option apply See Section 5 2 4 Restoring Backups Created with the use tts Option for more information on selective restores and for an example of table renaming Legacy Partial Backup Options Important A Information in this subsection is only for using the legacy options of include databases databases list file and only innodb with frm which will be deprecated in the upcoming issues For creating partial backups it is strongly recommended that the new options of include tables and xclude tables be used instead Note that you cannot combine the legacy and the new partial backup options in a single command
128. c Default 100 Interval in milliseconds that mysqlbackup waits before re reading a page that fails a checksum test A busy server could be writing a page at the same moment that mysqlbackup is reading it Can be a floating point number such as 0 05 meaning 50 microseconds Best possible resolution is 1 microsecond but it could be worse on some platforms Default is 100 milliseconds 0 1 seconds page reread count retry_limit 126 Performance Scalability Capacity Options Command Line Format page reread count number Permitted Values Type numeric Default 500 Maximum number of re read attempts when a page fails a checksum test A busy server could be writing a page at the same moment that mysqlibackup is reading it If the same page fails this many checksum tests consecutively with a pause based on the page reread time option between each attempt the backup fails Default is 500 on disk full abort abort_and_remove warn Command Line Format on disk full option Permitted Values Type enumeration Default abort Valid abort Values aa abort_and_remove Specifies the behavior when a backup process encounters a disk full condition This option is only for backup operations backup backup and apply log and backup to image abort Abort backup without removing the backup directory The disk remains full abort_and_remo
129. ce and this permission notice appear in supporting documentation Hewlett Packard Company makes no representations about the suitability of this software for any purpose It is provided as is without express or implied warranty Copy iig mea ce 1996 19 97 Silicon Graphics Computer Systems Inc Permission to use copy modify distribute and sell this software and its documentation for any purpose is hereby granted without fee provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear 165 Google Controlling Master Thread I O Rate Patch License in supporting documentation Silicon Graphics makes no representations about the suitability of this software for any purpose It is provided as is without express or implied warranty shared_count hpp Copyright c 2001 2002 2003 Peter Dimov and Multi Media Ltd shared_ptr hpp Copyright C 1998 1999 Greg Colvin and Beman Dawes Copyright C 2001 2002 2003 Peter Dimov weak_ptr hpp Copyright C 2001 2002 2003 Peter Dimov enable_shared_from_this hpp Copyright C 2002 Peter Dimov Distributed under the Boost Software License Boost Software License Version 1 0 August Permission is hereby granted free of charge organization obtaining a copy of the software documentation covered by this license the reproduce display distribute execute to the following Softtware
130. cket options that are necessary to connect to the MySQL server You can specify the following connection specific options in the mysqlbackup or client sections of a MySQL configuration file or through mysqlibackup command line options mysqlbackup reads your default configuration files and then the my cnf file specified on the command line Note R mysqlbackup reads only user password port and socket options from the client group and ignores any other connection options e If you do not provide a value for the password the command prompts for one from the keyboard e The host option is allowed in the configuration file for compatibility but currently it has no effect mysqlbackup always connects to the local server s IP address Options Common to mysqld login path name port port num protocol tcp socket pipe memory pipe alias for protocol pipe user name short option u host hostname socket name shared memory base name value Windows only character sets dir PATH default character set VALUE secure auth Don t connect to pre 4 1 1 server password value short option pi connect_timeout ssl Enable SSL for connection ssl key file_name ssl cert file name ssl ca file_name ssl capath directory_name ssl cipher cipher 11st ssl verify servor cert Connection Options Specific to mysql Backup
131. ckup COMpress Create backup in compressed format For a regular backup among all the storage engines supported by MySQL only data files of the InnoDB format are compressed and they bear the ibz extension after the compression Similarly for a single image backup only data files of the InnoDB format inside the backup image are compressed The binary log and relay log files are compressed and saved with the bz extension when being included in a compressed backup Default compression is disabled x compress method ALGORITHM Command Line Format compress method ALGORITHM Permitted Values Type enumeration Default 124 Valid zlib Values 124 lzma Specifies the compression algorithm The supported arguments for the option and the algorithms they represent are e 124 LZ4 r109 Out of the three algorithms that are supported this is the most efficient one typically taking the shortest backup and restore times with the lowest CPU cost See 1z4 Extremely Fast Compression algorithm for more details including a comparison with other compression algorithms e 1zma LZMA 9 20 Out of the three supported algorithms this typically provides the highest compression ratio but it is also far more expensive in terms of CPU cost than the other two options Thus we do not recommend this for active systems but only for off hour or inactive databases or where I O rates are extremely low e
132. ckup only contains the changes made since that last incremental backup Each subsequent incremental backup is thus usually smaller in size than a differential backup and is faster to make that allows you to make very frequent incremental backups and then enables you to restore the database to a more precise point in time when necessary However restoring data with incremental backups might take longer and more work in general to restore data up to for example time t you start with restoring the full backup and then restore the incremental backups one by one until you are finished with the incremental backup taken for time t MySQL Enterprise Backup supports both incremental and differential backups You should decide on which backup strategy to adopt by looking at such factors like how much storage space you have how quickly you have to be able to restore data and so on MySQL Enterprise Backup treats differential backup as a special case of incremental backup that has a full backup as its base To create a differential backup simply follow the instructions below for performing incremental backups and make sure you specify a full backup as the base of your incremental backup using the methods we describe below you should also ignore any instructions that only apply to the handling of multiple incremental backups See Section 13 7 Incremental Backup Options for descriptions of the mysqlbackup options used for incremental backups
133. clude tables is applied first meaning mysqlibackup first select all tables specified by include tables and then exclude from the set those tables specified by xclude tables for backup only known file types For back up only By default all files in the database subdirectories under the data directory of the server are included in the backup see Section 1 4 Files that Are Backed Up for details If the only known file types option is specified mysqlbackup only backs up those types of files that are data files for MySQL or its built in storage engines which have the following extensions e ARM Archive storage engine metadata ARZ Archive storage engine data e CSM CSV storage engine data e CSV CSV storage engine data e frm table definitions e ibd InnoDB tablespace created using the file per table mode e MRG Merge storage engine references to other tables e MYD MyISAM data 116 Partial Backup and Restore Options e MYI MyISAM indexes opt database configuration information e par partition definitions TRG trigger parameters TRN trigger namespace information only innodb For back up only Back up only InnoDB data and log files All files created by other storage engines are excluded Typically used when no connection to mysqld is allowed or when there is no need to copy MyISAM files The option is not compatible with the slave info option Defaul
134. combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work and to convey the resulting work The terms of this License will continue to apply to the part which is the covered work but the special requirements of the GNU Affero General Public License section 13 concerning interaction through a network will apply to the combination as such 14 Revised Versions of this License The Free Software Foundation may publish revised and or new versions of the GNU General Public License from time to time Such new versions will be similar in spirit to the present version but may differ in detail to address new problems or concerns Each version is given a distinguishing version number If the Program specifies that a certain numbered version of the GNU General Public License or any later version applies to it you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation If the Program does not specify a version number of the GNU General Public License you may choose any version ever published by the Free Software Foundation If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used that proxy s public statement of acceptance of a version permanently authorizes you to choose that version for the Program Later license
135. cryption Options for more details on backup encryption and decryption 5 2 3 Restoring an Incremental Backup There are different ways to use incremental backups to restore a database under different scenarios The preferred method is to first restore the full backup and make it up to date to the time at which the full backup was performed using the copy back and apply log command see Example 5 5 Restoring a Backup Directory using copy back and apply 1log or Example 5 6 Restoring a Single file Backup using copy back and apply 1log on how to do it then use copy back and apply log again to restore the incremental backup image on top of the full backup that was just restored Example 5 9 Restoring an Incremental Backup Image mysqlbackup defaults file lt backupDir gt backup my cnf uroot backup image lt inc_image_name gt incremental backup dir lt incBackupTmpDir gt datadir lt restoreDir gt incremental N copy back and apply log In this example the incremental backup image named lt inc_image_name gt was restored to lt restoreDir gt on the server where the full backup that the incremental backup image was based on has already been restored The incremental backup dir option is used to specify the temporary directory into which the image will be extracted you can use backup dir for the same purpose Repeat the step with other incremental backup images that you have until the da
136. ctory other metadata is stored in tables within the mysq1 database of the backed up instance no history logging Turns off the recording of backup progress and history in logging tables inside the backed up database See Section 10 4 Using the MySQL Enterprise Backup Logs for details about these tables Default history logging is enabled When no connection is specified history logging is automatically disabled When connect if online Is specified history logging only works if a database connection is successfully established during the backup comments STRING Command Line Format comments STRING Permitted Values Type string 111 Compression Options Specifies a comment string that describes or identifies the backup Surround multi word comments with appropriate quotation marks The string is saved in a file meta comments txt in the backup For example comments Backup of HR data on 2010 12 10 e comments file PATH Command Line Format comments file PATH Permitted Values Type file name Specifies path to a file containing comments describing the backup This file is saved as meta comments txt in the backup For example comments file path to comments txt This option overrides the comment s option if both are specified 13 6 Compression Options For an overview on backup compression see Section 4 3 3 Making a Compressed Ba
137. d 16 of this License or b Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it or c Prohibiting misrepresentation of the origin of that material or requiring that modified versions of such material be marked in reasonable ways as different from the original version or d Limiting the use for publicity purposes of names of licensors or authors of the material or e Declining to grant rights under trademark law for use of some trade names trademarks or service marks or f Requiring indemnification of licensors and authors of that material by anyone who conveys the material or modified versions of it with contractual assumptions of liability to the recipient for any liability that these contractual assumptions directly impose on those licensors and authors All other non permissive additional terms are considered further restrictions within the meaning of section 10 If the Program as you received it or any part of it contains a notice stating that it is governed by this License along with a term that is a further 159 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 restriction you may remove that term If a license document contains a further restriction but permits relicensing or conveying under this License you may add to a cov
138. d functioning of the modified object code is in no case prevented or interfered with solely because modification has been made If you convey an object code work under this section in or with or specifically for use in a User Product and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term regardless of how the transaction is characterized the Corresponding Source conveyed under this section must be accompanied by the Installation Information But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product for example the work has been installed in ROM 158 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 The requirement to provide Installation Information does not include a requirement to continue to provide support service warranty or updates for a work that has been modified or installed by the recipient or for the User Product in which it has been modified or installed Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network Corresponding Source conveyed and Installation Information provided in accord with this sec
139. d options the name of a command is not preceded by any dashes Each of these commands has its own set of required or allowed command options For example the backup command typically requires connection information to the database server The apply log and other commands that operate on the backup data after it is produced require the options that specify where the backup data is located The major groups of commands are e Backup operations backup backup and apply log backup to image e Apply log operations apply log apply incremental backup Restore operations copy back copy back and apply log Validation operation validate Single file backup operations image to backup dir backup dir to image list imag extract 12 1 Backup Operations The backup operations are the most frequently performed tasks by MySQL Enterprise Backup Various kinds of backups can be performed by adding different options like using compress or incremental for compressed or incremental backups Here is the syntax for the mysqibackup commands for performing a backup operation mysqlbackup STD OPTIONS CONNECTION OPTIONS SERVER REPOST TORY OPTIONS BACKUP REPOSTTORY OPLIONS METADATA OPTIONS COMPRESSION OPTIONS SPEC TAL BACKUP_ TYPES OPLIONS INCREMENTAL BACKUP OPTIONS PARTIAL BACKUP RESTORE OPTIONS SINGLE F ILE BACKUP OPTIONS PERFORMANCE SCALABILITY CAPACITY OPTIONS MESSAGE LOGGING O
140. de any data that was deleted while the backup was in process and it must ignore any changes started by transactions but not committed The Oracle product that performs hot backups of InnoDB tables especially but also tables from MyISAM and other storage engines is MySQL Enterprise Backup The hot backup process consists of two stages The initial copying of the InnoDB data files produces a raw backup The apply step incorporates any changes to the database that happened while the backup was running Applying the changes produces a prepared backup these files are ready to be restored whenever necessary A full backup consists of a hot backup phase that copies the InnoDB data followed by a warm backup phase that copies any non InnoDB data such as MyISAM tables and frm files See Also apply cold backup frm file full backup InnoDB instance prepared backup raw backup warm backup ibd file Each InnoDB tablespace created using the file per table setting has a filename with a ibd extension This extension does not apply to the system tablespace which is made up of files named ibdatal ibdata2 and so on See Also ibz file system tablespace tablespace ibz file When the MySQL Enterprise Backup product performs a compressed backup it transforms each tablespace file that is created using the file per table setting from a ibd extension to a ibz extension The compression applied during backup is distinct from the compressed row for
141. distributed in the hope that it will be useful but WITHOUT ANY WARRANTY without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE See the GNU General Public License for more details You should have received a copy of the GNU General Public License along with this program If not see lt http www gnu org licenses gt Also add information on how to contact you by electronic and paper mail If the program does terminal interaction make it output a short 163 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 notice like this when it starts in an interactive mode lt program gt Copyright C lt year gt lt name of author gt This program comes with ABSOLUTELY NO WARRANTY for details type show w This is free software and you are welcome to redistribute it under certain conditions type show c for details The hypothetical commands show w and show c should show the appropriate parts of the General Public License Of course your program s commands might be different for a GUI interface you would use an about box You should also get your employer if you work as a programmer or school if any to sign a copyright disclaimer for the program if necessary For more information on this and how to apply and follow the GNU GPL see lt http www gnu org licenses gt The GNU General Public License does not
142. dure for any partial backups to understand the relevant procedures and restrictions With its include option mysqlbackup can make a backup that includes some InnoDB tables but not others e A partial backup with the include option always contains the InnoDB system tablespace and all the tables inside it e For the InnoDB tables stored outside the system tablespace the partial backup includes only those tables whose names match the regular expression specified with the include option This operation requires the tables being left out to be stored in separate table_name ibd files To put an InnoDB table outside the system tablespace create it while the innodb_file_per_table MySQL configuration option is enabled Each ibd file holds the data and indexes of one table only Those InnoDB tables created with innodb_file_per_table turned off are stored as usual in the InnoDB system tablespace and cannot be left out of the backup For each table with a per table data file a string of the form db_name table_name is checked against the regular expression specified with the include option If the regular expression matches the complete string db_name table_name the table is included in the backup The regular expression syntax used is the extended form specified in the POSIX 1003 2 standard On Unix like systems quote the regular expression appropriately to prevent interpretation of shell meta characters This feature has been imp
143. e within the backup directory and applies log records to the InnoDB data files ibdata and ibd Example 5 2 Applying the Log to a Compressed Backup If the backup is compressed as in Section 4 3 3 Making a Compressed Backup specify the uncompress option to mysqlbackup when applying the log to the backup mysqlbackup backup dir export backups compressed uncompress apply log Example 5 3 Applying an Incremental Backup to a Full Backup After you take an incremental backup as described in Section 4 3 2 Making a Differential or Incremental Backup the changes reflected in those backup files must be applied to a full backup to bring the full backup up to date in the same way that you apply changes from the binary log To bring the data files from the full backup up to date first run the apply log step so that the data files will include any changes that occurred while the full backup was running Then apply the changes from the incremental backup to the data files produced by the full backup mysqlbackup backup dir export backups full apply log mysqlbackup backup dir export backups full incremental backup dir export backups incremental apply incremental backup Now the data files in the ful1 backup directory are fully up to date as of the time of the incremental backup 5 2 Performing a Restore Operation The mysqibackup options to perform a restore operation are copy back and copy back and
144. e In particular InnoDB tables have internal IDs and other data values that can only be restored to the same instance not a different MySQL server Always fully test the recovery procedure for any partial backups to understand the relevant procedures and restrictions Important A Because the InnoDB system tablespace holds metadata about InnoDB tables from all databases in an instance restoring a partial backup on a server that includes other databases could cause the system to lose track of those InnoDB tables in the other databases Always restore partial backups on a fresh MySQL server instance without any other InnoDB tables that you want to preserve The following are some command samples for partial backups Including all tables with names starting with emp into the backup mysqlbackup host localhost user mysqluser protocol TCP port 3306 backup dir MEB_BACKUPS_DIR backupdir include tables emp backup Taking a backup of all tables except tables from the mysql and performance_schema databases mysqlbackup host localhost user mysqluser protocol TCP port 3306 backup dir S MEB_BACKUPS_DIR backupdir exclude tables mysql performance_schema backup Taking a backup of all tables in the sales database but excludes the table with the name hardware mysqlbackup host localhost user mysqluser protocol TCP port 3306 backup
145. e It has to be the first option to defaults extra file PATH Read this file after the global files are read defaults group suffix str Also read option groups with the usual names and a suffix of str The following options are also common between mysqibackup and mysql and full descriptions for them can be found in the MySQL reference manual accessible through e g Server Option and 102 Standard Options Variable Reference However mysqlbackup does not accept any short forms for these options as mysql does for example you must use help instead of h for mysqlbackup help Display help version Display version information verbose Print more verbose information debug Print debug information More standard options are available for mysqlbackup force Force overwriting of data log or image files depending on the operation trace level Trace level of messages by mysqlbackup force By default some of the operations halt rather than overwrite any user data or log files when told to write to existing files force allows the following e Overwriting of InnoDB data and log files during the apply log and apply incremental backup operations e When restoring a TTS backup changing temporarily the value of innodb_file format on the server in order to allow restores of per table InnoDB data files regardless of their format Replacing of an image file during an backup to image or backup dir t
146. e MySQL Enterprise Backup can also read settings from the client section for configuration options that are common between MySQL Enterprise Backup and other programs that connect to the MySQL server See Also my cnf my ini connection The mechanism used by certain backup operations to communicate with a running MySQL server For example the mysqlbackup command can log into the server being backed up to insert and update data in the progress table and the history table A hot backup typically uses a database connection for convenience but can proceed anyway if the connection is not available A warm backup always uses a database connection because it must put the server into a read only state A cold backup is taken while the MySQL server is shut down and so cannot use any features that require a connection See Also cold backup history table hot backup progress table server warm backup crash recovery D The cleanup activities for InnoDB tables that occur when MySQL is started again after a crash Changes that were committed before the crash but not yet written to the tablespace files are reconstructed from the doublewrite buffer When the database is shut down normally this type of activity is performed during shutdown by the purge operation data dictionary A set of tables controlled by the InnoDB storage engine that keeps track of InnoDB related objects such as tables indexes and table columns These tables are part
147. e and they are not modified by the option values supplied through the command 14 Files that Are Backed Up File Name Pattern or Extension Relation to Original Data Files Notes Warning When using the file to restart the target server change parameters like tmpdir general log etc and any global variable that uses an absolute filepath to avoid the accidental usage of the wrong file locations by the target server server all cnf Contains values of all the global variables of the backed up server Use this file or server my cnf to start the target server for restoration During a copy back or copy back and apply log operation the server repository options values e g datadir innodb_data_home_dir etc in the file are modified if the command makes changes to them through the command options However during an apply incremental backup operation the values already saved in the file take precedence and they are not modified by the option values supplied through the command S Warning When using the file 15 InnoDB Data File Name Pattern or Extension Relation to Original Data Files Notes to restart the target server change parameters like tmpdir general log etc and any global variable that uses an absolute filepath to avoid the accidental usage of the wrong file
148. e the CSV format so the backup always includes some files with this extension MRG MERGE storage engine references to other tables The database is put into a read only state while these files are copied These files are copied without changes TRG Trigger parameters The database is put into a read only state while these files are Files that Are Backed Up File Name Pattern or Extension Relation to Original Data Files Notes copied These files are copied without changes IRN Trigger namespace information The database is put into a read only state while these files are copied These files are copied without changes ODE Database configuration information The database is put into a read only state while these files are copied These files are copied without changes opar Definitions for partitioned tables The database is put into a read only state while these files are copied These files are copied without changes ARM Archive storage engine metadata The database is put into a read only state while these files are copied These files are copied without changes ARZ Archive storage engine data The database is put into a read only state while these files are copied These files are copied without changes backup my cnf Records the configuration parameters that specify the layout of the MySQL
149. e Backup 1 5 Overview of Restoring a Database To initiate the restore process you run the mysqlbackup client with the copy back or the copy back and apply log command You can restore all the data for a MySQL server with multiple databases 17 Overview of Restoring a Database each containing multiple tables Alternatively you can also choose to restore selected databases tables or both To repair a problem such as data corruption you restore the data back to its original location on the original server machine You might restore to a different server machine or a different location to set up a new replication slave with the data from a master server or to clone a database for reporting purposes See Chapter 5 Recovering or Restoring a Database for instructions on restoring databases 18 Chapter 2 Installing MySQL Enterprise Backup Install MySQL Enterprise Backup on each database server whose contents you intend to back up Typically you perform all backup and restore operations locally by running mysqlbackup on the same server as the MySQL instance Optional You can also install MySQL Enterprise Backup on computers other than the database server only to run mysqlbackup with the apply log option See Section 12 2 Apply Log Operations for information about bringing backup data to a separate server and running the apply log step there MySQL Enterprise Backup is packaged as either an archi
150. e a partial backup including only those InnoDB tables in test database whose name starts with ib The contents of the database directory for test database are shown below The directory contains a MySQL description file frm file for each of the tables alex1 alex2 alex3 blobt3 ibstest0 ibstest09 ibtestila ibtest11b ibtestlic and ibtest11d in the database Of these 10 tables six alex1 alex2 alex3 blobt3 ibstest0 ibstest09 are stored in per table data files ibd files 43 Making a Partial Backup ls sqldata mts test alexl frm alex2 ibd blobt3 frm ibstest0O ibd ibtestlla frm ibtestlld frm alexl ibd alex3 frm blobt3 ibd ibtest09 frm ibtestllb frm alex2 frm alex3 ibd ibstest0O frm ibtest09 ibd ibtestllc frm We run the mysqlbackup with the include option Back up some InnoDB tables but not any frm files mysqlbackup defaults file home pekka my cnf include test ib only innodb backup many lines of output mysqlbackup Scanned log up to lsn 2666737471 mysqlbackup Was able to parse the log up to lsn 2666737471 mysqlbackup Maximum page number for a log record 0 101208 17 17 45 mysqlbackup Full backup completed Back up some InnoDB tables and the frm files for the backed up tables only mysqlbackup defaults file home pekka my cnf include test ib only innodb with frm related backup many lines of output mysqlbackup Scanned log up to 1lsn 2666737
151. e all recipients a copy of this License along with the Program You may charge any price or no price for each copy that you convey and you may offer support or warranty protection for a fee 5 Conveying Modified Source Versions You may convey a work based on the Program or the modifications to produce it from the Program in the form of source code under the terms of section 4 provided that you also meet all of these conditions a The work must carry prominent notices stating that you modified it and giving a relevant date b The work must carry prominent notices stating that it is released under this License and any conditions added under section 7 This requirement modifies the requirement in section 4 to keep intact all notices c You must license the entire work as a whole under this License to anyone who comes into possession of a copy This License will therefore apply along with any applicable section 7 additional terms to the whole of the work and all its parts regardless of how they are packaged This License gives no permission to license the work in any other way but it does not invalidate such permission if you have separately received it d If the work has interactive user interfaces each must display Appropriate Legal Notices however if the Program has interactive interfaces that do not display Appropriate Legal Notices your work need not make them do so A compilation of a covered work with other
152. e eres sees aaaaaaeeeeeeeeeeaaaaaaneeeeeeeeeaea 13 4 Backup Repository Options ccccceccceeeeeeeeeeeee ee aaa eeeeeeeeeeeeaaaaeeeeeeeeeeeeaaaaeneeseeeees 13 5 Metadata Options sisisi isan aaa a E a a EE 13 6 CompressioM Options sisse toinnasni nina aaa aaa ea bea a 13 7 Incremental Backup Options sseseseenesessssssterntrreersstsrntnnnerastsnntnnterstsnntnnnensnsnnnn 13 8 Partial Backup and Restore Options ccccceeeceeeee cece ee eeeeeeeeeeeeeeaaaaeeeeeeeeeeeeaeaaeaees 13 9 Single File Backup Options 0 cece ce eeeeee cece ee ceeeeeeeee sees ee ae aa eeneeeeeeeeeaeaaeaeeeeeeeeeeeaaa 13 10 Performance Scalability Capacity Options 0 cceceeeeeeceeeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaaa 13 11 Message Logging Options c ccc ececeeeee cece ee eeeeteee tees sees ae ea eeeeeeeeeeeaeaaeeneeeeeeeeeaeaaea 13 12 Progress Report Options csssevececssececceancvecaseadssteastty dcaben scant bits ndanan seeded A aAA AAR 13 13 Encryption Options ai sic psec asstectiteeteceresnattieneptee ss E E a E 13 14 Gloud Storage OptiONns sis sesseccens se cceseeseedeentepceesbssi eve snnstoeeeassaudered ee ceeeb saeeenneeeeeeeenaades 13 15 Options for Special Backup Types ccccceeeeeeeaeeeeeeeeeeeeeeeaaaaeeeeeeeeeeeaaaaeeneeeereees 14 Configuration Files and Parameters ccccccecececeeeeeeeeeeeeeeeaeaaeeteeeeeeeeeaeaaeaeeeeeeeeeaeaaeaenees W APPONI S ae toe ese atte et er waters a nomen teins Sa
153. e following command extracts all contents of the meta directory including all its files and subdirectories into the directory tmp my meta mysqlbackup backup image backup my mbi src entry meta dst entry tmp my meta extract Example 4 14 Dealing with Absolute Path Names Since absolute pathnames are extracted to the same paths in local system it could be a problem if you do not have write permission for that path You can remap absolute paths as follows mysqlbackup backup image backup my mbi src entry dst entry myroot extract mysqlbackup backup image backup my mbi src entry extract The first command extracts all absolute paths to myroot directory in the local system The second command extracts all relative paths to the current directory 4 3 5 1 Streaming the Backup Data to Another Device or Server To limit the storage overhead on the database server you can transfer the backup data to a different server without ever storing it locally You can achieve that with a single file backup To send the single file backup to standard output use the mysqlbackup command backup to image without specifying the backup image option You can also specify backup image to make it obvious that the data is sent to stdout To stream the data you use the single file backup in combination with operating system features such as pipes ssh scp and so on which take the input from standard output and create an equ
154. e of the option for mysqibackup to find the relay log files and include them in the backups The index file itself with the locations of the relay log files properly updated to point to the files locations in the backup directory is included into the backup under the datadir directory The relay log files are compressed and saved with the bz extension when being included in a compressed backup The relay log files and the index file when included in a backup are always copied into the restored server s data directory during a restore operation Use the skip relaylog option to skip the restoring of the relay log bz Compressed binary log or relay log files The binary log and relay log files are compressed and saved with the bz extension when being included in a compressed backup They are decompressed during a restore slave status log files Usually named master info and relay log info they are included by default in a backup of a slave database in a replication setup See Slave Status Logs for details Saved under the datadir directory under the backup directory For an offline backup use the master info fil and relaylog info file options to specify the absolute paths of the information files if they are different from the default values of the options for 12 Files that Are Backed Up File Name Pattern or Extension Relation to Original Data Files
155. e redo log cycles and LSNs get overwritten by the server before they are read by mysqlbackup The problem is intensified when the I O resources available for reading and writing the redo logs are scarce during the backup process However if only a small number of tables of the database are modified frequently the Optimistic Backup feature might alleviate the problem See Section 4 3 6 Making an Optimistic Backup for details Compressed InnoDB tables from MySQL server 5 6 10 and earlier cannot be restored with MySQL Enterprise Backup 3 9 0 or later due to a known issue with the InnoDB storage engine see Bug 72851 on the MySQL Bug System While it is possible to backup to or restore from a Network Attached Storage NAS device using MySQL Enterprise Backup due to networking issues that might arise the consistency of the backups and the performance of the backup or restore operations might be compromised When creating a backup using transportable tablespace TTS for a server containing tables with a mix of the Antelope and Barracuda file formats do not apply full locking on the tables that is do not specify use tts with full locking Instead just specify use tts or use tts with minimum locking both of which will apply minimum locking to the tables Bug 20583946 Tables created on the MySQL server with the ANSI_QUOTES SQL mode cannot be backed up using transportable tablespace TTS 148 Appendix C
156. e tables testdb tl use tts with full locking N cloud service openstack cloud container lt swift container gt cloud user id lt keystone user gt cloud password lt keystone password gt cloud region lt keystone region gt cloud tenant lt keystone tenant gt cloud identity url lt keystone url gt cloud trace 1 cloud object image_800 mbi backup dir home user dba s3backuptmpdir backup image backup to image Besides backup to image all other mysqibackup operations for single file backups backup dir to image list image validate image to backup dir extract copy back and copy back and apply log can also be performed with cloud storage For example Example 4 20 Extract an Existing Image from Amazon S3 Cloud Storage to Backup Directory Extract a backup image from Amazon S3 using the backup dir option to specify the directory into which the image will be extracted mysqlbackup cloud service s3 cloud aws region lt aws region gt cloud access key id lt aws access key id gt cloud secret access key lt aws secret access key gt cloud bucket lt s3 bucket name gt cloud object key lt aws object key gt backup dir home user dba s3backuptmpdir backup image image to backup dir See Section 5 2 5 Restoring a Backup from Cloud Storage to a MySQL Server on how to restore a backup image from a cloud storage 4 3
157. e the number of read or write threads iowait once the system iowait value reaches approximately 20 70 Chapter 8 Encryption for Backups In order to enhance security for backed up data MySQL Enterprise Backup provides encryption for single file backups The encryption can also be applied when creating a partial compressed or incremental single file backups and for streaming backup data to another device or server The encryption is performed with Advanced Encryption Standard AES block cipher in CBC mode with a key string of 64 hexadecimal digits supplied by the user Decryption is performed using the same key The key can be created manually just by putting together 64 random hexadecimal bytes or it can be generated by shasum or similar programs for hash calculations that work on your platform by supplying it with a keyphrase echo n my secret passphrase shasum a 256 a7e845b0854294da9aa7 43b807cb67b19647c1195ea8120369F3d12c70468f29 Note that the at the end is not part of the key and should be ignored Supply the key to mysqlbackup with the key option or paste the key into a key file and supply the file s pathname to mysqlbackup with the key file option To generate a key randomly you can use tools like OpenSSL openssl rand 32 hex 8f3ca9b850ec6366f4a54feba99f2dc42fa79577158911fe8cd641ffffle63d6 To put an OpenSSL generated key into a key file you can do the following openssl rand 32 hex
158. e user or the cron job running mysqlbackup has the rights to copy files from the MySQL database directories to the backup directory 85 Make sure that your connection timeouts are long enough so that the mysqlbackup command can keep the connection to the server open for the duration of the backup run mysqibackup pings the server after copying each database to keep the connection alive Important A Although mysqlbackup backs up InnoDB tables without interrupting database use the final stage that copies non InnoDB files such as MyISAM tables and frm files temporarily puts the database into a read only state using the statement FLUSH TABLES WITH READ LOCK For best backup performance and minimal impact on database processing 1 Do not run long SELECT queries or other SQL statements at the time of the backup run 2 Keep your MyISAM tables relatively small and primarily for read only or read mostly work Then the locked phase at the end of a mysqlbackup run is short maybe a few seconds and does not disturb the normal processing of mysqid much If the preceding conditions are not met in your database application use the only innodb option to back up only InnoDB tables or use the no locking option to back up non InnoDB files Note that MyISAM frm and other files copied under the no locking setting cannot be guaranteed to be consistent if they are updated during this final phase of the backup For a
159. e_size 256M innodb_log_files_in_group 3 All paths in the generated backup my cnf file point to a single backup directory For ease of verification and maintenance you typically store all data for a backup inside a single directory rather than scattered among different directories 139 Configuration Files Stored with the Backup Data During a backup the configuration parameters that are required for later stages such as the restore operation are recorded in the backup my cnf file that is generated in the backup directory Only the minimal required parameters are stored in backup my cnf to allow you to restore the backup to a different location without extensive changes to that file For example although the innodb_data_home_dir and innodb_log_group_home_dir options can go into backup my cnf they are omitted when those values are the same as the backup dir value 140 Part IV Appendixes Table of Contents A Frequently Asked Questions for MySQL Enterprise Backup ccceeeeeceeeeeeeeeeeeeeeeaeaaeeeeeeeeeees 145 B MySQL Enterprise Backup Limitations cccccceeeeeeeeeee ee eee eeee ener ee ee seed eeeeeeeeeeaeaaeeneeeeeeeeeaeaae 147 B 1 Limitations of MySQL Enterprise Backup ccccecceeeeeeeeeeeee ee aaeeeeeeeeeeeeeaeaaaeneeeeeeeeeaeaaed 147 C Compatibility Information for MySQL Enterprise Backup ccceeeeceeeeeeeeeeeeeeaeaaeaeeeeeeeeeeeeaaaaeeees 149 C 1 Cr
160. ead only state so that the backup operation is a true hot backup and does not interrupt database processing You must ensure that no ALTER TABLE or other DDL statements change frm files for InnoDB tables while the backup is in progress If mysqlbackup detects changes to any relevant frm files during the backup operation it halts with an error If it is not practical to forbid DDL on InnoDB tables during the backup operation use the only innodb option instead and use the traditional method of copying the frm files while the server is locked 120 Single File Backup Options All files created by other storage engines are excluded Typically used when no connection to mysqid is allowed or when there is no need to copy MyISAM files for example when you are sure there are no DDL changes during the backup See Making a Partial Backup with the Legacy Options for instructions and examples The option is not compatible with the slave info option Default backups include files from all storage engines e use tts with minimum locking with full locking Enable selective backup of InnoDB tables using transportable tablespaces TTS This is to be used in conjunction with the include option which selects the InnoDB tables to be backed up by a regular expression Using TTS for backups offers the following advantages e Backups can be restored to a different server e The system tablespace is not backed up sav
161. eaeeneeeeeeeeeeeeaea 6 14 Files that Are Backed UD socceveasliosseiiei sin ERR E AEE A a K R 7 1 5 Overview of Restoring a Database sssessssssessssttrirttsstttttttnttttstttn ttnt neeeeeeeeeaeaaaaeeeeeeeeeaeaaea 17 The MySQL Enterprise Backup product performs backup operations for MySQL data It can back up all kinds of MySQL tables It has special optimizations for fast and convenient backups of InnoDB tables Because of the speed of InnoDB backups and the reliability and scalability features of InnoDB tables we recommend that you use InnoDB tables for your most important data This book describes the best practices regarding MySQL backups and documents how to use MySQL Enterprise Backup features to implement these practices This book teaches you Why backups are important e The files that make up a MySQL database and the roles they play e How to keep the database running during a backup e How to minimize the time CPU overhead and storage overhead for a backup job Often minimizing one of these aspects increases another e How to restore your data when disaster strikes You learn how to verify backups and practice recovery so that you can stay calm and confident under pressure e Other ways to use backup data for day to day administration and in deploying new servers 1 1 Types of Backups The various kinds of backup techniques are classified on a scale ranging from hot the most desirable to cold the most disrupt
162. ect to 100 Format Description Introduced print defaults process threads Print a list of option values supplied by defaults files and exit Specifies the number of process threads for the backup operation progress interval Interval between progress reports in seconds protocol Connection protocol read threads relay log index Specifies the number of read threads for the backup operation Specifies the absolute path of the index file on the MySQL server that lists all the used relay log files for offline backups of salve servers only relaylog info file Specifies the absolute path of the information file in which a slave records information about the relay logs for offline backups of salve servers only rename Rename a single table when it is selected by the include tables option to be restored 3 12 0 sbt database name sbt environment Used as a hint to the Media Management Software MMS for the selection of media and policies for tape backup Comma separated list of environment variable assignments to be given to the SBT library sbt lib path Path name of the SBT library used by software that manages tape backups secure auth Refuse client connecting to server if it uses old pre 4 1 1 protocol shared memory base name show progress It designates the shared memory name used by a Windows s
163. ecution of the command progresses For some operations such as backup it is not possible to know exactly at the start of the execution how much data will be copied or processed Therefore the total data meter shows the estimated amount of the total data for a backup The estimate is updated during the execution of the command For example Progress 200 of 1450 MB is followed by Progress 200 of 1550 MB when 100MB of data is added on the server If the operation is successful the final progress indicator shows the actual amount of data copied at the end of the operation Compression meter It indicates the sliding average of the compression ratio which is defined for each block of data that is compressed as orig_size compressed_size orig_size For example compression 40 This means that after compression the data takes 40 less space calculated as an average over the last 10 data blocks The compression meter is included in the progress indicator if the compress option is enabled for the mysqlbackup operation The value of the compression meter is undefined until at least 10 data blocks have been compressed The undefined meter value is denoted by the in the meter compression 133 Encryption Options e State meter It is a short description of the major step the command is currently executing For example State Here are Progress Progress Copying tate Waiting te
164. ed for debugging them And because the default path name of backup_dir meta is not meaningful for the two operations this option is required for both turning on message logging and for supplying the path name of a directory in which to save the log file However if the skip messages logdir option is also specified it takes precedence and message logging is skipped The following are some examples showing how the message logging is controlled This creates a log file for the backup operation in the directory home backup_dir meta due to the default settings mysqlbackup uroot port 3306 backup dir home backup_dir backup This skips message logging for the backup operation mysqlbackup uroot port 3306 backup dir home backup_dir skip messages logdir backup This creates a log file for the app 1 y 1og operation in an existing directory named home teelog_dir rather than the default location mysqlbackup uroot port 3306 backup dir home backup_dir messages logdir home teelog_dir apply log This creates a log file for the 1ist image operation in an existing directory named home teelog_dir mysqlbackup uroot port 3306 backup image backup my mbi messages logdir home teelog_dir list image 13 12 Progress Report Options There are two options for controlling the progress reporting function of mysqibackup show progress and progress interval show progress stderr
165. eeeeeee ce aeeeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaeaeenees 61 6 1 Setting Up a New Replication Slave ccccceccceceeeeeee ee eeceeeeeeee sees ae aaeeteeeeeeeeeaeaaeeneeeeeeeeeaeaaea 61 6 2 Backing up and Restoring a Slave Database cccceeceeeceee eee eeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeaaes 62 6 3 Restoring a Master Database i cceceeeeeeeee eee e eee erence eee NKANKA NENNEN AA KE NENEN EEEE 63 7 Performance Considerations for MySQL Enterprise Backup c ccccceeeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeeees 65 7 1 Optimizing Backup Performance ccccceeeeeeeeeeeee ee eeteeeee sees ae aaa eeeeeeeeeeaeaaaaeeeeeeeeeseaaaaeeees 65 7 2 Optimizing Restore Performance ccccccecceeeeeeeee ects ee ae ee eeeeeeeeee ee ae aaa teeeeeeeeeaeaaeaneeeeeeeeeaeaaed 68 8 Encryption for Backups ccccceeeeeeeee eee e ee eee ranana a aaiae naaie ainina 71 9 Using MySQL Enterprise Backup with Media Management Software MMS Products 606 73 9 1 Backing Up to Tape with Oracle Secure Backup ccececeeeeeeeeeeeeeeeeaaeeeeeeeeeeeeaeaaeaneneeees 73 10 Troubleshooting for MySQL Enterprise Backup cceeceeeeeeeeeaeeeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaaaneeeeeees 75 10 1 Monitoring Backups with MySQL Enterprise Monitor ccseceeeeeee cee eeeeeeeeeeeeaeaaeaeeneeeees 75 10 2 Error codes of MySQL Enterprise Backup cccececeeeeeeeeeeeeee ee aa ee eeeeeeeeeeseaaaae
166. eeeeeeeeeeaeceeeeeeeeeeeeeaeaaeeeeeeeeeees 61 6 1 Setting Up a New Replication Slave ccceccccceeeeeeeee sees ee aaeeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaaaeeeees 61 6 2 Backing up and Restoring a Slave Database ccecccceeeeeeeeeee tees aa eeeeeeeeeeeeeaaaaeeeees 62 6 3 Restoring a Master Database 00 cece cece cence eens eee ee eee tees eee eeeeeeaeeeeeeeaaeeeeaaaeeeeeaaees 63 7 Performance Considerations for MySQL Enterprise Backup ceceeeeeeeaeeeeeeeeeeeeeeeaeaaeeees 65 7 1 Optimizing Backup Performance ccccccceeceeeeeeee tees eee eeeeeeeeeeeeaeaaeeneeeeeeeeeaeaaaaneneeeees 65 7 2 Optimizing Restore Performance ccccccecceeeeeeeeeeeee ee aeeeeeeeeeeeeaeaaeaeeeeeeeeeeaeaaaaneneeeees 68 8 Encryption for BackUPS ccccecceeeeeeeeee cece eee ecee ee ee eset eieaa eaaa ea a aaeei 71 9 Using MySQL Enterprise Backup with Media Management Software MMS Products 73 9 1 Backing Up to Tape with Oracle Secure Backup ccceceeeeeee eee eeeeeeeeeeeeaeaaeaeeeeeeees 73 MySQL Enterprise Backup User s Guide Version 3 12 1 10 Troubleshooting for MySQL Enterprise Backup cccccceeeeeeeeeee cece aaa eeeeeeeeeeeeaaaaeeeeeeeeeeeaaa 10 1 Monitoring Backups with MySQL Enterprise Monitor cecceeeeeeeeeeeeeeeaeaeeneeeeeeees 10 2 Error codes of MySQL Enterprise Backup 0 cceceeeeeeeeeeeeeeeeeeeeeaeeaeeeeeeeeeeeeaeaaeeees 10 3 Working
167. eeeeeeeeeeaes 51 4 3 8 Making Scheduled Backups c cececeeeeeeeeeeeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaaaeneeeseeeees 51 4 4 Making Backups with a Distributed File System DFS or Storage Access Network SANJ aiaa sone caw tioan hex ddacdeuyseausthssGectuasieliu chan scnatuasieuusbess cacausauegusnd as Ea Ean Kaaa aaia Eea 52 5 Recovering or Restoring a Database ececcccseeececeeeeeeeee eee eeeeee ENEAN 53 5 1 Preparing the Backup to be Restored cc eceeeeeeeee eee eeeeeeeeeeeeeaeeeeeeaaeeeeeeaaeeeeeeaaieeees 53 5 2 Performing a Restore Operation cccececceeeeeeee cece ae eeeeeeeeeeeeaeaaeaeeeeeeeeeeeeaaaaeeeeeseeeees 54 5 2 1 Restoring a Compressed Backup 0 ceceeeeeeeeeaeeeeeeeeeeeeeeeaaeaeeeeeeeeeeaeaaeaeeeees 55 5 2 2 Restoring an Encrypted Backup Image ceeeeeeeeeee ene eeeeeeeeeeeeeeeeeeeeeeeeeeeeeaaes 56 5 2 3 Restoring an Incremental Backup cceeeeeenneeeeeeaeeeeeeeaaeeeeeeaaeeeeeeaaeeeeeeaaeeees 56 5 2 4 Restoring Backups Created with the use tts Option ce eeceeeeeeeeeeeeeeeees 57 5 2 5 Restoring a Backup from Cloud Storage to a MySQL Server c eeeeeeeeeeeees 58 5 3 Point in Time Recovery from a Hot Backup cceececeeeeeee ee eeeeeenaeeeeeeaaeeeeeeaaaeeeeeaaeeees 58 5 4 Restoring a Backup with a Database Upgrade or Downgrade 0ceeeeeeeeeeeeeeeeeeeeeee 59 6 Using MySQL Enterprise Backup with Replication ccccceee
168. eeeseeeeeeaaa 75 10 3 Working Around Corruption Problems cccceeceeeeeeee cece eae eeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeaneneeeees 76 10 4 Using the MySQL Enterprise Backup LOGS c cceceeeeeeeeeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeaneneeeees 76 10 5 Using the MySQL Enterprise Backup Manifest ccccccceeeeeeeeeeeee ee aaeeeeeeeeeeeeeeaaeaeeneeeees 78 25 26 Chapter 4 Backing Up a Database Server Table of Contents 4 1 Before the First BACKUP soccirceniiisreniiipiei iior ceccavadeecsecnceded ene cuus centeceb A dvessbed scnetene EEEREN ENE BAREK 27 4 1 1 Collect Database Information cccceeeee cece eeeeeeeeeee tees ae ea eeeeeeeeeeeeaaaaaeeeeeeeeeeeaeaaeeneeseeeees 27 4 1 2 Grant MySQL Privileges to Backup Administrator c c cceeceeeeeeeeeeeeeeeeeeeeeeeseaaenneeeeeees 29 4 1 3 Designate a Location for Backup Data 0 cccccseceeeeeee ee aeeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaaaeeeeeees 30 4 2 The Typical Backup Verify Restore Cycle cccccccceeeeeeeeeee tees eee eeteeeeeeeeeaeaaeneeeeeeeeeaeaaeaneneeeees 30 4 2 1 Backing Up an Entire MySQL Instance ccecceeee ee eeeeeeeeeeee tees ee aa ee eeeeeeeeeeeeaaaaeeeeeeeeeeeaea 30 4 2 2 Veritying a BACKUP scccisiecccasiesekecan erener erne dese cons ERENER teeta ATIRE CENE REENE REEE RAE i 32 4 2 3 Restoring a Database at its Original Location 0 0 0 0 cece cece eeeeeeeeee eee eeeeeeeeeeeeaaaaeeeeeeeeee
169. ement Software MMS for the selection of media and policies This name has nothing to do with MySQL database names It is a term used by the MMS See Section 4 3 5 2 Backing Up to Tape for usage details sbt lib path PATH Command Line Format sbt lib path PATH Permitted Values Type file name Path name of the SBT library used by the software that manages tape backups If this is not specified operating system specific search methods are used to locate 1ibobk so UNIX or orasbt d11l Windows See Section 4 3 5 2 Backing Up to Tape for usage details e sbt environment VAR value Command Line Format sbt environment VAR1 valuel VAR2 value2 SBT API provider Permitted Values Type string Passes product specific environment variables to Oracle Secure Backup or another SBT compliant backup management product as an alternative to setting and unsetting environment variables before and after each mysqlbackup invocation The parameter to this option is a comma separated list of key value pairs using syntax similar to that of the RMAN tool for the Oracle Database For example sbt environment VAR1 vall VAR2 val2 VAR3 val3 Consult the documentation for your backup management product to see which of its features can be controlled through environment variables For example the Oracle Secure Backup product defines environment variables such as OB_MEDIA_FAM
170. en a database connection exists the value is retrieved automatically and overrides any value you specify e innodb_checksum_algorithm NAME Specifies the name of the checksum algorithm used for validating InnoDB tablespaces Default is innodb Typically you do not need to specify this option because its value is retrieved automatically using the database connection If no database connection is available you must specify it When a database connection exists the value is retrieved automatically and overrides any value you specify 13 4 Backup Repository Options These options specify various parameters related to the backup directory and its layout or to how the backup will be restored Typically backup dir is the only option from the group that you need to specify when using mysqlbackup The backup repository options are used with the following operations e Backup operations backup backup and apply log backup to image e Restore operations copy back copy back and apply log The backup repository options are divided into two groups the first one determines the structure of the backup and the second one provides information on the original structure of the data on the backed up server for future operations on the backup The following options determine the structure of the backup backup_dir PATH Same as backup dir The directory under which the backup data and metadata are stored permanently or temporarily I
171. enaming a Table from a TTS Backup ccceceeeeeeeceeeeeeeeeeeeeaeaaeeeeeeeeeeeaeaaes 58 5 12 Restoring a Single file Backup from Amazon S3 to a MySQL Server cccceecceeeceeeeneeeeeeaaeeeees 58 5 13 Restoring a Single file Backup from an OpenStack Object Storage to a MySQL Server 58 9 1 Sample mysqlbackup Commands Using MySQL Enterprise Backup with Oracle Secure Backup Siete sale a leneaeuegetmecctinn tenes E qetnmee fraiherattis oucnmecrnnsd eatetasarecenerereteceednecteerats 74 12 1 Apply Log to Full Backups s icicccsccsseccectanecentnsuseeandanecennas aeaa aea a aa a anai ni 89 141 Example backup my cnf Te asirieni tenai nara AAAA RRELA ceteceabeacnaads EKEREN EE 139 Preface and Legal Notices This is the User Manual for the MySQL Enterprise Backup product For license information see the Legal Notices This product may contain third party code For license information on third party code see Appendix E Licenses for Third Party Components Legal Notices Copyright 2003 2015 Oracle and or its affiliates All rights reserved This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish
172. eprod 2011 05 30 sbt database name shoeprod backup dir backup backup to image Uses an alternative SBT library opt Other MMS so mysqlbackup port 3306 protocol tcp user root password backup image sbt backup shoeprod 2011 05 30 sbt lib path opt Other MMS so backup dir backup backup to image 74 Chapter 10 Troubleshooting for MySQL Enterprise Backup Table of Contents 10 1 Monitoring Backups with MySQL Enterprise Monitor 0 cccceeceeeeeeeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaaaeeeees 75 10 2 Error codes of MySQL Enterprise Backup cccccceeeeeeeeeee tees ee ee eeeeeeeeeeeeaeaaeeeeseeeeeeaeaaeaneeeeeees 75 10 3 Working Around Corruption Problems ccceceeeeeee eee eeeeeeeeeeee ce aaeaeeeeeeeeeeaeaaaaeeeeeeeeeeeaaaaeeeees 76 10 4 Using the MySQL Enterprise Backup LOGS ccccccceeeeeeeeeee ee ce aa eeteeeeeeeeeaeaaeaeeeeeeeeeeaeaaaaneneeeees 76 10 5 Using the MySQL Enterprise Backup Manifest c cccceeeeeeeeee ee aaeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaaaeenees 78 To troubleshoot issues regarding backup and restore with the MySQL Enterprise Backup product consider the following aspects e Before troubleshooting any problem familiarize yourself with the known limits and restrictions on the product in Appendix B MySQL Enterprise Backup Limitations If mysqibackup encounters problems during operating system calls it returns the corresponding O
173. er circumstances is permitted solely under the conditions stated below Sublicensing is not allowed section 10 makes it unnecessary 3 Protecting Users Legal Rights From Anti Circumvention Law No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996 or similar laws prohibiting or restricting circumvention of such measures When you convey a covered work you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work and you disclaim any intention to limit operation or modification of the work as a means of enforcing against the work s users your or third parties legal rights to forbid circumvention of technological measures 4 Conveying Verbatim Copies You may convey verbatim copies of the Program s source code as you 156 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 receive it in any medium provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice keep intact all notices stating that this License and any non permissive terms added in accord with section 7 apply to the code keep intact all notices of the absence of any warranty and giv
174. ered work material governed by the terms of that license document provided that the further restriction does not survive such relicensing or conveying If you add terms to a covered work in accord with this section you must place in the relevant source files a statement of the additional terms that apply to those files or a notice indicating where to find the applicable terms Additional terms permissive or non permissive may be stated in the form of a separately written license or stated as exceptions the above requirements apply either way 8 Termination You may not propagate or modify a covered work except as expressly provided under this License Any attempt otherwise to propagate or modify it is void and will automatically terminate your rights under this License including any patent licenses granted under the third paragraph of section 11 However if you cease all violation of this License then your license from a particular copyright holder is reinstated a provisionally unless and until the copyright holder explicitly and finally terminates your license and b permanently if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation Moreover your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means this is the first time you have received notice of violat
175. erring files and CPU speed processor cores and so on for uncompressing data For the combination of options you can specify for a restore job see Section 12 3 Restore Operations Restoring Different Classes of Backup Data Restoring a partial backup takes less time than restoring a full backup because there is less data to physically copy See Section 13 8 Partial Backup and Restore Options for information about making partial backups Restoring a compressed backup takes more time than restoring an uncompressed backup because the time needed to uncompress the data is typically greater than any time saved by transferring less data across the network If you need to rearrange your storage to free up enough space to uncompress the backup before restoring it include that administration work in your estimate of the total time required In an emergency the time needed to uncompress the backup data before restoring it might be unacceptable on the database server to hold both the compressed backup and the uncompressed data Thus the more critical the data is the more likely that you might choose not to use compression accepting a slower larger backup to ensure that the restore process is as fast and reliable as possible See Section 13 6 Compression Options for information about making compressed backups The unpacking process to restore a single file backup is typically not expensive either in terms of raw speed or extra sto
176. erver to permit clients to connect using shared memory Windows only Instructs mysqlbackup to periodically output short progress reports known as progress indicators on its operation skip binlog Do not include binary log files during backup or do not restore binary log files during restore skip messages logdir Disable logging to teelog file skip relaylog skip unused pages Do not include relay log files during backup or do not restore relay log files during a restore Skip unused pages in tablespaces when backing up InnoDB tables slave info Capture information needed to set up an identical slave server sleep Time to sleep in milliseconds after copying each 1MB of data socket Socket file to use to connect src entry Identifies a file or directory to extract from a single file backup 101 Standard Options Format Description Introduced ssl Enable SSL for connection automatically enabled with other ssl flags ssl ca CA file in PEM format implies ssl ssl capath CA directory check OpenSSL docs implies ssl ssl cert X509 cert in PEM format implies ssl ssl cipher SSL cipher to use implies ssl ssl key X509 key in PEM format implies ssl ssl verify server cert Verify server s Common Name in its cert against hostname used when connecting Start Isn Specifies the highest LSN value
177. es 32 4 3 Backup Scenarios and Examples 0 ccccccecceeeeeeeeeeeeee ee ae eae teeeeeeeeeseaaeageeeeeeeeeeeaaaaeeegeseeeeeeaeaaeaaes 34 43 1 Making a Full Backup ssccecc cceccsd i cgocee et aoe caveeaied ances tech ddan ected deed snaeeuud seca E 34 4 3 2 Making a Differential or Incremental Backup 0 ccccececeeeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeaneneeeees 35 4 3 3 Making a Compressed Backup ceceeeeeeeceeeeneeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeaneeeeeeeeeaeaaaaeeeees 39 4 3 4 Making a Partial BACKUP 2000 2 eee ee eer ee ener reed NEA KNEE KENNEN ERREEN NEE 40 4 3 5 Making a Single File Backup ccceceeceeeeee cece ee aeecee eter sees ae aa eae eeeeeeeeseaaaaaaneeeeseeeeaaaaenees 45 4 3 6 Making an Optimistic Backup ccceeeeeeeee cece ee eeee eres ee aeaaeaeeeeeeeeeeaeaaeaeeeeeeeeeaeaaeaneneeeees 49 4 3 7 Making a Back Up of In Memory Database Data cccccceceeeeeee eee eeeeeeeeeeeeeeaaaaeeeeneeeees 51 4 3 8 Making Scheduled Backups ccccceeeceeeeeeeeeeeee ee aa aa eeeeeeeeeeeeaaaaeeeeeeeeeeeeaeaaeneeeeeeeeeaeaaes 51 4 4 Making Backups with a Distributed File System DFS or Storage Access Network SAN 52 This section explains the preparations you need for creating backups with MySQL Enterprise Backup the typical backup verify restore cycle and the different backup scenarios for using MySQL Enterprise Backup It also includes sample commands and outputs s
178. ess If you see that there is unused system capacity during a restore consider increasing the values for these options and testing whether doing so increases restore performance e When tuning and testing backup performance using a RAID storage configuration consider the combination of option settings read threads 3 process threads 6 write threads 3 Compare against the combination read threads 1 process threads 6 writ threads 1 69 Parallel Restore e When tuning and testing backup performance using a non RAID storage configuration consider the combination of option settings read threads 1 process threads 6 write threads l When you increase the values for any of the 3 threads options also increase the value of the limit memory option to give the extra threads enough memory to do their work e If the CPU is not too busy less than 80 CPU utilization increase the value of the process threads option e If the storage device that you are restoring from the source drive can handle more I O requests increase the value of the read threads option e If the storage device that you are restoring to the destination drive can handle more I O requests increase the value of the write threads option Depending on your operating system you can measure resource utilization using commands such as top iostat sar dtrace or a graphical performance monitor Do not increas
179. eter points to the right location on the verification server Edit the values for port socket and so on if you need to use different connection settings on the verification server 4 2 3 Restoring a Database at its Original Location To restore a MySQL instance from a backup Shut down the database server using commands such as mysqladmin shutdown e Use for example mysqibackup with the copy back and apply log command which makes the raw backup into a prepared backup by updating it to a consistent state and then copies the tables indexes metadata and any other required files back to their original locations as defined by the original MySQL configuration file For the different combinations of options that you can specify as part of this operation see Section 12 3 Restore Operations 32 Restoring a Database at its Original Location In the example below the single file backup created in the example given in Section 4 2 1 Backing Up an Entire MySQL Instance is restored using the copy back and apply log command Besides the usual connection parameters the following options are used in the command e defaults file supplies the configuration file backup my cnf which was created in the temporary directory you specified with backup dir when you created the single image backup see Section 4 2 2 Verifying a Backup for more explanations and is now at the location specified with the option
180. except executing it on a computer or modifying a private copy Propagation includes copying distribution with or without modification making available to the public and in some countries other activities as well To convey a work means any kind of propagation that enables other parties to make or receive copies Mere interaction with a user through a computer network with no transfer of a copy is not conveying An interactive user interface displays Appropriate Legal Notices to the extent that it includes a convenient and prominently visible feature that 1 displays an appropriate copyright notice and 2 tells the user that there is no warranty for the work except to the extent that warranties are provided that licensees may convey the work under this License and how to view a copy of this License If the interface presents a list of user commands or options such as a menu a prominent item in the list meets this criterion 1 Source Code The source code for a work means the preferred form of the work for making modifications to it Object code means any non source form of a work A Standard Interface means an interface that either is an official standard defined by a recognized standards body or in the case of interfaces specified for a particular programming language one that is widely used among developers working in that language The System Libraries of an executable work include anything other than the
181. f the CPU is not too busy less than 80 CPU utilization increase the value of the process threads option e If the storage device that you are backing up from the source drive can handle more I O requests increase the value of the read threads option e If the storage device that you are backing up to the destination drive can handle more I O requests increase the value of the write threads option Depending on your operating system you can measure resource utilization using commands such as top iostat sar dtrace or a graphical performance monitor Do not increase the number of read or write threads iowait once the system iowait value reaches approximately 20 66 MyISAM Considerations MyISAM Considerations A Important Although mysqlbackup backs up InnoDB tables without interrupting database use the final stage that copies non InnoDB files such as MyISAM tables and frm files temporarily puts the database into a read only state using the statement FLUSH TABLES WITH READ LOCK For best backup performance and minimal impact on database processing 1 Do not run long SELECT queries or other SQL statements at the time of the backup run 2 Keep your MyISAM tables relatively small and primarily for read only or read mostly work Then the locked phase at the end of a mysqibackup run is short maybe a few seconds and does not disturb the normal processing of mysqid much If the preceding
182. ff locking with the no locking or no connection option The only innodb and only innodb with frm options also prevent the locking step Because locking all tables could be problematic on a busy server you might use a combination of only innodb and suspend at end to back up only certain non InnoDB tables xec when locked utility argl arg2 Command Line Format xec when locked utility argl arg2 Permitted Values Type string You can use this option to run a script that backs up any information that is not included as part of the usual backup For example with xec when locked you can use mysqldump to back up tables from the MEMORY storage engine which are not on disk Set any variable you want to use within your script before you run mysqibackup In the following example the BACKUP_DIR environment variable is set to point to the current backup directory quotes are used for the argument of xec when locked to prevent premature expansion of the variable BACKUP_DIR On Unix or Linux systems export BACKUP_DIR path_to_backupdir mysqlbackup exec when locked mysqldump mydb t1 gt SBACKUP_DIR t1l sql other_options mysqlbackup_command Or on Windows systems set BACKUP_DIR path_to_backupdir mysqlbackup exec when locked mysqldump mydb t1 gt BACKUP_DIR t1 sql other_options mysqlbackup_command If the utility cannot be executed or returns a non zero exit status the whole backup
183. ffiliates reserve any and all rights to this documentation not expressly granted above xii Part Getting Started with MySQL Enterprise Backup Table of Contents 1 Introduction to MySQL Enterprise Backup ccceccceeeeeeeeeee ener eee teeeeeee ee ae aaeeteeeeeeeeeaeaaaaeeeeeeeeeeeaea 5 1 1 Types of BackUPS ianiai ha nt dae hia tee te en ei tad ee 5 1 2 The mysqlbackup Cent i aineina nerean ttnan teeter ee ee seca eda tees esse ease Saa a EUa aA rN ENAR 6 1 3 Overview of Backup Performance and Capacity Considerations 0 ccceceeeeeeeeeeeeeeeeeeeaeeaee 6 1 4 Files that Are Backed Up aroro cece cece cece ener eeeeee ee E eeeeaa ee A a E 7 1 5 Overview of Restoring a Database cccceceeeeeee ee eeeee cece tees ae aa eee eeeeeeeeeeaaeaeeeeeeeeeseaaaaenees 17 2 Installing MySQL Enterprise Backup cccceeceeeeeeeee cece ae ee ee eeee eres ee ae aa ea teeeeeeeeeaeaaaaeeeeeeeeeaeaaaaenees 19 3 What s New in MySQL Enterprise Backup 3 12 cccccccceceeeeeee cess ee aeeeeeeeeeeeeeseaaeaeeeeeeeeeeaeaaaaeeeeeess 21 Chapter 1 Introduction to MySQL Enterprise Backup Table of Contents Wel Types Of Backus eorr cncciaatenwediigcnedinancrecedadcacoeaccstescaaenadinanesecteuncasieenncaretacacaieeemeeeeeeaceanass 5 1 2 The Mysqlbackup CONE ovcroteseescvcaseevedesshe iana aa a a a a E aa aaa eae 6 1 3 Overview of Backup Performance and Capacity Considerations c cseeeeeeeeeeeee
184. file_path option it determines the actual file paths of the InnoDB data files inside the backup The value for the parameter is derived as follows If backup_innodb_data_home_dir is not specified its value will be backup dir datadir If backup_innodb_data_home_dir is an absolute path its value is used as is If backup_innodb_data_home_dir is a relative path the path is taken to be relative to that is underneath backup dir An empty string for backup_innodb_data_home_dir means the value of innodb_data_file_path is to be taken as an absolute path 108 Backup Repository Options This parameter is applicable only for backup operations during a restore the InnoDB data files are restored under the data directory specified by datadir unless another location is specified using the innodb_data_home_dir option during restore backup_innodb_data_file_path VALUE The InnoDB data file names and sizes Examples ibdatal 32M ibdata2 32M autoextend abs path ibdatal 32M autoextend innodb dir ibdatal 32M autoextend This parameter together with backup_innodb_data_home_dir determines where the InnoDB data files are stored within the backup repository Any file path specified with this option is taken to be relative to the value of the backup_innodb_data_home_dir option that is true even if the file path is specified in the form of an absolute path like abs path ibdatal 32M autoextend To specify truly absolute
185. fringed by some manner permitted by this License of making using or selling its contributor version but do not include claims that would be infringed only as a consequence of further modification of the contributor version For purposes of this definition control includes the right to grant patent sublicenses in a manner consistent with the requirements of this License Each contributor grants you a non exclusive worldwide royalty free patent license under the contributor s essential patent claims to make use sell offer for sale import and otherwise run modify and propagate the contents of its contributor version In the following three paragraphs a patent license is any express agreement or commitment however denominated not to enforce a patent such as an express permission to practice a patent or covenant not to sue for patent infringement To grant such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party If you convey a covered work knowingly relying on a patent license and the Corresponding Source of the work is not available for anyone to copy free of charge and under the terms of this License through a publicly available network server or other readily accessible means then you must either 1 cause the Corresponding Source to be so available or 2 arrange to deprive yourself of the benefit of the patent license for this particular work or
186. fter restoring table data from a backup The binary logging feature can be turned on and off although Oracle recommends always enabling it if you use replication or perform backups You can examine the contents of the binary log or replay those statements during replication or recovery by using the mysqlbinlog command For full information about the binary log see The Binary Log For MySQL configuration options related to the binary log see Binary Log Options and Variables For the MySQL Enterprise Backup product the file name of the binary log and the current position within the file are important details To record this information for the master server when taking a backup in a replication context you can specify the slave info option Prior to MySQL 5 0 a similar capability was available known as the update log In MySQL 5 0 and higher the binary log replaces the update log The binary log if enabled on the server is backed up by default See Also binlog relay log replication binlog An informal name for the binary log file For example you might see this abbreviation used in e mail messages or forum discussions See Also binary log C cold backup A backup taken while the database is shut down For busy applications and web sites this might not be practical and you might prefer a warm backup or a hot backup 174 See Also backup connection hot backup warm backup compression A technique that produces
187. g a validate or list image operation on an encrypted backup image 134 Cloud Storage Options The option cannot be used in a apply log backup and apply log of copy back operation For restoration using the copy back command the encrypted backup image has to be unpacked and decrypted first using the image to backup dir or extract command together with the decrypt option e key STRING Command Line Format key KEY Permitted Values Type string The symmetric key for encryption and decryption of a backup image It should be a 256 bit key encoded as a string of 64 hexadecimal digits See Chapter 8 Encryption for Backups on how to create a key The option is incompatible with the key file option e key file PATH Command Line Format key file FILE Permitted Values Type file name The pathname to file that contains a 256 bit key encoded as a string of 64 hexadecimal digits for encryption and decryption of a backup image The option is incompatible with the key option 13 14 Cloud Storage Options These options are for using cloud storage for single file operations See Section 4 3 5 3 Backing Up to Cloud Storage and Section 5 2 5 Restoring a Backup from Cloud Storage to a MySQL Server for more information and instructions on using cloud storage with MySQL Enterprise Backup e cloud service SERVICE Cloud service for data backup or rest
188. g option the skip relaylog option or both with your copy back or copy back and apply log command 146 Appendix B MySQL Enterprise Backup Limitations Table of Contents B 1 Limitations of MySQL Enterprise Backup ccceeeeeeeeeee cece eee eeeeeeeeee ee aa eae eeeeeeeeeeaaaaeeeeeeeeeeeeaaa 147 Please refer to the MySQL Enterprise Backup version history in Appendix D MySQL Enterprise Backup Release Notes for a list of fixed mysqibackup bugs B 1 Limitations of MySQL Enterprise Backup The group commit feature in MySQL 5 6 and higher changes the frequency of flush operations for the InnoDB redo log which could affect the point in time associated with the backup data from InnoDB tables See Section C 4 Compatibility Notes for Specific MySQL Versions for details In Linux Unix and OS X systems mysqlbackup does not record file ownership or permissions of the files that are backed up Upon restore these files might have different ownership for example being owned by root now rather than mysql They might also have different read write permissions for example being readable by anyone rather than just the file owner When planning your backup strategy survey the files in the MySQL data directory to ensure they have consistent owner and permission settings When executing a restore operation use an appropriate combination of su umask chown and chmod on the restored files to set up the same owners and privi
189. ge errors alerts and normal informational messages are always printed to standard error stream 12 2 Apply Log Operations These operations bring the backup files up to date with any changes to InnoDB tables that happened while the backup was in progress Although for convenience you can combine this operation with the initial backup using the backup and apply log command you must run the steps separately when performing incremental or compressed backups mysqlbackup STD OPTIONS limit memory MB uncompress backup dir PATH MESSAGE LOGGING OPTIONS PROGRESS REPORT OPTIONS apply log mysqlbackup STD OPTIONS incremental backup dir PATH backup dir PATH limit memory MB uncompress MESSAGE LOGGING OPTIONS PROGRESS REPORT OPTIONS apply incremental backup apply log Brings the InnoDB tables in the backup up to date including any changes made to the data while the backup was running 88 Restore Operations e apply incremental backup Brings the backup up to date using the data from an incremental backup Example 12 1 Apply Log to Full Backup mysqlbackup backup dir path to backup apply log It reads the backup my cnf file inside backup dir to understand the backup The my cnf default files have no effect other than supplying the 1 imit memory MB value which limits usage of memory while doing the apply log operation Because the apply log operat
190. ge from cloud storage to dat adir on the server use the cloud storage options and the backup dir option to specify the temporary directory into which the image will be extracted Example 5 12 Restoring a Single file Backup from Amazon S3 to a MySQL Server mysqlbackup defaults file bkups backupdir backupmy cnf cloud service s3 cloud aws region lt aws region gt cloud access key id lt aws access key id gt cloud secret access key lt aws secret access key gt cloud bucket lt s3 bucket name gt cloud object key lt aws object key gt backup dir home user dba s3backuptmpdir datadir home user dba datadir backup image copy back and apply log Example 5 13 Restoring a Single file Backup from an OpenStack Object Storage to a MySQL Server mysqlbackup defaults file bkups backupdir backupmy cnf cloud service openstack cloud container lt swift container gt cloud user id lt keystone user gt cloud password lt keystone password gt cloud region lt keystone region gt cloud tenant lt keystone tenant gt cloud identity url lt keystone url gt cloud object image_800 mbi backup dir home user dba swiftbackuptmpdir datadir home user dba datadir backup image copy back and apply log 5 3 Point in Time Recovery from a Hot Backup Using MySQL Enterprise Backup and the binary log 11 files included by default in the
191. gfile file 7 ibd file 7 177 ibdata file 7 177 ibreset command 76 bz file 7 ibz file 7 177 ib_logfile file 7 image 178 image to backup dir option 94 121 121 image_files xml file 7 78 include 178 include option 40 119 include tables option 115 incremental backup 6 113 178 incremental option 113 incremental backup dir option 115 incremental base option 114 incremental with redo log only option 113 InnoDB 178 InnoDB tables 5 7 85 85 compressed backup feature 39 incremental backup feature 35 installing MySQL Enterprise Backup 19 instance 178 K key option 135 key file option 135 L limit memory option 126 list image option 94 121 locking 178 log 7 88 178 log bin index 128 logical backup 6 178 logs of backup operations 76 LSN 35 113 179 manifest 7 78 123 179 master 63 179 master info file 129 media management software 179 media management software MMS products 73 MEMORY tables 51 message logging 130 meta directory 7 MMS products 73 monitoring backup jobs 75 MRG file 179 my cnf 179 my ini 179 188 MYD file 7 MYD file 179 MYI file 7 MYI file 179 MyISAM 179 MyISAM tables 85 MySQL Enterprise Backup 180 MySQL Enterprise Monitor 75 mysqlbackup 85 180 and media management software MMS products 73 configuration options 139 examples 34 files produced 7 modes of oper
192. gt keyfile cat keyfile 6ald325e6ef0577 3400b7cd624ae574 518 6d0da2eeb946895de418297ed75b The encryption function uses MySQL Enterprise Backup s own encryption format which means decryption is possible only by using MySQL Enterprise Backup For Unix like operating systems different magic numbers are used to identify encrypted and unencrypted backup files For examples you can add these lines to the etc magic file of your operating system 0 string MBackuP n MySQL Enterprise Backup backup image 0 string MebEncR n MySQL Enterprise Backup encrypted backup The file command can then be used to identify the file types file backups imagel backups image2 backups imagel MySQL Enterprise Backup backup image backups image2 MySQL Enterprise Backup encrypted backup The command options used for encryption and decryption are encrypt decrypt key and key file These options can be used with various operations on backup images See Section 13 13 Encryption Options for details The following is a sample command for creating an encrypted backup mysqlbackup backup image backups image enc encrypt key 23D987F3A047B475C900127148F 9E0394857983645192874A2B3049570C12A34 backup dir var tmp backup backup to image To use a key file for the same task mysqlbackup backup image backups image enc encrypt key file meb key backup dir var tmp backup backup to image 71 To decrypt a backup when ext
193. h backup dir See the description for backup dir for details The location specified by incremental backup dir is the same location you will specify with incremental base when you use that option for a subsequent incremental backup 13 8 Partial Backup and Restore Options Note E Since MySQL Enterprise Backup 3 10 the two options include tables and xclude tables have been introduced These were intended for replacing the older options of include databases databases list file and only innodb with frm which are incompatible with the new options and will be deprecated in future releases For references purpose we have included information on the older options at the end of this section in Legacy Partial Backup Options To select specific data to be backed up or restored use the partial backup and restore options described in this section For an overview of partial backup and usage examples on the following options see Section 4 3 4 Making a Partial Backup See also Section 5 2 4 Restoring Backups Created with the use tts Option on selective restore of tables from a backup e include tables REGEXP Command Line Format include tables REGEXP Permitted Values Type string Include for backup or restoration only those tables both innodb and non innodb whose fully qualified names in the form of db_name table_name match the regular expression REGEX
194. has 10 corrupt pages mysqlbackup failed with errors This is a sample output for a successful validation for a compressed backup directory mysqlbackup INFO backups backup dir datadir tpch tabnorm5 ibz Validated mysqlbackup INFO backups backup dir datadir tpch tabnorm6 ibz Validated mysqlbackup INFO backups backup dir datadir tpch tabnorm7 ibz Validated mysqlbackup INFO backups backup dir datadir tpch tabnorm8 ibz Validated mysqlbackup INFO backups backup dir datadir tpch tabnorm9 ibz Validated 92 Single File Backup Operations mysqlbackup INFO backups backup dir datadir tpch tabrowformat ibz Validated 140219 11 22 45 mysqlbackup INFO Validate backup directory operation completed successfully 12 5 Single File Backup Operations To simplify transfer and management of backup data you can keep each backup in a single file the backup image The backup to image command performs a backup directly to a single file and there are the commands for packing an existing backup into a single file or unpacking a single file backup to a full backup directory structure These and other commands for working with single file backups are explained below For usage examples see Section 4 3 5 Making a Single File Backup mysqlbackup STD OPTIONS CONNECTION OPTIONS SERVER REPOST TORY OPTIONS BACKUP REPOSITORY OPTIONS METADATA OPTIONS COMPRESSTON OPTIONS SPEC IAL BACKUP TYPES
195. he backup image with the backup image option also supply with the backup dir option the location of a folder that will be used for storing temporary files produced during the restoration process e To restore an incremental backup directory assuming the full backup on which the incremental backup was based has already been restored e Include the incremental option in the command line e Use either the backup dir or incremental backup dir option to specify the incremental backup directory e To restore a single file incremental backup besides specifying the location of the incremental backup image with the backup image option also supply with the backup dir or incremental backup dir option the location of a folder that will be used for storing temporary files produced during the restoration process e To restore a backup created with the use tts option See the general requirements described in Section 5 2 4 Restoring Backups Created with the use tts Option e When restoring an image backup created with the option setting use tts with minimum locking also supply with the backup dir option the location of a folder that will be used for extracting temporarily all tables in the backup and for performing an apply log operation to make the data up to date before restoring them to the server s data directory e When restoring a backup directory created with the option use tts an
196. her than using the with timestamp option mysqlbackup defaults file home pekka my cnf incremental incremental base dir incr backup wednesday incremental backup dir incr backup thursday backup many lines of output mysqlbackup Backup created in directory incr backup thursday mysqlbackup start_lsn 2654255717 mysqlbackup incremental_base_lsn 2666733462 mysqlbackup end_lsn 2666736714 101208 17 14 58 mysqlbackup mysqlbackup completed OK Note that if your last backup was a single file instead of a directory backup you can still use incremental base by specifying for dir directory_path the location of the temporary directory you supplied with the backup dir option during the full backup As an alternative to specifying incremental base dir directory_path you Can tell mysqlbackup to query the end_isn value from the last successful backup as recorded in the backup_history table on the server using incremental base history last_backup this required that the last backup was made with mysqlbackup connected to the server You can also use the start 1sn option to specify where the incremental backup should start You have to record the LSN of the previous backup reported by mysqibackup at the end of the backup mysqlbackup Was able to parse the log up to lsn 2654255716 The number is also recorded in the meta backup_variables txt file in the folder specified by
197. hout locking the MySQL instance And because those tables are not expected to be changed before the backup is finished redo logs undo logs and system table spaces are not backed up by mysqlbackup in this phase 2 Normal phase In this second phase tables that are not backed up in the first phase referred to as the busy tables below are being backed up in a manner similar to how they are processed in an ordinary backup the InnoDB files are copied first and then other relevant files and copied or processed with the MySQL instance locked The redo logs undo logs and the system tablespace are also backed up in this phase An optimistic backup occurs whenever the opt imistic time or optimistic busy tables option is used For how to use the options see detailed descriptions for them in Section 13 10 Performance Scalability Capacity Options If as expected the inactive tables identified by the options are not changed a lot during the backup the overall backup time time for the backup operation plus time for the apply log operation can be reduced significantly comparing with an ordinary backup because the apply log operation will be much faster However if it turns out that the inactive tables identified are modified a lot during the backup process benefits of performing an optimistic back up will become limited and in the worst case an optimistic backup might actually take longer to perform and for a single file backup the
198. howing you how to use the mysqlbackup client in different situations 4 1 Before the First Backup This section outlines some of the preparations needed before you can start working with MySQL Enterprise Backup 4 1 1 Collect Database Information Before backing up a particular database server for the first time gather some information and use it to make some planning decisions as outlined in the following table Table 4 1 Information Needed to Back Up a Database Information to Gather Where to Find It How Used Path to MySQL configuration file Default system locations This is the preferred way to hardcoded application default convey database configuration locations or from the information to mysqlbackup defaults file option in the using the defaults file mysqld startup script option When connection and data layout information is available from the configuration file you can skip most of the other choices listed below MySQL port MySQL configuration file or Used to connect to the database mysqld startup script instance during backup 27 Collect Database Information Information to Gather Where to Find It How Used operations Specified via the port option of mysqlbackup port is not needed if available from MySQL configuration file Not needed when doing a cold offline backup which works directly on the files using OS level file permissions Path to MySQL da
199. ificantly improved as explained in Optimizing InnoDB Configuration Variables With those releases you can make your redo log files bigger if that helps your backup strategy and your database workload As discussed later there are a number of reasons why you might prefer to run with the setting innodb_file_per_table 1 Parallel Backup mysqlbackup can take advantage of modern multicore CPUs and operating system threads to perform backup operations in parallel See Section 13 10 Performance Scalability Capacity Options for the options to control how many threads are used for different aspects of the backup process If you see that there is unused system capacity during backups consider increasing the values for these options and testing whether doing so increases backup performance e When tuning and testing backup performance using a RAID storage configuration consider the combination of option settings read threads 3 process threads 6 write threads 3 Compare against the combination read threads 1 process threads 6 writ threads 1 e When tuning and testing backup performance using a non RAID storage configuration consider the combination of option settings read threads 1 process threads 6 write threads 1l When you increase the values for any of the 3 threads options also increase the value of the limit memory option to give the extra threads enough memory to do their work e I
200. included in a previous backup suspend at end trace 103 Pauses the mysqlbackup command when the backup procedure is close to ending Trace level of messages by mysqlbackup uncompress Uncompress the compressed backup before applying log use tts Enable selective backup of InnoDB tables using transportable tablespaces TTS user Database user name to connect verbose Print more verbose information version Display version information with timestamp Create a subdirectory underneath the backup directory with a name formed from the timestamp of the backup operation write threads 13 1 Standard Options Specifies the number of write threads for the backup operation The standard options are options of a general nature or options that are not classified under any other specific option group Here is a list of the standard options e The following standard options also exist for the mysql command Full descriptions for these options can be found in the MySQL reference manual accessible through e g Server Option and Variable Reference These options must be specified ahead of any other mysqibackup options including the rest of the standard options lt primt detaules jney elSecsho lies Print the program argument list and exit Don t read default options from any option file defaults file PATH Only read default options from the given fil
201. influence the physical representation of records on disk such as changing column names or default column values When statement based binary log format is used on the MySQL server which is the default behavior if you take a backup when there are temporary tables in the database and they have been used to update or insert into normal tables during the backup application of the MySQL binary log to a backup could then failthat is you might not be able to roll forward the backup to a particular point in time using the MySQL binary log This is because temporary tables are not copied to the backup as the physical filenames sql1 frm do not correspond to the logical table names that MySQL writes to the binary log To avoid the problem use row based or mixed format for the binary log by setting the value for the binlog format option to ROW or MIXED on the server 147 Limitations of MySQL Enterprise Backup The engines column in the mysql backup_history table does not correctly reflect the storage engines of the backed up databases Hot backups for large databases with heavy writing workloads say in the order of gigabytes per minute can take a very long time to complete due to the huge redo log files that are generated on the server when the backup is in progress And if the redo log files grow faster than they can be processed by mysqlbackup the backup operation can actually fail when mysqlbackup cannot catch up with th
202. ing backed up in a manner similar to how they are processed in an ordinary backup the InnoDB files are copied first and then other relevant files and copied or processed with the MySQL instance locked The redo logs undo logs and the system tablespace are also backed up in this phase See Section 4 3 6 Making an Optimistic Backup for details Oracle Secure Backup An Oracle product for managing backup media and so classified as media management software MMS Abbreviated OSB For MySQL Enterprise Backup OSB is typically used to manage tape backups See Also backup media management software OSB OSB Abbreviation for Oracle Secure Backup a media management software product MMS See Also Oracle Secure Backup P par file A file containing partition definitions Files with this extension are always included in backups produced by the mysqlbackup command of the MySQL Enterprise Backup product parallel backup The default processing mode in MySQL Enterprise Backup 3 8 and higher employing multiple threads for different classes of internal operations read process and write See Section 1 3 Overview of Backup Performance and Capacity Considerations for an overview Section 13 10 Performance Scalability Capacity Options for the relevant mysqlbackup options and Chapter 7 Performance Considerations for MySQL Enterprise Backup for performance guidelines and tips partial backup A backup that contains some of the
203. ing data loss for you MySQL server This section discusses some simple means for setting up a schedule for running MySQL Enterprise Backup For Linux and other Unix like platforms you can set up a cron job on your system for scheduled backups There are two types of cron jobs to set up a user cron job which is owned and run by a particular user do the following e Log on as the user who runs MySQL Enterprise Backup and use the following command to invoke an editor for creating or modifying a crontab shell gt crontab e e In the editor add an entry similar to the following one to the crontab and then save your changes daily path to mysqlbackup mysqlbackup uroot backup dir path to backup folder cronbackups with ti This crontab entries invokes mysqlbackup to create a backup under the cronbackups directory at 00 00 00 everyday Outputs from the stderr and stdout streams are redirected to dev null so they will not invoke other actions on the part of the Cron server for example email notifications to the user To set up a system cron job which is owned and run by root create a file under the etc cron d folder and put into it a similar crontab entry as the one above adding the user root in the following example before the mysqlbackup command daily root path to mysqlbackup mysqlbackup uroot backup dir path to backup folder cronbackups with Check your platform s documentation on further details on the differen
204. ing disk space and I O resources e Data consistency of the tables is managed by MySQL Enterprise Backup However the option has the following limitations e Supports only MySQL version 5 6 and after as earlier versions of MySQL do not support TTS e Can only backup tables that are stored in their own individual tablespaces i e tables created with the innodb_file_per_table option enabled e Cannot back up partitioned tables e Cannot restore tables selectively from the backup Cannot be used for incremental backups There are two possible values for the option e with minimum locking Hot copies of the selected tables are backed up and the tables are then locked in read only mode while the redo log with only the portion containing the relevant changes made after the hot backup is being included in the backup Any tables created during the locking phase are ignored e with full locking The selected tables are locked in read only mode while they are being backed up The redo log is not included in the backup Any tables created during the locking phase are ignored Default back up with minimum locking There are some special requirements for restoring backups created with the use tts option see the explanations in Section 5 2 Performing a Restore Operation for details 13 9 Single File Backup Options These options are associated with single file backups You use them in combination with the mysqlbackup command
205. innodb_log_files_in_group 97 Format Description Introduced s Backup directory for InnoDB log files backup_innodb_log_group_home_dir backup_innodb_page_size The page size for all InnoDB tablespaces in a MySQL instance The relative or absolute directory path where InnoDB backup_innodb_undo_directory creates separate tablespaces for the undo logs backup_innodb_undo_logs Number of rollback segments in the system tablespace that InnoDB uses within a transaction The number of tablespace files that the undo logs are backup_innodb_undo_tablespac divided between when a non zero innodb_undo_logs setting is used character sets dir Directory for character set files cloud access key id AWS access key ID for logging onto Amazon S3 cloud aws region Region for Amazon Web Services that mysqlbackup access for S3 cloud bucket The storage bucket on Amazon S3 for the backup image cloud container 136 The Swift container for the backup image 3 12 0 cloud identity url 137 The URL of the Keystone identity service 3 12 0 cloud object 136 The Swift object for the backup image 3 12 0 cloud object key The Amazon S3 object key for the backup image cloud password 136 Password for user specified by cloud user id 3 12 0 cloud proxy Proxy address and port number for overriding the environment s default proxy settings for accessing cloud service
206. ion does not apply to incremental backups no incremental backup dir is needed for this operation You can also perform apply log and copy back which restores the prepared backup together with a single copy back and apply log command 12 3 Restore Operations The restore operations restores the data files from a backup to their original locations on the database server or to other desired locations The MySQL instance must be shut down first before a restore operation except for backups created using transportable tablespace TTS The options datadir innodb_log_files_in_group and innodb_log_file_size must be specified either in the target server s configuration file in the file specified by the defaults file option or as command line options For usage examples see Chapter 5 Recovering or Restoring a Database mysqlbackup STD OPTIONS SERVER REPOST TORY OPTIONS backup dir PATH MESSAGE LOGGING OPTIONS PARTIAL BACKUP RESTORE OPTIONS PROGRES S REPORT OPTIONS CLOUD STORAGE OPTIONS copy back mysqlbackup STD OPTIONS SERVER REPOSLT TORY OPTIONS backup image IMAGE backup dir PATH MESSAGE LOGGING OPTIONS PARTIAL BACKUP RESTORE OPTIONS PROGRESS REPORT OPTIONS ENCRYPTION OPTIONS CLOUD STORAGE OPTIONS copy back and apply log copy back Restores files from a backup to their original locations within the MySQL server Some clean up efforts on
207. ion of this License for any work from that copyright holder and you cure the violation prior to 30 days after your receipt of the notice Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License If your rights have been terminated and not permanently reinstated you do not qualify to receive new licenses for the same material under section 10 9 Acceptance Not Required for Having Copies You are not required to accept this License in order to receive or run a copy of the Program Ancillary propagation of a covered work occurring solely as a consequence of using peer to peer transmission to receive a copy likewise does not require acceptance However nothing other than this License grants you permission to propagate or modify any covered work These actions infringe copyright if you do not accept this License Therefore by modifying or propagating a covered work you indicate your acceptance of this License to do so 10 Automatic Licensing of Downstream Recipients Each time you convey a covered work the recipient automatically receives a license from the original licensors to run modify and propagate that work subject to this License You are not responsible for enforcing compliance by third parties with this License An entity tratsaction is 4 transaction transferring control of an organization or substantially all assets of one
208. irectory datadir directory A subdirectory that stores the data files and database subdirectories from the original MySQL instance Created under the backup directory by mysqlbackup 10 Files that Are Backed Up File Name Pattern or Extension Relation to Original Data Files Notes binary log files Binary log files from the server which are included in a backup by default except when the backup is created with the use tts option They allow a snapshot of the server to be taken so a server can be cloned to its exact state Using a full backup as a basis the binary log files that are included with an incremental backup can be used for a point in time recovery PITR which restores a database to its state at a certain point in time after the last full backup See Section 5 3 Point in Time Recovery from a Hot Backup for details Saved under the datadir directory under the backup directory Use the skip binlog option to exclude binary logs in the backup For MySQL 5 5 and earlier as well as all offline backups use the log bin index option to specify the absolute path of the index file on the MySQL server that lists all the used binary log files if it is different from the default value of the option for mysqibackup to find the binary log files and include them in the backups The index file itself with the locations of the binary log files properl
209. is requires a connection to the MySQL server and therefore only works when backing up a running MySQL instance mysqlbackup first adds one row of the progress report to the mysql backup_progress table and then updates the row afterwards with the latest progress indicator The progress indicator is stored in the current_status column of the table If the backup locks the MySQL instance for example by issuing a FLUSH TABLES WITH READ LOCK statement the progress reports are not delivered to the mysql backup_progress table until the MySQL instance is unlocked variable Progress indicators are sent to the system variable backup_progress Server Users need to create their own plugin to define the variable See The Warning The system variable backup_progress is not yet defined for the MySQL MySQL Plugin API for more information on user plugins When there is no argument specified for show progress progress indicators are sent to stderr Progress can be reported to multiple destinations by specifying the show progress option several times on the command line For example the following command line reports progress of the backup command to stderr and to a file called meb_output mysqlbackup show progress show progress file meb_output backup dir full backup backup The progress indicators are short strings that indicate how far the execution of a mysqlbackup operation has progressed A progress indicator consist
210. ise Backup containing a minimal set of configuration parameters This file records the settings that apply to this backup data Subsequent operations such as the apply process read options from this file to determine how the backup data is structured This file always has the extension cnf rather than cnf on Unix like systems and ini on Windows systems See Also apply configuration file Barracuda The code name for an InnoDB file format that supports compression for table data This file format was first introduced in the InnoDB Plugin It supports the compressed row format that enables InnoDB table compression and the dynamic row format that improves the storage layout for BLOB and large text columns You can select it through the innodb_file format option Because the InnoDB system tablespace is stored in the original Antelope file format to use the Barracuda file format you must also enable the file per table setting which puts newly created tables in their own tablespaces separate from the system tablespace The MySQL Enterprise Backup product version 3 5 and above supports backing up tablespaces that use the Barracuda file format See Also Antelope file format MySQL Enterprise Backup row format system tablespace binary log A file containing a record of all statements that attempt to change table data These statements can be replayed to bring slave servers up to date in a replication scenario or to bring a database up to date a
211. ivalent file on a remote system You can either store the single file backup directly on the remote system or invoke mysqlbackup with the image to backup dir option on the other end to reproduce the directory structure of a regular backup Example 4 15 Single File Backup to a Remote Host The following command streams the backup as a single file output to a remote host where it may be saved directly to a tape device backup dir tmp designates the directory for storing temporary files rather than the final output file mysqlbackup backup image backup dir tmp backup to image ssh user host command argl arg2 47 Making a Single File Backup For simplicity all the connection and other necessary options are assumed to be specified in the default configuration file To have the desired operations run on the remote system substitute the combination of command device and so on that you use as part of your normal archiving procedure such as dd or tar Example 4 16 Single file Backup to a Remote MySQL Server The following command streams the backup as a single backup file to be restored on a remote MySQL server mysqlbackup backup dir backup backup image compress backup to image ssh lt user name gt lt remote host name gt mysqlbackup backup dir backup_tmp datadir data innodb_log_group_home_dir innodb_log_files_in_group lt innodb_log_files_in_group_of_backedup_server gt N in
212. ive Your goal is to keep the database system and associated applications and web sites operating and responsive while the backup is in progress Hot backups are performed while the database is running This type of backup does not block normal database operations It captures even changes that occur while the backup is happening For these reasons hot backups are desirable when your database grows up when the data is large enough that the backup takes significant time and when your data is important enough to your business so that you must capture every last change without taking your application web site or web service offline MySQL Enterprise Backup does a hot backup of all InnoDB tables MyISAM and other non InnoDB tables are backed up last using the warm backup technique the database continues to run but the system is ina read only state during that phase of the backup You can also perform cold backups while the database is stopped To avoid service disruption you would typically perform such a backup from a replication slave which can be stopped without taking down the entire application or web site Points to Remember Points to Remember To back up as much data as possible during the hot backup phase you can designate InnoDB as the default storage engine for new tables or convert existing tables to use the InnoDB storage engine In MySQL 5 5 and higher InnoDB is now the default storage engine for new tables
213. ke databases and databases list file can be used Important A This option does not filter the rm files associated with InnoDB tables meaning that regardless of the option s value all the frm files for all InnoDB tables are always backed up unless they are excluded by other options Those frm files for InnoDB tables that are not backed up should be deleted before the database backup is restored See Making a Partial Backup with the Legacy Options for details e databases LIST Specifies the list of non InnoDB tables to back up The argument specifies a space separated list of database or table names of the following form db_name table_name db_namei table_namei If the specified values do not match any database or table then no non InnoDB data files are backed up See Making a Partial Backup with the Legacy Options 45 for details By default all non InnoDB tables from all databases are backed up 119 Legacy Partial Backup Options databases or tables it specifies To filter InnoDB data files use the include option instead Note N The option has no filtering effects on the InnoDB data files iba files for the e databases list file PATH Specifies the pathname of a file that lists the non InnoDB tables to be backed up The file contains entries for databases or fully qualified table names separated by newline or space The format of the entries is the same as for the databases o
214. kup image var my mbi extract Example 4 11 Extract Single File Backup into a Backup Directory This command behaves like the image to backup dir option by extracting all contents of a single file backup into the backup dir directory mysqlbackup backup image var my mbi backup dir var backup extract Example 4 12 Selective Extract of Single File The following command extracts the single file meta comments txt from the backup image my mbi into the local path meta comments txt mysqlbackup backup image var my mbi src entry meta comments txt extract The following command extracts the meta comments txt file from the backup image my mbi into a specified path tmp mycomments txt by using the dst entry option 46 Making a Single File Backup mysqlbackup backup image var my mbi src entry meta comments txt dst entry tmp mycomments txt extract The following command dumps the contents of meta comments txt which is inside the single file backup my mbi to standard output mysqlbackup backup image var my mbi src entry meta comments txt dst entry extract Example 4 13 Selective Extract of Single Directory The following command extracts a single directory meta from the backup image my mbi into a local file system path meta All contents in the meta directory are extracted including any subdirectories mysqlbackup backup image backup my mbi src entry meta extract Th
215. kups backup_history Table Each row in the backup_history table records the details of one completed backup job produced by mysqlbackup command The backup_history table has the following columns backup_id e tool_name start_time e end_time binlog_pos binlog_file compression_level engines innodb_data_file_path e innodb_file_ format start_isn e end_isn backup_type backup_format mysql_data_dir 77 Using the MySQL Enterprise Backup Manifest e innodb_data_home_dir innodb_log_group_home_dir innodb_log_files_in_group innodb_log_file_size e backup_destination e lock_time exit_state last_error e last_error_code Use the end_isn value to automate operations related to incremental backups When you take a full or incremental backup you specify the end LSN from that backup as the starting LSN for the next incremental backup Use the values that correspond to backup related configuration settings such as mysql_data_dir innodb_data_home_dir and backup_dest ination to confirm that the backups are using the right source and destination directories Use the values exit_state last_error and last_error_code to evaluate the success or failure of each backup If last_error is NO_ERROR the backup operation was successful In case of any errors you can retrieve the full list of errors for that backup operation from the backup_progress table 10 5 Usi
216. l backup makes restore faster or postponing it until right before the restore makes backup faster In an emergency restore performance is the most important consideration Thus the more crucial the data is the more important it is to run the apply log phase immediately after the backup Either combine the backup and apply log phases on the same server by specifying the backup and apply 1log option or perform the fast initial backup transfer the backup data to another server and then perform the apply log phase using one of the options from Section 12 2 Apply Log Operations 7 2 Optimizing Restore Performance This section describes the performance considerations for restoring a database with MySQL Enterprise Backup This subject is important because The restore operation is the phase of the backup restore cycle that tends to vary substantially between different backup methods For example backup performance might be acceptable using mysqldump but mysqldump typically takes much longer than MySQL Enterprise Backup for a restore operation e The restore operation is often performed during an emergency where it is critical to minimize the downtime of the application or web site 68 Restoring Different Classes of Backup Data The restore operation is always performed with the database server shut down e The restore operation is mainly dependent on low level considerations such as I O and network speed for transf
217. l Backup Using both the opt imistic busy tables and optimistic time Options a siexc neuen cennnsiccleeaiiended eatvvanaahicuseenseyebeanusleeys iaee a RE EnA desapedecaed aedeleatia dy satetedntinedeeaadated 51 5 1 Applying the Log to a BaCkup ccccceeeeceeceeeeeeeeee ee ae eae te aa aa a aaa aa Ta TEn 54 5 2 Applying the Log to a Compressed Backup ccccccceeeeeeeeeeeeeeceaaeeeeeeeeeeeaeaaeaeeeeeeeeeeaeaaaaeeeeeees 54 5 3 Applying an Incremental Backup to a Full Backup cccceeeeeeeeeeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaeaaeeeeeseeeees 54 5 4 Shutting Down and Restoring a Database 0 ccccceeeeeceeeeeeeee tees ee aaeeeeeeeeeeeeseaaeaeeeeeeeeeeaeaaaaeeees 55 5 5 Restoring a Backup Directory using copy back and apply 1l0g ceseeeeceeeecneeeeeeeeeeeeesaeeeeaeeeneeeeed 55 5 6 Restoring a Single file Backup using copy back and apply LOG ceecessececcseeeceeeneeeeeeaeeeeeeeaaeeeeees 55 5 7 Restoring a Compressed Backup ccceeeceeceeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaaaeeeeeeeeeeeeaeaaaeeeseeeeeeaeaaeaees 56 5 8 Restoring an Encrypted Backup Image ceeeeceeeeeeeecneeeeeeaaeeeeeeaaeeeeeeaaeeeeeeaaeeeeeeaaeeeeeaaeeeeeeaaaeees 56 5 9 Restoring an Incremental Backup Image ceeeeeeeneeeee eee eeeeee ease eeee cae eeeeaaeeeeeeaaeeeeeeaaeeeeeaaeeeees 56 5 10 Restoring Selected Tables from a TTS Backup ccccccccceeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaaeeeeseeeeeeaeaaenees 57 5 11 Restoring and R
218. ld not allow patents to restrict development and use of software on general purpose computers but in those that do we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary To prevent this the GPL assures that patents cannot be used to render the program non free 154 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 The precise terms and conditions for copying distribution and modification follow TERMS AND CONDITIONS 0 Definitions This License refers to version 3 of the GNU General Public License Copyright also means copyright like laws that apply to other kinds of works such as semiconductor masks The Program refers to any copyrightable work licensed under this License Each licensee is addressed as you Licensees and recipients may be individuals or organizations To modify a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission other than the making of an exact copy The resulting work is called a modified version of the earlier work or a work based on the earlier work A covered work means either the unmodified Program or a work based on the Program To propagate a work means to do anything with it that without permission would make you directly or secondarily liable for infringement under applicable copyright law
219. leges as on the original files In some cases backups of non transactional tables such as My 1 SAM tables could contain additional uncommitted data If autocommit is turned off and both TnnoDB tables and non transactional tables are modified within the same transaction data can be written to the non transactional table before the binary log position is updated The binary log position is updated when the transaction is committed but the non transactional data is written immediately If the backup occurs while such a transaction is open the backup data contains the updates made to the non transactional table If the mysqlbackup process is interrupted by for example a Unix kill 9 command a FLUSH TABLES WITH READ LOCK operation might remain running In this case use the KILL QUERY statement from the mysql command line to kill the FLUSH TABLES WITH READ LOCK statement This issue is more likely to occur if the FLUSH TABLES operation is stalled by a long running query or transaction Refer to Section 7 1 Optimizing Backup Performance for guidelines about backup timing and performance Do not run the DDL operations ALTER TABLE TRUNCATE TABLE OPTIMIZE TABLE REPAIR TABLE Of RESTORE TABLE while a backup operation is going on The resulting backup might become corrupted The only ALTER TABLE operations that can be safely run in parallel with a backup are those that do not
220. lemented with the RE2 regular expression library The backup directory produced contains a backup log file and copies of InnoDB data files IMPORTANT Although mysqibackup supports taking partial backups be careful when restoring a database from a partial backup mysqibackup copies also the frm files of those tables that are not included in the backup except when you do partial backups using for example the databases option If you use mysql backup with the include option before restoring the database delete from the backup data the frm files for any tables that are not included in the backup IMPORTANT Because the InnoDB system tablespace holds metadata about InnoDB tables from all databases in an instance restoring a partial backup on a server that includes other databases could cause the system to lose track of those InnoDB tables in other databases Always restore partial backups on a fresh MySQL server instance without any other InnoDB tables that you want to preserve The only innodb and only innodb with frm options back up InnoDB tables only skipping those of other storage engines You might also use them together with the include option to make selective backup of InnoDB tables while excluding all other files created by other storage engines Example 4 1 Making an Uncompressed Partial Backup of InnoDB Tables In this example we have configured MySQL so that some InnoDB tables have their own tablespaces We mak
221. ll backup see Section 4 2 1 Backing Up an Entire MySQL Instance This section outlines some of the things to consider when deciding on a strategy for creating full backups As we shall see factors like speed capacity and convenience are all relevant for your decisions 34 Making a Differential or Incremental Backup Options on Command Line or in Configuration File For clarity the examples in this manual often show some of the command line options that are used with the mysqlbackup commands For convenience and consistency you can include those options that remain unchanged for most backup jobs into the mysqlbackup section of the MySQL configuration file that you supply to mysqlbackup mysqlbackup also picks up the options from the mysqld section if they are present there Putting the options into a configuration file can simplify backup administration for you for example putting port information into a configuration file you can avoid the need to edit your backup scripts each time the database instance switches to a different port See Chapter 14 Configuration Files and Parameters for details about the use of configuration files Output in Single Directory or Timestamped Subdirectories For convenience the with timestamp option creates uniquely named subdirectories under the backup directory to hold the output from each backup job The timestamped subdirectories make it simpler to establish retention periods a
222. llowing easy removal and archiving of backup data that has passed a certain age If you do use a single backup directory that is if you omit the with timestamp option either specify a new unique directory name for each backup job or specify the force 103 option to overwrite existing backup files For incremental backups that uses the incremental base option to specify the directory containing the previous backup in order to make the directory names predictable you might prefer to not use the with timestamp option and generate a sequence of directory names with your backup script instead Always Full Backup or Full Backup plus Incremental Backups If your InnoDB data volume is small or if your database is so busy that a high percentage of data changes between backups you might want to run a full backup each time However you can usually save time and storage space by running periodic full backups and then several incremental backups in between them as described in Section 4 3 2 Making a Differential or Incremental Backup Use Compression or Not Creating a compressed backup can save you considerable storage space and reduce I O usage significantly And with the LZ4 compression method introduced since release 3 10 the overhead for processing compression is quite low In cases where database backups are moving from a faster disk system where the active database files sit to a possibly slower storage compres
223. locations by the target server InnoDB Data Data managed by the InnoDB storage engine is always backed up The primary InnoDB related data files that are backed up include the ibdata files which represent the system tablespace and possibly the data for some user tables any ibd files which contains data from user tables created with the file per table setting enabled and the data extracted from the ib_logfile files the redo log information representing changes that occur while the backup is running which is stored in a new backup file ibbackup_logfile If you use the compressed backup feature the ibd files are renamed in their compressed form to ibz files The files as they are originally copied form a raw backup that requires further processing before it is ready to be restored You then run the apply step which updates the backup files based on the changes recorded in the ibbackup_logfile file producing a prepared backup At this point the backup data corresponds to a single point in time The files are now ready to be restored to their original location or for some other use such as testing reporting or deployment as a replication slave To restore InnoDB tables to their original state you must also have the corresponding frm files along with the backup data Otherwise the table definitions could be missing or outdated if someone has run ALTER TABLE Of DROP TABLE statements since the backup By default
224. lowing format MEB_timestamp_operation 1log where operationis the mysqlbackup operation that was run e g backup apply log etc and timestamp is the date and time at which the operation was run Here are some examples of names for the log files MEB_2013 06 24 16 32 43 backup log Mine ZAOLS OG 2E lil O ile sysjeulay_lexey ler Mina 2013 06 24 nnO OS 0ibmlarstmalmace shaq The following options control the message logging function skip messages logdir Skip message logging Logging is turned on by default except for the 1ist image and validate operations see the description for the messages logdir option for details and it is turned off by this option e messages logdir path Command Line Format messages logdir PATH Permitted Values Type directory name Default backup_dir meta Specifies the path name of an existing directory for storing the message log If the specified directory does not exist message logging fails and returns an error message When this option is omitted the 130 Progress Report Options default directory of backup_dir meta is used where backup_dir is the directory specified with the backup dir option Note R Use this option to turn on message logging for the 1ist image and validate operations Message logging is turned off by default for the two operations because they do not modify any files and a message log is usually not requir
225. ly unzip the file and put mysqlbackup exe at the desired installation location You can add that location to the PATH variable so that you can run the mysqlbackup client from any directory Verify the installation by selecting the menu item Start gt Programs gt MySQL Enterprise Backup 3 12 gt MySQL Enterprise Backup Command Line The menu item displays version information and opens a command prompt for running the mysqlbackup command 19 20 Chapter 3 What s New in MySQL Enterprise Backup 3 12 This chapter highlights the new features in MySQL Enterprise Backup 3 12 as well as any significant changes made to MySQL Enterprise Backup with the release of this series e Renaming a table restored from a TTS backup You can now rename a table when you restore it from a backup created using transportable tablespace TTS See the description for the rename option for details e Support for OpenStack Object Storage MySQL Enterprise Backup now supports cloud backup and restore using OpenStack Object Storage Swift MySQL Enterprise Backup supports the Swift v1 0 API and also the OpenStack Identity Keystone API v2 0 for authentication Also supports authentication using Swift s TempAuth system A number of new command options have been introduced to support OpenStack Object Storage see Section 13 14 Cloud Storage Options for details e Binary and Relay Logs are now compressed when included in a compre
226. mand Line Format xclude tables REGEXP Permitted Values Type string Exclude for backup or restoration all tables both innodb and non innodb whose fully qualified names in the form of db_name table_name match the regular expression REGEXP The regular expression syntax is the extended form specified in the POSIX 1003 2 standard For example xclude tables mydb t 12 matches the tables t 1 and t2 in the database mydb On Unix like systems quote the regular expression appropriately to prevent interpretation of shell meta characters mysqlbackup throws an error when the option is used without a regular expression being supplied with it While mysqlbackup understands the MySQL convention of quoting the database or the table name or both by backticks see Schema Object Names there is no need to include the backticks in the regular expression for xclude tables While the option can be used for different kinds of backups selective restore is only supported for backups created using transportable tablespaces TTS that is backups created with the use tts option The option can also be used with the backup dir to image and image to backup dir commands to select tables when creating or unpacking a backup image The option cannot be used together with the include databases databases list file or only innodb with frm option When used together with the include tables option in
227. mat that keeps table data compressed during normal operation An InnoDB tablespace that is already in compressed row format is not compressed a second time but is nevertheless still saved as an ibz file in the compressed backup See Also bz file compression compression level ibd file ibz file MySQL Enterprise Backup tablespace ibdata file A set of files with names such as ibdatal ibdata2 and so on that make up the InnoDB system tablespace These files contain metadata about InnoDB tables and can contain some or all of the table and index data 177 also depending on whether the file per table option is in effect when each table is created For backward compatibility these files always use the Antelope file format See Also Antelope system tablespace image The file produced as part of a single file backup operation It can be a real file that you store locally or standard output specified as when the backup data is streamed directly to another command or remote server This term is referenced in several mysqlbackup options such as backup dir to image and image to backup dif See Also single file backup streaming include In a partial backup to select a set of tables databases or a combination of both to be backed up Contrast with exclude See Also partial backup incremental backup A backup that captures only data changed since the previous backup It has the potential to be smaller and faster than
228. mpatible software or if it is done without using any work based on GCC For example using non GPL compatible Software to optimize any GCC intermediate representations would not qualify as an Eligible Compilation Process 1 Grant of Additional Permission You have permission to propagate a work of Target Code formed by combining the Runtime Library with Independent Modules even if such propagation would otherwise violate the terms of GPLv3 provided that all Target Code was generated by Eligible Compilation Processes You may then convey such a combination under terms of your choice consistent with the licensing of the Independent Modules 2 No Weakening of GCC Copyleft The availability of this Exception does not imply any general presumption that third party software is unaffected by the copyleft requirements of the license of GCC E 3 GNU Standard C Library libstdc License The following software may be included in this product GNU Standard C Library libstdc This component is licensed under Section E 2 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 Additional notices Copyright c 1994 Hewlett Packard Company Permission to use copy modify distribute and sell this software and its documentation for any purpose is hereby granted without fee provided that the above copyright notice appear in all copies and that both that copyright noti
229. mysql innodb_table_stats ibd 13 10 39 mysqlbackup INFO Copying datadir mysql slave_master_info ibd 13 10 39 mysqlbackup INFO Copying datadir mysql slave_relay_log_info ibd 13 10 39 mysqlbackup INFO Copying database directory datadir mysql 13 10 39 mysqlbackup INFO Copying datadir mysql slave_worker_info ibd IslG 39 mysqlbackup INFO Copying datadir test2 tb1 bd 13 10 39 mysqlbackup INFO Copying database directory datadir performance_schema 13 10 39 mysqlbackup INFO Copying database directory datadir test 13 10 39 mysqlbackup INFO Copying database directory datadir test2 13 10 40 mysqlbackup INFO Copying database directory datadir mysql 13 10 41 mysqlbackup INFO Copying database directory datadir performance_schema 13 10 42 mysqlbackup INFO Copying database directory datadir test 13 10 42 mysqlbackup INFO Copying database directory datadir test2 13 10 43 mysqlbackup INFO Total files as specified in image 161 13 10 43 mysqlbackup INFO Creating server config files server my cnf and server all cnf in var lib m 13 10 43 mysqlbackup INFO Copy back operation completed successfully backup INFO Source Image Path home admin backups my mbi lbackup INFO Creating 14 buffers each of size 65536 13 10 43 mysqlbackup INFO Apply log operation starts with following threads ad threads process threads backup INFO Using up to 100 MB of memory 13 10 43 mysqlbackup INFO ibbackup_logfile s creation parameters start ln
230. n are required for a successful restore The master database is now recovered Shut down the master and edit my cnf to uncomment log ban Start the master again Start replication in the slaves again mysql gt START SLAVE 63 64 Chapter 7 Performance Considerations for MySQL Enterprise Backup Table of Contents 7 1 Optimizing Backup Performance ccceeeeeeeee ee ae ea eeeeeeee ee ee ae aaa eeeeeeeeseaaaaaaeeeeeeeeseaaaaaaeeeeeeeeeeaaa 65 7 2 Optimizing Restore Performance ccccccceeeeeeeeeeeeeeee aa ee eeeeeeeeeeeeaaaaeedeeseeeeeeaeaaeaeeeeeeeeeeaeaaeaneneeeees 68 This chapter describes the performance considerations for backing up and restoring databases using MySQL Enterprise Backup 7 1 Optimizing Backup Performance This section describes the performance considerations for backing up a database with MySQL Enterprise Backup When optimizing and tuning the backup procedure measure both the raw performance how long it takes the backup to complete and the amount of overhead on the database server When measuring backup performance consider The limits imposed by your backup procedures For example if you take a backup every 8 hours the backup must take less than 8 hours to finish The limits imposed by your network and storage infrastructure For example if you need to fit many backups on a particular storage device you might use compressed backups even if that made the backup
231. n it and proceeds to the next file instead In that case the operation s summary will not give a full count of corrupted pages but only says at least 20 pages are corrupted The operation also has the following limitations e For any backup directory the operation can only validate the InnoDB data files ibdata and ibd files in it Problems with other file types within a backup directory for example frm file corruptions are not detected 91 Validation Operations e If any ibdor frmfiles are missing from a backup directory during a backup or have been deleted from a backup directory after the backup was made the validate operation will not be able to detect the problem e If a backup directory has been corrupted by removing or truncating pages from any of the ibd files inside the validate operation will not be able to detect the problem Here is asample command for validating a backup directory mysqlbackup uroot backup dir logs backupext validate Here is asample command for validating a backup image mysqlbackup uroot backup image logs fullimage mi validate The following is a sample command for validating an encrypted backup image and the output for the successful validation mysqlbackup backup image meb backups image mbi decrypt key file meb enckeyfile validate 140219 11 22 44 mysqlbackup INFO Validating image logs img bi 140219 11 22 44 mysqlbackup INFO Validate Dir
232. nally this has not been possible for InnoDB tablespaces because all table data was part of the system tablespace In MySQL 5 6 and higher the FLUSH TABLES FOR EXPORT syntax prepares an InnoDB table for copying to another server running ALTER TABLE DISCARD TABLESPACE and ALTER TABLE IMPORT TABLESPACE on the other server brings the copied data file into the other instance A separate cfg file copied along with the ibd file is used to update the table metadata for example the space ID as the tablespace is imported See Copying File Per Table Tablespaces to Another Server for usage information Use the use tts option to create a backup with transportable tablespace See also Section 5 2 4 Restoring Backups Created with the use tts Option See Also partial backup TTS Short form for transportable tablespace See Also partial backup transportable tablespace 184 W warm backup A backup taken while the database is running but that restricts some database operations during the backup process For example tables might become read only For busy applications and web sites you might prefer a hot backup See Also backup cold backup hot backup 185 186 Index Symbols exclude tables option 40 include tables option 40 frm file 40 A Antelope 85 173 apply 173 apply incremental backup option 54 89 apply log option 88 ARM file 173 ARZ file 173
233. nate mca in ers Wa eve tae ae ealg ners ale amen A Frequently Asked Questions for MySQL Enterprise Backup ceseeeeeeeeeeeeeeeteeeeeeeeeaeaaea B MySQL Enterprise Backup Limitations 0 cccccceeeeeeeeeeeeeeeeeee tees aaeaeeeeeeeeeeeeaeaaeeneeeeeeeeeaeaaea B 1 Limitations of MySQL Enterprise Backup 0 cceceeeeeeeeeeeeeeeeeeeeaaeateeeeeeeeeaeaaaaenees C Compatibility Information for MySQL Enterprise Backup 0 ccceceeeeeeeeeeeeeeeeeeeeeaeaaeeeeeeeees C 1 Cross Platform Compatibility cece cceeeeeee cece eee eeee cree tees ae aaee tenses eeeeaeaaaaeeeeeeeeeaeaaes C 2 Compatibility with MySQL Versions 0 cccccceeeeeeeeeeeeeeeee teen aeaaeeeeeeeeeeeeaeaaaaeeeeeeeeeeeaaa C 3 Compatibility with Older MySQL Enterprise Backup c eeeeeeeeeeeeeeaeeeeeeeeeeeeeeeaes C 4 Compatibility Notes for Specific MySQL Versions 0 ccccceeeeeeeeeeeeeeeeeeeeeaeaaeneeeeeeees D MySQL Enterprise Backup Release Notes cccceeeceeeeeeeeeeeeeeeeaaaaeeeeeeeeeeeeaaaaeeeeeeeeeeeeaaa E Licenses for Third Party Component ceceeeeeeeeeeeeeeeeeeeeeeeaaaaeeeeeeeeeeeeaeaaeeneeeeeeeeeaeaaea E 1 CURL ocurl LICGMSO sssscccts cccecstexeceaasiacieasseroconstecntessennedias AAEN RRAN E 2 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 cccccecccecece cece ee eeee ae eeeeeeeeaaeeeeaeeesaeeeeaaeeesaeeeaaes E
234. ncluding any InnoDB datafiles in the backup innodb_checksum_algorithm The name of the checksum algorithm used for validating InnoDB tablespaces innodb_data_file_path innodb_data_home_dir Specifies InnoDB system tablespace files path and size Specifies base directory for all InnoDB data files in the shared system tablespace innodb_log_file_size The size in bytes of each InnoDB log file in the log group innodb_log_files_in_group The number of InnoDB log files 99 Format Description Introduced innodb_log_group_home_dir innodb_page_size The directory path to InnoDB log files The page size for all InnoDB tablespaces in a MySQL instance key The symmetric key used for encryption and decryption key file The pathname of a file that contains the symmetric key used for encryption and decryption limit memory The memory in MB available for the MEB operation log bin index Specifies the absolute path of the index file on the MySQL server that lists all the used binary log files for MySQL 5 5 and for all offline backups login path Read options from the named login path in the mylogin cnf login file master info file Specifies the absolute path of the information file in which a slave records information about its master for offline backups of salve servers only information file messages logdir no c
235. ne operation is the restore step You can optionally perform a cold backup which is another offline operation Contrast with online See Also cold backup online restore online A type of operation performed while the database server is running A hot backup is the ideal example because the database continues to run and no read or write operations are blocked For that reason sometimes hot backup and online backup are used as synonyms A cold backup is the opposite of an online operation by definition the database server is shut down while the backup happens A warm backup is also a kind of online operation because the database server continues to run although some write operations could be blocked while a warm backup is in progress Contrast with offline See Also cold backup hot backup offline warm backup optimistic backup Optimistic backup is a feature introduced in MySQL Enterprise Backup 3 11 for improving performance for backing up and restoring huge databases in which only a small number of tables are modified frequently An optimistic backup consists of two phases 1 the optimistic phase in which tables that are unlikely to be modified during the backup process identified by the user with the opt imist ic time option or by exclusion with the optimistic busy tables option are backed up without locking the MySQL instance 2 a normal phase 180 in which tables that are not backed up in the first phase are be
236. ng the MySQL Enterprise Backup Manifest Each backup directory includes some files in the met a subdirectory that detail how the backup was produced and what files it contains The files containing this information are known collectively as the manifest mysqlbackup produces these files for use by database management tools it does not consult or modify the manifest files after creating them Management tools can use the manifest during diagnosis and troubleshooting procedures for example where the original MySQL instance has been lost entirely and the recovery process is more involved than copying files back to a working MySQL server The files in the manifest include e backup_create xml1 information about the backup operation e backup_content xm1 information about the files in the backup This information is only complete and consistent when the backup operation succeeds A management tool might use this information to confirm which tables are part of a full backup or a partial backup performed with the databases option the information is not present for partial backups taken with the include incremental incremental with redo log only only innodb or only innodb with frm options A management tool might compare the checksum recorded in the manifest for a single file backup against the checksum for the file after the single file backup is unpacked The file also contains details of all the plugins defined on the backed up server
237. nly mode while the redo log with only the portion containing the relevant changes 117 Legacy Partial Backup Options made after the hot backup is being included in the backup Any tables created during the locking phase are ignored e with full locking The selected tables are locked in read only mode while they are being backed up The redo log is not included in the backup Any tables created during the locking phase are ignored Note E Due to a known issue when creating a backup using TTS for a server containing tables with a mix of the Antelope and Barracuda file formats do NOT apply full locking on the tables Default with minimum locking To use the use tts option extra privileges are required of the user through which mysqlbackup connects to the server see Section 4 1 2 Grant MySQL Privileges to Backup Administrator for details There are some special requirements for restoring backups created with the use tts option see Section 5 2 4 Restoring Backups Created with the use tts Option for details rename old_table_name to new_table_name Rename a single table when it is selected by the include tables or xclude tables option or both together to be restored to a database from a backup created using the use tts option The table named old_table_name is renamed to new_table_name Note that when using the option e The include tables or xclude tables option or
238. nnodb_undo_logs option on the backed up server backup_innodb_undo_tablespaces NUMBER Specifies the number of tablespace files that the undo logs are divided between when you use a non zero backup_innodb_undo_logs setting This option should be specified carefully because the value must be the same as that of innodb_undo_tablespaces on the backed up MySQL instance or the backup could become useless For an online backup the value for the parameter is taken from the value of the innodb_undo_tablespaces option on the backed up server By default all the undo logs are part of the system tablespace and the system tablespace will always contain one undo tablespace in addition to those configured by innodb_undo_tablespaces backup_innodb_checksum_algorithm NAME Specifies for an offline backup the name of the checksum algorithm used for validating the InnoDB tablespaces on the restored server This option should be specified carefully because the checksum algorithm must be the same use on the backed up MySQL instance or the backup could become useless For an online backup the value is taken from the value of the innodb_checksum_algorithm option on the backed up server Default value of the option is innodb Value of this option is saved in the backup my cnf file to be used for restoring the database 13 5 Metadata Options These options control the generation of metadata about backups Some metadata is stored in the backup dire
239. nodb_log_file_size lt innodb_log_file_size_of_backedup_server gt innodb_data_file_path lt innodb_data_file_path_of_backedup_server gt uncompress backup image copy back and apply log Example 4 17 Stream a Backup Directory to a Remote MySQL Server The following command streams a backup directory as a single backup file to be restored on a remote MySQL server mysqlbackup backup image backup dir path to my backup backup dir to image ssh lt user name gt lt remote host name gt mysqlbackup backup dir backup_tmp datadir data backup image copy back and apply log 4 3 5 2 Backing Up to Tape Tape drives are affordable high capacity storage devices for backup data MySQL Enterprise Backup can interface with media management software MMS such as Oracle Secure Backup OSB to drive MySQL backup and restore jobs The media management software must support Version 2 or higher of the System Backup to Tape SBT interface For information about doing tape backups in combination with MMS products such as Oracle Secure Backup see Chapter 9 Using MySQL Enterprise Backup with Media Management Software MMS Products 4 3 5 3 Backing Up to Cloud Storage MySQL Enterprise Backup supports cloud backups Only single file backups can be created on and restored from cloud storage All mysqlbackup options compatible with single file operations including for example the incremental compression
240. non innodb files Adding database directory datadir test Adding database directory datadir test2 A copied database page was modified at 1631766 31 Verifying a Backup This is the highest lsn found on page Scanned log up to lsn 1631766 Was able to parse the log up to lsn 1631766 Maximum page number for a log record 0 141204 12 55 04 mysqlbackup INFO All tables unlocked 141204 12 55 04 mysqlbackup INFO All MySQL tables were locked for 2 057 seconds 141204 12 55 04 mysqlbackup INFO Reading all global variables from the server 141204 12 55 04 mysqlbackup INFO Completed reading of all global variables from the server 141204 12 55 04 mysqlbackup INFO Creating server config files server my cnf and server all cnf in home admi mysqlbackup INFO Copying meta file home admin backup tmp meta backup_variables txt mysqlbackup INFO Copying meta file home admin backup tmp datadir ibbackup_logfile mysqlbackup INFO Copying meta file home admin backup tmp server all cnf mysqlbackup INFO Copying meta file home admin backup tmp server my cnf mysqlbackup INFO Copying meta file home admin backup tmp meta backup_content xml mysqlbackup INFO Copying meta file home admin backup tmp meta image_files xml 141204 12 55 08 mysqlbackup INFO Full Image Backup operation completed successfully 141204 12 55 08 mysqlbackup INFO Backup image created successfully mysqlbackup INFO Image Path home admin backups my mbi 141
241. ntal backups it should not be deleted or modified by users For some sample commands for restoring different kinds of backups with the copy back and apply log command see Section 5 2 Performing a Restore Operation Warning When restoring a server for replication purpose if the backed up server has used the innodb_undo_directory option to put the undo logs outside of the data directory when using the file server my cnf or server al11 cnf for the defaults file option with copy back or copy back and apply log care should be taken to configure correctly the innodb_undo_directory option in the file Otherwise the data or log files on the original server might be overwritten by accident 12 4 Validation Operations To ensure the integrity of the backup data MySQL Enterprise Backup provides a validate command for validating a backup by the checksum values of its data pages after the backup is created or transferred to another system mysqlbackup STD OPTIONS backup dir PATH backup image IMAGE MESSAGE LOGGING OPTIONS PROGRESS REPORT OPTIONS CLOUD STORAGE OPTIONS validate e validate Verifies that a backup is not corrupted truncated or damaged This operation validates the checksum value for each data page in a backup To avoid spending excessive time and resources on files that are too heavily corrupted mysqibackup stops validating a ibd file after more than twenty corrupted pages are found i
242. o image operation Overwriting data in a non empty target directory with backup data during a copy back operation performed on a full backup the use of copy back and apply log is not recommended in this case Restoring a partial image backup created with MySQL Enterprise Backup 3 11 or earlier the force option is required due to a known issue Bug 20485910 Restoring a backup onto a server where the directory pointed to by the b1 file in the backup a copy of the isi file from the backed up server already contains ibd data files For all other operations the force option is rejected with an error message trace level Command Line Format t race LEVEL Permitted Values Type enumeration Default 0 Valid 0 Values 2 3 Trace level of mysqlbackup messages The permissible levels in the order of increasing fineness are e 0 INFO information warnings errors 1 FINE verbose option is enabled 2 FINER debug option is enabled 103 Connection Options e 3 FINEST includes all low level outputs 13 2 Connection Options When mysqlbackup creates a backup it sends SQL commands to MySQL server using a database connection The general connection details are the same as described in Connecting to the MySQL Server in the MySQL Reference Manual As part of the mysqibackup invocation specify the appropriate user password port and or so
243. oduction to MySQL Enterprise Backup ccccececceeeeeeeeee ee ee ae ea eeeeeeeeeeeeaeaaaaneeeeeeeeeaeaaaaeenees 5 1 1 Types of Backups 2 e2cccclcc ecectendeseleceed ce cteded ceeeeaecedeeadsecietse ceededee cbbedaermcnendesleckeernedee 5 1 2 The mysqlbackup Client cccceccceceee cece cece tees eae eeee cesses ee aaeaeeeeeeeeeseaaaaeeeeeeeeeeaeaaaaeeeees 6 1 3 Overview of Backup Performance and Capacity Considerations c cseeseeeeeeeeeeeeeee 6 1 4 Files that Are Backed Up 0 ccccceeeeeeeceee teeter ee ee eee eeeeeeeeee ee ae aaeeteeeeeeeeeaeaaeaneeeeeeeeeaeaaea 7 1 5 Overview of Restoring a Database 0 0 cece cceceeeee cece ee eeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeeeeeeeeeees 17 2 Installing MySQL Enterprise Backup 0 ccccececeeeeeeeeeeeeeee ee aa ea eeeeeeeeeeeeaaaaeeneeeeeeeeeaeaaeaneneeeees 19 3 What s New in MySQL Enterprise Backup 3 12 0cccecceeeeeeeeeeeeeeeeeeeeeeaeaeeeeeeeeeeeeaeaaeaneneeeees 21 Il Using MySQL Enterprise Backup ccc ceeeeeee cece eee tee ee ee ee ee ee eaten sees ee ae aa ea teeeeeeeeeeeaaaaeeeeeeeeeeeeaea 23 4 Backing Up a Database Server 0 cccccececeeeeeeeee eee e ee ee eet te seen ee ee aa da teen gees ee aeaaaaneeeeeeeeeanaaea 27 4 1 Before the First Backup cccceeeee ee eeee ee ee cece neeese Eea KENE aaa E REES 27 4 1 1 Collect Database Information 0 cc ccceceeeeeee cece ee aeeeteeeeeee tees aaeaeeeeeeeeeeaeaaaaeenee
244. of the InnoDB system tablespace Because the MySQL Enterprise Backup product always backs up the system tablespace all backups include the contents of the data dictionary See Also hot backup MySQL Enterprise Backup system tablespace 175 database A set of tables and related objects owned by a MySQL user Equivalent to schema in Oracle Database terminology MySQL Enterprise Backup can perform a partial backup that includes some databases and not others The full set of databases controlled by a MySQL server is known as an instance See Also instance partial backup differential backup A backup that captures only the data changed since the last full backup It has the potential to be smaller and faster than a full backup but is usually bigger and takes longer to create than an incremental backup See Section 4 3 2 Making a Differential or Incremental Backup for usage details Related mysqlbackup options are incremental incremental with redo log only incremental backup dir incremental base and start lsn See Also full backup incremental backup downtime A period when the database is unresponsive The database might be entirely shut down or in a read only state when applications are attempting to insert update or delete data The goal for your backup strategy is to minimize downtime using techniques such as hot backup for InnoDB tables cold backup using slave servers in a replication configuration
245. og to the compressed backup files so that the full backup is ready to be restored at any time You can move the backup data to a different server first to avoid the CPU and I O overhead of performing this operation on the database server e After applying the log periodically take incremental backups which are smaller and can be made faster than a full backup 4 3 4 Making a Partial Backup Note R To facilitate the creation of partial backups MySQL Enterprise Backup has introduced two new options for partial backup since version 3 10 include tables and xclude tables The new options are intended for replacing the older options of include databases databases list file and only innodb with frm which are incompatible with the new options and will be deprecated in the upcoming releases In the discussions below we assume the new options are used for partial backups For reference purpose we have included information on the older options at the end of this section in Making a Partial Backup with Legacy Options By default all the files under the database subdirectories in the data directory are included in the backup so that the backup includes data from all MySQL storage engines any third party storage engines and even any non database files in that directory This section explains options you can use to selectively back up or exclude data There are various ways to create different kinds of partial backup with MySQL Ente
246. ompare the rate of redo log accumulation with the size of the redo log files Use this ratio to see how often to take an incremental backup in order to avoid the likelihood of the backup failing because the historical data are not available in the redo log For example if you are producing 1GB of redo log data per day and the combined size of your redo log files is 7GB you would schedule incremental backups more frequently than once a week You might perform incremental backups every day or two to avoid a potential issue when a sudden flurry of updates produced more redo than usual Benchmark incremental backup times using both the incremental and incremental with redo log only options to confirm if the redo log backup technique performs faster and with less overhead than the traditional incremental backup method The result could depend on the size of your data the amount of DML activity and the size of your redo log files Do your testing on a server with a realistic data volume and a realistic workload For example if you have huge redo log files reading them in the course of an incremental backup could take as long as reading the InnoDB data files using the traditional incremental technique Conversely if your data volume is large reading all the data files to find the few changed pages could be less efficient than processing the much smaller redo log files Other Considerations for Incremental Backups The incremental backup fea
247. on the command line or in a configuration file e Parameters you specify on the mysqlbackup command line You can specify certain options for individual backup jobs this way e The MySQL configuration file by default my cnf on Unix and my ini on Windows The parameters are searched for first under the mysqlbackup group then under the client group You can put common parameters that apply to most of your backup jobs into the configuration file Because mysqlbackup does not overwrite any files during the initial backup step the backup directory must not contain any old backup files mysqlbackup stops when asked to create a file that already exists to avoid harming an existing backup For convenience specify the with timestamp option which always creates a unique timestamped subdirectory for each backup job underneath the main backup directory Configuration Files Stored with the Backup Data Each set of backup data includes a configuration file backup my cnf containing a minimal set of configuration parameters The mysqlbackup command generates this file to record the settings that apply to this backup data Subsequent operations such as the appl y log process read options from this file to determine how the backup data is structured Example 14 1 Example backup my cnf file Here is an example backup my cnf file generated by mysqlbackup mysqld innodb_data_file_path ibdatal 256M ibdata2 256M autoextend innodb_log_fil
248. onnection Specifies the path name of an existing directory for storing the message log Do not connect to server no defaults Do not read default options from any given file no history logging Disable history logging even if connection is available no locking number of buffers Disable locking of tables even if connection is available Specifies the exact number of memory buffers to be used for the backup operation on disk full Specifies the behavior when a backup process encounters a disk full condition only innodb Back up only InnoDB data and log files only innodb with frm only known file types Legacy Back up only InnoDB data log files and the frm files associated with the InnoDB tables Includes only files of a list of known types in the backup optimistic busy tables Perform an optimistic backup using the regular expression specified with the option to select tables that will be skipped in the first phase of an optimistic backup optimistic time Perform an optimistic backup with the value specified with the option as the optimistic time a time after which tables that have not been modified are believed to be inactive tables page reread count page reread time Maximum number of page re reads Wait time before a page re read password Connection password pipe alias for protocol pipe port TCP portnumber to conn
249. or subdividing an organization or merging organizations If propagation of a covered work results from an entity transaction each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party s predecessor in interest had or could 160 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 give under the previous paragraph plus a right to possession of the Corresponding Source of the work from the predecessor in interest if the predecessor has it or can get it with reasonable efforts You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License For example you may not impose a license fee royalty or other charge for exercise of rights granted under this License and you may not initiate litigation including a cross claim or counterclaim in a lawsuit alleging that any patent claim is infringed by making using selling offering for sale or importing the Program or any portion Bi AREE 11 Patents A contributor is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based The work thus licensed is called the contributor s contributor version A contributor s essential patent claims are all patent claims owned or controlled by the contributor whether already acquired or hereafter acquired that would be in
250. oration Currently there are two types of cloud storage services supported by mysqibackup represented by the following values for the options e 53 Amazon Simple Storage Service S3 openstack OpenStack Object Storage Swift MySQL Enterprise Backup 3 12 supports the Swift v1 0 API and also the OpenStack Identity Keystone API v2 0 for authentication Also supports authentication using Swift s TempAuth system cloud trac Print trace information for cloud operations It works independently of t race 103 which specifies the trace level for the non cloud operations of mysqibackup Any non zero value for the option enables the trace function Default value is 0 cloud proxy proxy url port Proxy address and port number for overriding the environment s default proxy settings for accessing a cloud storage service 135 Cloud Storage Options Note N The list image operation can be performed on a cloud backup only if the cloud proxy supports HTTP range headers e Options used only for Amazon S3 using them when the argument for cl1oud service is anything other than s3 will cause mysqlbackup to throw an error cloud bucket S3_BUCKET The storage bucket on Amazon S3 for the backup image In order to perform cloud backups and restores with the bucket the user identified by the cloud access key id option must have at least the following permissions on the bucket e s3 ListBucket For lis
251. oring a backup 5 2 1 Restoring a Compressed Backup Restore a compressed backup at lt backupDir gt to lt restoreDir gt on the server using copy back and apply log 55 Restoring an Encrypted Backup Image Example 5 7 Restoring a Compressed Backup mysqlbackup defaults file lt my cnf gt uroot backup dir lt backupDir gt datadir lt restoreDir gt uncompress copy back and apply log Do the same for a compressed backup image named lt image_name gt using the backup dir option to specify the temporary directory into which the image will be extracted mysqlbackup defaults file lt backupDir gt backup my cnf uroot backup image lt image_name gt backup dir lt backupTmpDir gt datadir lt restoreDir gt uncompress copy back and apply log See Section 4 3 3 Making a Compressed Backup and Section 13 6 Compression Options for more details on compressed backups 5 2 2 Restoring an Encrypted Backup Image Restore an encrypted backup image named lt image_name gt to lt restoreDir gt on the server with copy back and apply log using the encryption key contained in a file named lt keyFile gt Example 5 8 Restoring an Encrypted Backup Image mysqlbackup defaults file lt backupDir gt backup my cnf backup image lt image_name gt backup dir lt backupTmpDir gt datadir lt restoreDir gt decrypt key file lt keyFile gt copy back and apply log See Section 13 13 En
252. ormance Condition 2 though can remain unfulfilled even when condition 1 has been satisfied for example mysqibackup could copy all the pages of a tablespace correctly except for one page for which mysqibackup has included an old version into the copy If the LSN of that old version of the page is smaller than the LSN first seen by mysqlbackup at the beginning of the backup process the resulting backup will be defective This example shows that mysqlbackup may have problem preforming a hot backup unless it can see the writes to the file system being executed in the correct order that is the order in which the server executed them Regarding condition 3 unlike data file pages redo log blocks are written sequentially which means condition 3 is easier to fulfill than conditions 1 and 2 However if mysqlbackup reaches the highest LSN in the copied data file pages before encountering the end of the redo log the backup fails A failure occurs also if mysqlbackup reads a corrupted log block at any time during the copying of the redo log Both these failures can occur if mysqlbackup does not see the same history of the file system states as the MySQL server does Therefore to use mysqlbackup with a DFS or SAN it is important to make sure that mysqibackup sees all the writes to the file system in the same order as the MySQL server does The condition is most likely to be satisfied when mysqlbackup and the MySQL server are running on the same server node
253. oss Platform Compatibility 0 00 0 cece ceeeeee cece eee cece eter tees ae aaa eeeeeeeeeeaeaaaaaeeeeeeeeeaeaaaaneeeeeees 149 C 2 Compatibility with MySQL Versions 0 cccecececeeeeeee cece cece aa ee eeeeeeeeee ee aaaaeeeeeeeeeeeeaaaaaeneenereees 149 C 3 Compatibility with Older MySQL Enterprise Backup ccceeeeeeeee eee eeeeeeeeeeeeaeaaeaeeeeeeees 149 C 4 Compatibility Notes for Specific MySQL Versions ccceccccceeeeeeeeeeeeeeeaeeaeeeeeeeeeeeeaeaaeaees 149 D MySQL Enterprise Backup Release Notes 0 c cccceeeeeeeeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeaeeeeeeeeeaeaaaaenees 151 E Licenses for Third Party Component 2 cccccccceeeeeeeeeeeee ee ee ae ee teeeeeeeeeaeaaeaeeeeeeeeeaeaaeaneeeeeeeeeaeaae 153 El CURL hocurl License soa E E EAE aie ae iid a Wa Ae aie Stee 153 E 2 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 ccccecccecece cece ee eeee ee eeeeeeee ae eeeeaeeesaeeeeaeeesaeeeeaeeeeseeeaaes 153 E 3 GNU Standard C Library libstdc License 200 00 cece cece cece cece eeeeeeeeeeeeeeaaaaeeeeeeeeees 165 E 4 Google Controlling Master Thread I O Rate Patch License cceceecseeeeeeeeeeeeeeeaeeeeeees 166 E 5 Google SMP Patch License simian aaa i a a iaa aa 167 E6 EZ4AkICGnSO aea O E S E O E a E E at aaa SS 168 E 7 OpenSsL v1 0 EICENS E ming harain a a ee a 168 E 8 Percona Multiple I O Threads Patch License
254. other places Here are some sample commands to start a backup operation with mysqlbackup are Information about data files can be retrieved through the database connection Specify connection options on the command line mysqlbackup user dba password port 3306 with timestamp backup dir export backups backup Or we can include the above options in the configuration file under the mysqlbackup section and just specify the configuration file and the backup operation mysqlbackup defaults file usr local mysql my cnf backup Or we can specify the configuration file as above but override some of those options on the command line mysqlbackup defaults file usr local mysql my cnf compress user backupadmin password port 18080 backup The user and the password you specify are used to connect to the MySQL server This MySQL user must have certain privileges in the MySQL server as described in Section 4 1 2 Grant MySQL Privileges to Backup Administrator The with timestamp option places the backup in a subdirectory created under the directory you specified above The name of the backup subdirectory is formed from the date and the clock time of the backup run For the meanings of other command line options see Chapter 13 mysql backup Command Line Options For information about configuration files see Chapter 14 Configuration Files and Parameters Make sure that th
255. otice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution Neither the name of Google Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission 170 RegEX Spencer Library License HIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS ND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE MPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE RE DISCLAIMED IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE IABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPECIAL EXEMPLARY OR ONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF UBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS RRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN RACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE NG IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE OSSIBILITY OF SUCH DAMAGE Sl iS On 2H H ii W al n lig HSE 1G 1S tes fey al as The RE2 Authors are Google Inc Samsung Electronics Stefano Rivera lt stefano rivera gmail com gt E 10 RegEX Spencer Library License The following software may be included in this product Henry Spencer s Regular Expression Library RegEX Spencer Copyright 1
256. ow go inside the meta subdirectory backup_variables txt Holds important information about the backup For use by mysqlbackup only mysqlbackup consults and possibly updates this file during operations after the initial backup such as the apply log phase or the restore phase image_files xml Contains the list of all the files except itself that are present in the single file backup produced by the backup to image or backup dir to image options For details about this file see Section 10 5 Using the MySQL Enterprise Backup Manifest This file is not modified at any stage once generated backup_create xml Lists the command line arguments and environment in which the This file is not modified once it is created You can prevent 13 Files that Are Backed Up File Name Pattern or Extension Relation to Original Data Files Notes backup was created For details about this file see Section 10 5 Using the MySQL Enterprise Backup Manifest this file from being generated by specifying the disable manifest option backup_content xml Essential metadata for the files and database definitions of the backup data It also contains details of all the plugins defined on the backed up server by which users should make sure the same plugins are defined in the same manner on the target server for restoration For details about this file see Section
257. oxy option 135 cloud secret access key option 136 cloud service option 135 cloud trace option 135 cold backup 5 174 command line tools 6 comments option 112 comments file option 112 comments txt file 7 112 compress option 39 112 compress level option 39 113 compress method option 112 compressed backups 6 39 44 54 112 compression 175 compression level 175 configuration file 175 configuration options 139 connection 175 connection options 104 187 copy back option 17 53 89 copy back and apply log option 32 90 corruption problems 76 crash recovery 53 175 cron jobs 51 CSM file 7 CSV file 7 D data dictionary 175 database 176 databases option 119 databases list file option 120 datadir directory 7 datadir option 105 data_home_dir option 105 decrypt option 134 decryption 71 differential backup 176 disable manifest option 123 disk storage for backup data 6 47 distributed file system 52 downtime 176 dst entry option 122 E encrypt option 134 encrypted backups 71 encryption 71 error codes 75 exclude 176 exclude tables option 116 exec when locked option 138 extract 176 extract option 94 121 F FAQ 145 file format 176 files backed up 7 frequently asked questions 145 frm file 7 176 full backup 34 177 G GRANT statement 29 H history table 177 hot backup 5 177 l ibbackup_lo
258. p image sales mbi backup dir backups backup to image Example 4 5 Single File Backup to Standard Output The following command dumps the backup output to standard output Again the folder specified with the backup dir option is used as a temporary directory 45 Making a Single File Backup mysqlbackup backup dir backups backup image backup to image gt backup mybackup mbi Example 4 6 Convert Existing Backup Directory to Single Image The backup dir directory is bundled into the backup my mbii file mysqlbackup backup image backup my mbi backup dir var mysql backup backup dir to image Example 4 7 Extract Existing Image to Backup Directory The image contents are unpacked into backup dir mysqlbackup backup dir var backup backup image backup my mbi image to backup dir Example 4 8 List Single File Backup Contents The image contents are listed with each line indicating a file or directory entry mysqlbackup backup image backup my mbi list image Example 4 9 Validate a Single File Backup The following command verifies that the single file backup is not corrupted truncated or damaged by validating the checksum value for each data page in the backup mysqlbackup backup image logs fullimage mi validate Example 4 10 Extract Single File Backup into Current Directory The following command extracts all contents from a single file backup into the current working directory mysqlbackup bac
259. partial and encryption options can be used with cloud backups or restores Currently MySQL Enterprise Backup supports two types of cloud storage services Amazon S3 and OpenStack Object Storage Swift MySQL Enterprise Backup 3 12 supports the Swift v1 0 API and also the OpenStack Identity Keystone API v2 0 for authentication Also supports authentication using Swift s TempAuth system Backups are stored as dynamic large objects in Swift with each backup larger than 5G being split into multiple parts with names in the form of lt object_name gt _part_ lt number gt See the OpenStack documentation for details A cloud backup is created using the cloud options for mysqibackup which are described in details in Section 13 14 Cloud Storage Options Here are some sample commands for creating a cloud backup 48 Making an Optimistic Backup Example 4 18 Creating a Cloud Backup on Amazon S3 mysqlbackup cloud service s3 cloud aws region lt aws region gt cloud access key id lt aws access key id gt cloud secret access key lt aws secret access key gt cloud bucket lt s3 bucket name gt cloud object key lt aws object key gt backup dir home user dba s3backuptmpdir backup image backup to image Example 4 19 Creating a Cloud Backup on an OpenStack Object Storage This example uses the Keystone identity service for authenticating user credentials mysqlbackup includ
260. per_table mode Incremental backups are faster than full backups save storage space on the database server and save on network traffic to transfer the backup data on a different server Incremental backup requires additional processing to make the backup ready to restore which you can perform on a different system to minimize CPU overhead on the database server Compressed backups save on storage space for InnoDB tables and network traffic to transfer the backup data on a different server They do impose more CPU overhead than uncompressed backups Files that Are Backed Up During restore you need the compressed and uncompressed data at the same time so take into account this additional storage space and the time to uncompress the data In addition to compressing data within InnoDB tables compressed backups also skip unused space within InnoDB tablespace files Uncompressed backups include this unused space e When space is limited or you have a storage device such as tape that is cheap large but also slow the performance and space considerations are different Rather than aiming for the fastest possible backup you want to avoid storing an intermediate copy of the backup data on the database server MySQL Enterprise Backup can produce a single file backup and stream that file directly to the other server or device Since the backup data is never saved to the local system you avoid the space overhead on the database server You al
261. pply log operation but in MySQL Enterprise Backup 3 8 and higher it applies to all operations Do not include any suffixes such as mb or kb in the option value Default 100 for appl y log not used with uncompress 300 for all operations in megabytes The memory limit specified by this option also caps the number of 16MB buffers available for multithreaded processing For example with a 300 MB limit the maximum number of buffers is 18 If additional buffers are required because you increase the values for read threads process threads write threads and or number of buffers increase the limit memory value proportionally sleep MS Command Line Format sleep MS Permitted Values Type numeric Default 0 Specify the number in milliseconds to sleep after copying a certain amount of data from InnoDB tables Each block of data is 1024 InnoDB data pages typically totalling 16MB This is to limit the CPU and I O overhead on the database server Default 0 no voluntary sleeps no Locking Disables locking during backup of non InnoDB files even if a connection is available Can be used to copy non InnoDB data with less disruption to normal database processing There could be inconsistencies in non InnoDB data if any changes are made while those files are being backed up page reread time MS Command Line Format page reread t ime MS Permitted Values Type numeri
262. ption db_name table_name db_namel table_namel1 Remove any white spaces surrounding the database or table names as the white spaces are not removed automatically Begin a line with the character to include a comment No regular expressions are allowed If the specified entries do not match any database or table then no non InnoDB data files are backed up databases or tables it specifies To filter InnoDB data files use the include Note E The option has no filtering effects on the InnoDB data files iba files for the option instead e only innodb with frm all related Back up only InnoDB data log files and the frm files associated with the InnoDB tables e only innodb with frm al1 includes the frm files for all InnoDB tables in the backup e only innodb with frm related in combination with the include option copies only the frm files for the tables that are included in the partial backup e only innodb with frm with no argument is the same as only innodb with frm related Note Ql For incremental backups even only changed ibd files are backed up frm files associated with all specified InnoDB tables are included This option saves you having to script the backup step for InnoDB frm files which you would normally do while the server is put into a read only state by a FLUSH TABLES WITH READ LOCK statement The frm files are copied without putting the server into a r
263. r backups 75 TTS 184 U uncompress option 113 uncompressed backups 6 43 use tts option 117 V validate option 91 validating a backup 91 verifying a backup 32 W warm backup 5 185 what is new 21 with timestamp option 110 write threads option 125 190
264. r peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d A separable portion of the object code whose source code is excluded from the Corresponding Source as a System Library need not be included in conveying the object code work A User Product is either 1 a consumer product which means any tangible personal property which is normally used for personal family or household purposes or 2 anything designed or sold for incorporation into a dwelling In determining whether a product is a consumer product doubtful cases shall be resolved in favor of coverage For a particular product received by a particular user normally used refers to a typical or common use of that class of product regardless of the status of the particular user or of the way in which the particular user actually uses or expects or is expected to use the product A product is a consumer product regardless of whether the product has substantial commercial industrial or non consumer uses unless such uses represent the only significant mode of use of the product Installation Information for a User Product means any methods procedures authorization keys or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source The information must suffice to ensure that the continue
265. r to allow restores of per table data files regardless of their format Selected tables can be restored from a backup created with transportable tablespaces TTS using the include tables and xclude tables options The following command restores all tables in the sales database from the backup but excludes the table with the name hardware Example 5 10 Restoring Selected Tables from a TTS Backup mysqlbackup socket tmp restoreserver sock datadir logs restoreserverdata backup dir logs backup include tables sales exclude tables sales hardware copy back and apply log 57 Restoring a Backup from Cloud Storage to a MySQL Server This following commands rename a table when restoring it from a TTS Backup by using the rename option Example 5 11 Restoring and Renaming a Table from a TTS Backup Using fully qualified table names mysqlbackup socket tmp restoreserver sock datadir logs restoreserverdata backup dir logs backup include tables sales cars rename sales cars to sales autos copy back and apply log It works the same if database names are omitted in the argument for rename mysqlbackup socket tmp restoreserver sock datadir logs restoreserverdata backup dir logs backup include tables sales cars rename cars to autos copy back and apply log 5 2 5 Restoring a Backup from Cloud Storage to a MySQL Server To restore a backup ima
266. racting it mysqlbackup backup image backups image enc decrypt key file meb key backup dir backups extract dir extract To validate an encrypted backup image mysqlbackup backup image logs encimage bi decrypt key file meb enckey validate 72 Chapter 9 Using MySQL Enterprise Backup with Media Management Software MMS Products Table of Contents 9 1 Backing Up to Tape with Oracle Secure Backup cccceeeeeeeeeee cece aaa eeeeeeeeeeaeaaeaeeeeeeeeeeeaaaaeenees 73 This section describes how you can use MySQL Enterprise Backup in combination with media management software MMS products Such products are typically used for managing large volumes of backup data often with high capacity backup devices such as tape drives 9 1 Backing Up to Tape with Oracle Secure Backup Tape drives are affordable high capacity storage devices for backup data MySQL Enterprise Backup can interface with media management software MMS such as Oracle Secure Backup OSB to drive MySQL backup and restore jobs The media management software must support Version 2 or higher of the System Backup to Tape SBT interface On the MySQL Enterprise Backup side you run the backup job as a single file backup using the backup image parameter with the prefix sbt in front of the filename and optionally pass other sbt parameters to mysqlbackup to control various aspects of the SBT processing The sbt options are listed in
267. rage Each file is unpacked directly to its final destination the same as if it was copied individually Thus if you can speed up the backup substantially or decrease its storage requirements by using single file backups that typically does not involve a tradeoff with restore time See Section 12 5 Single File Backup Operations for information about making single file backups The Apply Log Phase See The Apply Log Phase for performance considerations regarding the apply log phase Network Performance For data processing operations you might know the conventional advice that Unix sockets are faster than TCP IP for communicating with the database Although the mysqlbackup command supports the options protocol tcp protocol socket and protocol pipe these options do not have a significant effect on backup or restore performance These processes involve file copy operations rather than client server network traffic The database communication controlled by the protocol option is low volume For example mysqlbackup retrieves information about database parameters through the database connection but not table or index data Parallel Restore mysqlbackup can take advantage of modern multicore CPUs and operating system threads to perform backup operations in parallel See Section 13 10 Performance Scalability Capacity Options for the options to control how many threads are used for different aspects of the restore proc
268. rd OptiONS sipia inesonsnaeus irarria eiaeaen AANE NAE RAEE AANE EA Naaa 102 13 2 Connection Options i verac tte seteaeaeidabechetleaveiagledeahedavandacenschateastiielals dealecatandzieteahatieacaee 104 13 3 Server Repository Options ccceecece cece ee ee ee ee eee ee ee eres ee ae aaa teeeeeeeeeaeaaeaneeeeeeeeeeeaaeaeeees 105 13 4 Backup Repository Options resines iaaa eeeeeeeeeeeeaaaaaeeeeseeeeeeaeaaaeees 107 13 5 Metadata Options 20 02 ccc ec ee cece ect ee eee e ee ee eee akena eiaa a nese ee ae aaa eeeeeeeeaeaaaaneneeeees 111 13 6 Compression Options act secevbeee eee ececazde eieviehsoleagdel nigietecsdenae lead ehien a E Roa 112 13 7 Incremental Backup Options ccceceeeeeee ee eeeeeeeee sees ee ae eae eeeeeeeeeeaeaaeaeeeeeeeeeeaeaaaaneeeeeees 113 13 8 Partial Backup and Restore Options cceceeeeeee ee eeceeeeeee eres ee ae aaa eeeeeeeeeeseaaaaeeeeeeeeeeeeaea 115 13 9 Single File Backup Options c ccceceeeeeee ee eeeeee cece sete ee aa ee eeeeeeeeeeeeaaaaeteeeeeeeeeaaaaeeeeeseeeees 121 13 10 Performance Scalability Capacity Options cececeeeeeeeeeeeee eee ee eeeeeeeeeeeeaaaaeeeeeeeeeees 123 13 11 Message Logging Options ccececeeeeeceteeceeee eter ee ee eee eeeeee ee ee aa ea eee eeeeeeeeaaaaeeeeeeeeeeeaea 130 13 12 Progress Report Options w isis iivcieieiss Arad dinate Reels 131 13 13 Encryption Options ccccceceeeee cece cnet ee cere eter ee eed iaae a
269. rd for the user specified by cloud user id 136 The user credentials are authenticated using the Swift TempAuth identity system when the cloud tempauth url 137 option is used and by the OpenStack Keystone identity service when the cloud identity url 137 option is used cloud tempauth url SWIFT_TEMPAUTH URL The TempAuth URL for authenticating user credentials Either this option or cloud identity url 137 but not both should be used when accessing a Swift service s cloud identity url SWIFT_KEYSTONE URL The URL of the Keystone identity service when it is used for authenticating user credentials Either this option or cloud tempauth ur1 137 but not both should be used when accessing a Swift service cloud tenant SWIFT_KEYSTONE TENANT The Keystone tenant for the user specified by cloud user id 136 when the Keystone identity service is used for authenticating user credentials id cloud region SWIFT_KEYSTONE REGION The Keystone region for the user specified by cloud user id 136 when the Keystone identity service is used for authenticating user credentials 13 15 Options for Special Backup Types These options are for backing up database servers that play specific roles in replication or contain certain kinds of data that require special care in backing up e slave info When backing up a replication slave server this option captures information needed to se
270. read threads or write threads depending on the type of operation Default currently 14 For compression or incremental backup operations the buffer size is slightly more than 16MB to accommodate the headers One additional buffer is used for single file incremental backup and single file compressed backup Compressed backup compressed single file backup and uncompress apply log operations require one additional buffer for each process thread If you change the number of read write and processing threads you can experiment with changing this value so that it is slightly larger than the total number of threads specified by those other options See Section 7 1 Optimizing Backup Performance and Section 7 2 Optimizing Restore Performance for additional advice about recommended combinations of values for this and other performance related options for various hardware configurations such as RAID or non RAID storage devices read threads num_threads Command Line Format read threads NUMBER Permitted Values Type numeric Default 1 Min 1 Value Max 15 Value Specifies the number of threads to use for reading data from disk Default currently 1 This default applies to these kinds of operations copy back extract and backup If you specify a value of 0 it is silently adjusted to 1 The maximum is 15 if you supply a negative value it is silently adjusted to 15 For appl y
271. ribution Neither the name of Percona Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission of Percona Inc THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT NCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE E 9 RE2 License The following software may be included in this product RE2 Copyright c 2009 The RE2 Authors All rights reserved Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions are met Redistributions of source code must retain the above copyright notice this list of conditions and the following disclaimer Redistributions in binary form must reproduce the above copyright n
272. rk and under which the third party grants to any of the parties who would receive the covered work from you a discriminatory patent license a in connection with copies of the covered work conveyed by you or copies made from those copies or b primarily for and in connection with specific products or compilations that contain the covered work unless you entered into that arrangement or that patent license was granted prior to 28 March 2007 Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law 2 No Surrender of Others Freedom f conditions are imposed on you whether by court order agreement or otherwise that contradict the conditions of this License they do not excuse you from the conditions of this License If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations then as a consequence you may not convey it at all For example if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program 3 Use with the GNU Affero General Public License Notwithstanding any other provision of this License you have permission to link or
273. rprise Backup e Including or excluding specific tables by their names This uses the include tables or xclude tables option Each table is checked against the regular expression specified with the include tables or xclude tables option If the regular expression matches the fully qualified name of the table in 40 Making a Partial Backup the form of db_name table_name the table is included or excluded for the backup The regular expression syntax used is the extended form specified in the POSIX 1003 2 standard The options have been implemented with the RE2 regular expression library Including some or all InnoDB tables but not other table types This uses the only innodb option Leaving out files that are present in the MySQL data directory but not actually part of the MySQL instance This uses the only known file types option e Achieving a multiple of selection effects by using a combination of the above mentioned options e Backing up a selection of InnoDB tables using transportable tablespaces TTS This uses the use tts and the include tables or xclude tables or both options For syntax details on all the options involved see Section 13 8 Partial Backup and Restore Options Important A Typically a partial backup is more difficult to restore than a full backup because the backup data might not include the necessary interrelated pieces to constitute a complete MySQL instanc
274. rrent one to calculate how much redo data is generated each hour day and so on Prior to MySQL 5 5 it was common practice to keep the redo logs fairly small to avoid a long startup time when the MySQL server was killed rather than shut down normally With MySQL 5 5 and higher the performance of crash recovery is significantly improved as described in Optimizing InnoDB Configuration Variables so that you can make your redo log files bigger if that helps your backup strategy and your database workload e This type of incremental backup is not so forgiving of too low start 1sn values as the standard incremental option For example you cannot make a full backup and then make a series of incremental with redo log only backups all using the same start 1sn value Make sure to specify the precise end LSN of the previous backup as the start LSN of the next incremental backup do not use arbitrary values backups it is recommended that you always use the incremental bas option when you use the incremental with redo log onl1y option Note R To ensure the LSN values match up exactly between successive incremental e To judge whether this type of incremental backup is practical and efficient for a particular MySQL instance e Measure how fast the data changes within the InnoDB redo log files Check the LSN periodically to decide how much redo data accumulates over the course of some number of hours or days e C
275. rsion 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 durable physical medium customarily used for software interchange for a price no more than your reasonable cost of physically performing this conveying of source or 2 access to copy the Corresponding Source from a network server at no charge c Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source This alternative is allowed only occasionally and noncommercially and only if you received the object code with such an offer in accord with subsection 6b d Convey the object code by offering access from a designated place gratis or for a charge and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge You need not require recipients to copy the Corresponding Source along with the object code If the place to copy the object code is a network server the Corresponding Source may be on a different server operated by you or a third party that supports equivalent copying facilities provided you maintain clear directions next to the object code saying where to find the Corresponding Source Regardless of what server hosts the Corresponding Source you remain obligated to ensure that it is available for as long as needed to satisfy these requirements e Convey the object code using peer to peer transmission provided you inform othe
276. rtheless such tablespace files are also saved with the ibz extension inside the backup copied during an uncompressed backup Perform a compressed backup to avoid Note R When there is unused space within an InnoDB tablespace file the entire file is the storage overhead for the unused space 39 Making a Partial Backup The binary log and relay log files are compressed and saved with the bz extension when being included in a compressed backup You can only use the compress option for full backups not for incremental backups You can also select the compression algorithm to use by the compress method option and when using the ZLIB or LZMA compression algorithm the level of compression by the compress level option See Section 13 6 Compression Options for details This is a sample command for making a compressed backup mysqlbackup defaults file etc my cnf compress compress level 5 backup This is a Sample command for making a compressed single file backup mysqlbackup defaults file etc my cnf compress compress level 5 backup image backup img backup to image Next steps e Make a note of the LSN value in the message at the end of both the full and incremental backups for example in the line mysqlbackup Was able to parse the log up to lsn LSN_number You specify this value when performing incremental backups of changes that occur after this full backup e Apply the l
277. s 27 4 1 2 Grant MySQL Privileges to Backup Administrator cccceseeeeeeeeeeeeeeeeeeeeeees 29 4 1 3 Designate a Location for Backup Data 2 0 0 ceceeececeeneeee cece eeeeeeaaeeeeeeaaeeeeeeaaeeees 30 4 2 The Typical Backup Verify Restore Cycle ccccceceeeeeeeeeeeeeeeeeeeeeeeeeaaaaeeneeseeeeeeaaa 30 4 2 1 Backing Up an Entire MySQL Instance cccccceeeeeeeeee cece ee aeeeeeeeeeeeeeeeaaaaeeeees 30 4 2 2 Verifying a Backup errei cc ccececeeeee cece ee ee ence eee eres ceca eeeeeeaaeeeeeeaaeeeeseaaeeeessaaeeeeesaaees 32 4 2 3 Restoring a Database at its Original Location ccc ceeeeeeeeeeeee ee eeeeeeeeeeeeeeeeaes 32 4 3 Backup Scenarios and Examples cccceeeeeeeeeeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaae 34 4 3 1 Making a Full Backup sisesma aai eei 34 4 3 2 Making a Differential or Incremental Backup c ceeeeeeeeeeeeeeeeeeeeeeeeeeeeeaeaaea 35 4 3 3 Making a Compressed Backup ccceeeeeeeeeeeceaaeeeeeeeeeeeeeeaaaaeeeeeeeeeeeeaaaaenees 39 4 3 4 Making a Partial Backup cece cece eeeeeeeneeeeeeaa eter sean eeeeeeaaeeeeeeaaeeeeeaaeeeeeeaaeeees 40 4 3 5 Making a Single File Backup 0 cccceeeeceeeeeeeeeeeeeeeeaaeeeeeeeeeeeeeeaaaaeeeeeeeeeeeeaaa 45 4 3 6 Making an Optimistic Backup cccccceeeeeeeeeeeee ee ee ee eeeeeeeeeeeeaeaaeeneeseeeeeeaeaaeaees 49 4 3 7 Making a Back Up of In Memory Database Data 0ccceceeeeeeeeeneeee
278. s backup to image image to backup dir backup dir to image list image and extract For usage examples see Section 4 3 5 Making a Single File Backup 121 Single File Backup Options e backup image IMAGE Command Line Format backup image IMAGE Permitted Values Type file name Specify the path name of the file used for a single file operation By default the single file backup is streamed to standard output so that you can pipe it directly to other commands such as a tape backup or an ssh related network command You can optionally prefix the image name with file to signify a file I O the default For tape backups prefix the image name with sbt See Section 4 3 5 2 Backing Up to Tape for details about tape backups SrCc entry PATH Command Line Format src entry PATH Permitted Values Type path name Identifies a file or directory to extract from a single file backup This option is used with the extract command If the argument is a directory all its files and subdirectory contents are extracted No pattern matching expression is allowed for the argument Optionally you can also specify the dst entry option to extract the file or directory in a location different from its original path name For example src entry meta comments txt extracts only one file comment s txt while src entry meta extracts the entire directory tree for the
279. s data directory during a restore operation if that is not the behavior you desire use this option to skip the restoring of the relay log log bin index PATH Command Line Format log bin index F ILENAME Permitted Values Type file name Default data_dir host_name bin index For MySQL 5 5 and earlier as well as all offline backups specify the absolute path including file name and extension of the index file on the MySQL server that lists all the used binary log files if it is different from the default path given below in order to include the binary log files in the backup Default data_dir host_name bin index relay log index PATH Command Line Format relay log index FILENAME Permitted Values Type file name Default data_dir host_name relay bin index For offline backups of salve servers only specify the absolute path including file name and extension of the index file on the MySQL server that lists all the used relay log files if it is different from the default path given below in order to include the relay log files in the backup Default data_dir host_name relay bin index master info file PATH 128 Performance Scalability Capacity Options Command Line Format master info file FILENAME Permitted Values Type file name Default data_dir master info For offline backup
280. s for InnoDB tables hot backup is less disruptive to database operations than for MyISAM tables warm backup See Also hot backup InnoDB warm backup MySQL Enterprise Backup A licensed products that performs hot backups of MySQL databases It offers the most efficiency and flexibility when backing up InnoDB tables it can also back up MyISAM and other kinds of tables It is included as part of the MySQL Enterprise Edition subscription See Also Barracuda hot backup InnoDB mysqlbackup The primary command of the MySQL Enterprise Backup product Different options perform backup and restore operations See Also backup restore mysqldump A MySQL command that performs logical backups producing a set of SQL commands to recreate tables and data Suitable for smaller backups or less critical data because the restore operation takes longer than with a physical backup produced by MySQL Enterprise Backup See Also logical backup physical backup restore N non TTS backup A backup that is NOT created using transportable tablespace TTS that is not with the use tts option See Also transportable tablespace O opt file A file containing database configuration information Files with this extension are always included in backups produced by the backup operations of the MySQL Enterprise Backup product offline A type of operation performed while the database server is stopped With the MySQL Enterprise Backup product the main offli
281. s indexes when the table is dropped or truncated Each table and its associated indexes are represented by a ibd file that is deleted or emptied by these DDL operations It allows unused space within a ibd file to be reclaimed by the OPTIMIZE TABLE statement when substantial amounts of data are removed or indexes are dropped It enables partial backups where you back up some InnoDB tables and not others as discussed in Section 4 3 4 Making a Partial Backup Avoid creating indexes that are not used by queries Because indexes take up space in the backup data unnecessary indexes slow down the backup process The copying and scanning mechanisms used by mysqlbackup do not rely on indexes to do their work For example it is typically not helpful to create an index on each column of a table because only one index is used by any query Because the primary key columns are included in each InnoDB secondary index it wastes space to define primary keys composed of numerous or lengthy columns or multiple secondary indexes with different permutations of the same columns The Apply Log Phase If you store the backup data on a separate machine and that machine is not as busy the machine hosting the database server you can offload some postprocessing work the apply log phase to that separate machine Section 12 2 Apply Log Operations There is always a performance tradeoff between doing the apply log phase immediately after the initia
282. s of one or more meters that measure the progress of the operation For example Progress 100 of 1450 MB state Copying ibd files This shows that 100 megabytes of a total of 1450 megabytes have been copied or processed so far and mysqlbackup is currently copying InnoDB data files ibd files 132 Progress Report Options The progress indicator string begins with Progress followed by one or more meters measuring the progress If multiple meters are present they are separated by semicolons The different types of meters include e Total data meter It is always the first meter in the progress indicator It is in the format of DATA of TOTAL UNIT DATA and TOTAL are unsigned decimal integers and UNIT is either MB megabytes KB kilobytes or bytes 1MB 1024KB and 1KB 1024 bytes The total data meter has two slightly different meanings depending on the mysqibackup operation The amount of data copied or processed and the total amount of data to be copied or processed by the mysqlbackup operation For example Progress 200 of 1450 MB When the operation is for e g backup the indicator means 200MB is copied of 1450MB But when the operation is for e g validate or incremental it means 200MB is processed out of 1450MB e Total amount of data copied or processed and an estimate for the total that will be copied by the end of the operation The estimated total is updated as per the data on the server as the ex
283. s of salve servers only specify the absolute path including file name and extension of the information file in which a slave records information about its master if it is different from the default path given below in order to include the information file in the backup Default data_dir master info relaylog info file PATH Command Line Format relaylog info file FILENAM Permitted Values Type file name Default data_dir relay log info For offline backups of salve servers only specify the absolute path including file name and extension of the information file in which a slave records information about the relay logs if it is different from the default path given below in order to include the information file in the backup Default data_dir relay log info optimistic time DATE TIME Command Line Format optimistic time DATE TIME Permitted Values Type string Default now Perform an optimistic backup with the value specified with the option as the optimistic time a time after which the tables that have not been modified are taken as inactive tables The inactive tables are believed to be unlikely to change during the backup process The inactive tables are backed up in the optimistic phase of the backup and all other tables are backed up in the normal phase See Section 4 3 6 Making an Optimistic Backup for details on the concep
284. s used with the restore command or 2 if the full backup the incremental backup was based on or any prior incremental backup that came in between the full backup and this incremental backup has the binary log or relay log missing See Section 4 3 2 Making a Differential or Incremental Backup and Section 13 7 Incremental Backup Options for more details on incremental backups 5 2 4 Restoring Backups Created with the use tts Option There are some special requirements for restoring backups created with transportable tablespaces TTS that is created with the use tts option The destination server must be running e Make sure that the required parameters for connecting to the server port number socket name etc are provided as command line options for mysqlbackup or are specified in the client section ofa default file The destination server must be using the same page size that was used on the server on which the backup was made e The innodb_file_per_table option must be enabled on the destination server e The tables being restored must not exist on the destination server A restore fails if the InnoDB file format of a per table data file ibd file to be restored does not match the value of the innodb_file_format system variable on the destination server In that case use the force 103 option with the restore commands to change temporarily the value of innodb_file_format on the server in orde
285. se subprograms and other parts of the work The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding SOULCET The Corresponding Source for a work in source code form is that same work 2 Basic Permissions All rights granted under this License are granted for the term of copyright on the Program and are irrevocable provided the stated conditions are met This License explicitly affirms your unlimited permission to run the unmodified Program The output from running a covered work is covered by this License only if the output given its content constitutes a covered work This License acknowledges your rights of fair use or other equivalent as provided by copyright law You may make run and propagate covered works that you do not convey without conditions so long as your license otherwise remains in force You may convey covered works to others for the sole purpose of having them make modifications exclusively for you or provide you with facilities for running those works provided that you comply with the terms of this License in conveying all material for which you do not control copyright Those thus making or running the covered works for you must do so exclusively on your behalf under your direction and control on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you Conveying under any oth
286. shooting is beyond the scope of this manual 10 4 Using the MySQL Enterprise Backup Logs The mysql backup_progress table lets you monitor backup jobs as they run The mysql backup_history table lets you see the results of completed jobs Because these tables are created with the CSV storage engine you can query them from SQL or parse the text files from an application or script To skip updating these tables for a backup operation use the no history logging option backup_progress Table Each row in the backup_progress table records a state change or message from a running backup job The backup_progress table has the following columns 76 backup_history Table backup_id e tool_name e error_code error_message e current_time current state Because the CSV storage engine cannot represent NULL values directly the logs use a 1 value instead for example in the binlog_pos column if binary logging is not enabled Use the backup_id value to group together the information for a single backup operation and to correlate with the corresponding row in the backup_history table after the job is finished Use the error_code and error_message values to track the progress of the job and detect if a serious error occurs that requires stopping the backup operation Use the current_time and current_state values to measure how long each part of the backup operation takes to help with planning the time intervals for future bac
287. sion will often significantly lower the overall backup time It can result in reduced restoration time as well In general we recommend LZ4 compression over no compression for most users as LZ4 based backups often finish in a shorter time period However test out MySQL Enterprise Backup within your environment to determine what is the most efficient approach 4 3 2 Making a Differential or Incremental Backup Assuming a good portion of the data on your MySQL server remains unchanged over time you can increase the speed and reduce the required storage space for your regular backups by backing up not all the data on the server each time but only the changes to the data which have taken place over time In order to that after making first a full backup that contains all data you can do one of the following Performing a series of differential backups Each differential backup includes all the changes made to the data since the last full backup was performed To restore data up to for example time t you simply restore first the full backup and then on top of it the differential backup taken for time t Perform a series of incremental backup Each incremental backup only includes the changes since the previous backup which can itself be a full or incremental backup The first backup in an incremental 35 Making a Differential or Incremental Backup series is always then a differential backup but after that each incremental ba
288. so avoid the performance overhead of saving a set of backup files and then bundling them into an archive for transport to another server or storage device For details see Section 4 3 5 1 Streaming the Backup Data to Another Device or Server When streaming backup data to tape you typically do not compress the backup because the CPU overhead on the database server to do the compression is more expensive than the additional storage space on the tape device When streaming backup data to another server you might compress on the original server or the destination server depending on which server has more spare CPU capacity and how much network traffic the compression could save Or you might leave the backup data uncompressed on the destination server so that it is ready to be restored on short notice For disaster recovery when speed to restore the data is critical you might prefer to have critical backup data already prepared and uncompressed so that the restore operation involves as few steps as possible It is during a disaster recovery that speed is most critical For example although a logical backup performed with the mysqldump command might take about the same time as a physical backup with at least for a small database the MySQL Enterprise Backup restore operation is typically faster Copying the actual data files back to the data directory skips the overhead of inserting rows and updating indexes that comes from replaying the SQ
289. ssed backup The binary log file and relay log files in the case of a slave server are now compressed when they are being included in a compressed backup and decompressed during a restore e Copying of the binary and relay Logs can now be skipped during a restore The skip binlog and skip relaylog options can now be used to skip the copying back of the binary log and relay log onto a server during a restore This is particularly useful for users who do not want those logs appearing in the restored server s data directory as that is always the location to which mysqlbackup will restore them regardless of their original locations on the backed up server Using the force 103 option to overwrite server data during a restore The force 103 option can now be used during the restore of a full backup to overwrite existing data ina non empty target directory See the description of the force 103 option for details 21 22 Part Il Using MySQL Enterprise Backup Table of Contents 4 Backing Up a Database Server cce cece ccceeeeeee cece ee ee ae eee teen eres ee ae aaa teeter ee sees aaaaaeeeeeeeeeeeaaaaeneeeeeeeees 27 4 1 Betore the First BACKUP 22 eiceeccectetee sont ienei en estat cancel ent deat ect deed shinwent ect E 27 4 1 1 Collect Database Information 0 cccceceeeee cece eee eeee cece sees ae aaeeeeeeeeeeeeeeaaaaeeneeeeeeeeeaea 27 4 1 2 Grant MySQL Privileges to Backup Administra
290. ster my cn file and comment out 1og bin so that the slaves do not receive twice the binary log needed to recover the master Replication in the slaves must be stopped temporarily while you pipe the binary log to the master In the slaves do mysql gt STOP SLAVE Start the master mysqid on the restored backup mysqld InnoDB Doing recovery scanned up to log sequence number 0 64300044 InnoDB Last MySQL binlog file position 0 5585832 file name omnibook bin 002 InnoDB prints the binary log file omnibook bin 002 in this case and the position 5585832 in this case it was able to recover to Pipe the remaining of the binary log files to the restored backup For example if there are two more binary log files omnibook bin 003 and omnibook bin 004 that come after omnibook bin 002 pipe them all with a single connection to the server see Point in Time Incremental Recovery Using the Binary Log for more instructions on using mysqlbinlog mysqlbinlog start position 5585833 mysqldatadir omnibook bin 002 mysqldatadir omnibook bin 003 mysqldatadir omnibook bin 004 mysql The number of remaining binary log files varies depending on the length of the timespan between the last backup and the time to which you want to bring the database up to date The longer the timespan the more remaining binary log files there may be All the binary log files containing all the continuous binary log positions in that timespa
291. t backups include files from all storage engines use tts with minimum locking with full locking Command Line Format use tts with minimum locking with full locking Permitted Values Type enumeration Default with minimum locking Valid with minimum locking Values itn full locking Enable selective backup of InnoDB tables using transportable tablespaces TTS This is to be used in conjunction with the include tables and xclude tables options for selecting the InnoDB tables to be backed up by regular expressions Using TTS for backups offers the following advantages e Backups can be restored to a different server e The system tablespace is not backed up saving disk space and I O resources e Data consistency of the tables is managed by MySQL Enterprise Backup However the option has the following limitations e Supports only MySQL version 5 6 and after as earlier versions of MySQL do not support TTS e Can only backup tables that are stored in their own individual tablespaces i e tables created with the innodb_file_per_table option enabled Cannot back up partitioned tables for MySQL 5 7 3 or before e Cannot be used for incremental backups Does not include the binary log or the relay log in the backup There are two possible values for the option e with minimum locking Hot copies of the selected tables are backed up and the tables are then locked in read o
292. t use cases and command samples for an optimistic backup Accepted formats for specifying the option include now This includes all tables into the optimistic phase of the backup process It is the default value for the option when no value is specified e Number Unit Indicates the optimistic time as a time at a certain duration into the past Unit can be any one of years months hours and minutes Some examples for option strings in this format include 5years 2days 13months 23hours and 35minutes A date time format in any of the following forms YYMMDD YYYYMMDD YYMMDDHHMMSS YYYYMMDDHHMMSSYY MM DD YYYY MM DD YY MM DD or HH MM SSYYYYMMDDTHHMMSS as designated by the ISO 8601 standard When both the opt imistic time and the optimistic busy tables options are used and they come into conflict on determining which tables are to be backed up in the optimistic phase optimistic busy tables takes precedence over optimistic time 129 Message Logging Options optimistic busy tables REGEXP Command Line Format optimistic busy tables REGEXP Permitted Values Type string Perform an optimistic backup using the regular expression specified with the option to select tables that will be skipped in the first phase of an optimistic backup because they are likely to be modified during the backup process Tables whose fully qualified names in the form of database_name
293. t every page in the data files corresponds to the same log sequence number of the InnoDB log This phase also creates new ib_logfiles that correspond to the data files The mysqibackup option for turning a raw backup into a prepared backup is appl y log You can run this step on the same database server where you did the backup or transfer the raw backup files to a different system first to limit the CPU and storage overhead on the database server Note R Since the apply log operation does not modify any of the original files in the backup nothing is lost if the operation fails for some reason for example 53 Performing a Restore Operation insufficient disk space After fixing the problem you can safely retry apply log and by specifying the force 103 option which allows the data and log files created by the failed appl y 1og operation to be overwritten For simple backups which are not compressed and non incremental you can combine the initial backup and the apply log steps using the backup and apply log command You can also perform apply log and copy back which restores the prepared backup with a single copy back and apply log command Example 5 1 Applying the Log to a Backup This example runs mysqlbackup to roll forward the data files so that the data is ready to be restored mysqlbackup backup dir export backups 2011 06 21__8 36 58 apply log That command creates InnoDB log files 1b_logfil
294. t is a crucial parameter required for most kinds of backup and restore operations The option is used differently for different operations and under different situations 107 Backup Repository Options For backup to a directory Use backup dir to specify the directory to store the backup data and metadata including the mysqibackup message log the start and end LSN and so on The directory specified by backup dir cannot be a subdirectory of the directory specified by datadir When the with timestamp option is also specified an additional level of subdirectory with the timestamp in its name is created under backup dir see description for the with timestamp option for details Unless the with timestamp option is used the directory specified by backup dir must be empty or the backup operation will fail with an error For backup to a single file including incremental compressed encrypted and cloud backups Use backup dir to supply a temporary folder to save the backup metadata including the mysqlbackup message log the start and end LSN and so on and some temporary output The backup data together with a copy of the metadata will be stored in a singe file whose name is specified with the backup image option Note that however if backup image does not give a full path name mysqlbackup will actually take the value of backup image as a path relative to the directory specified by backup
295. t the slave server Replication starts For more information on the GTIDs see GTID feature 6 2 Backing up and Restoring a Slave Database To backup a slave database add the slave info option to your backup command To restore the backup on a slave server follow the same steps outlined in Section 6 1 Setting Up a New Replication Slave details whenever the SQL thread for the slave is stopped for example during a slave shutdown that has to occur when you restore a backup to a slave server Warning O In a statement based replication SBR setting see Replication Formats for all temporary tables that are open then will not get replicated on the slave see 62 Restoring a Master Database Replication and Temporary Tables for details That means it is not always safe to backup a slave server in an SBR setting with mysqlbackup if temporary tables might be created on the master as the temporary tables might be missing from the backup making it inconsistent Therefore only use mysqlbackup with an SBR slave if you know no temporary tables are created on the master 6 3 Restoring a Master Database To fix a corruption problem in a replication master database you can restore the backup taking care not to propagate unnecessary SQL operations to the slave servers 1 Using the backup of the master database do the appl y log operation shut down the database and do the copy back operation Edit the ma
296. t up an identical slave server It creates a file meta ibbackup_slave_info inside the backup directory containing a CHANGE MASTER statement with the binary log position and name of the binary log file of the master server This information is also printed in the mysqlbackup output To set up a new slave for this master restore the backup data on another server start a slave server on the backup data and issue a CHANGE MASTER command with the binary log position saved in the ibbackup_slave_info file See Section 6 1 Setting Up a New Replication Slave for instructions Note R Only use this option when backing up a slave server Its behavior is undefined when used on a master or non replication server This option is not compatible with the no locking option using both options together will make mysqlbackup throw an error This option is not compatible with the only innodb or only innodb with frm options s suspend at end This option pauses the mysqlbackup command when the backup procedure is close to ending It creates a file called ibbackup_suspended in the backup log group home directory and waits until you 137 Options for Special Backup Types delete that file before proceeding This option is useful to customize locking behavior and backup of non InnoDB files through custom scripting All tables are locked before suspending putting the database into a read only state unless you turn o
297. t ways to set up cron jobs for various types of schedules 51 Making Backups with a Distributed File System DFS or Storage Access Network SAN For Windows platforms Use the Task Scheduler for the purpose Check the documentation for you Windows platform for instructions 4 4 Making Backups with a Distributed File System DFS or Storage Access Network SAN When system administrators attempt to set up MySQL and MySQL Enterprise Backup in an environment that uses a distributed file system DFS or a storage access network SAN the MySQL server the server s data directory MySQL Enterprise Backup and the backup directory may end up existing on different physical servers When that happens the operations of mysqlibackup might be impacted The operation most likely to be adversely affected is hot backup the success of which depends on 1 Each page of a data file is copied consistently that is all the bytes in the page correspond to the same LSN 2 No copied page is older than the time that marks the beginning of the temporal duration the backup is supposed to cover 3 The redo log is copied consistently meaning a continuous segment of redo log is copied and it includes all the changes from the beginning of the temporal period that the backup is to cover until the end of the backup operation Each block of the copied redo log has to be consistent Condition 1 is easily achievable with most DFSs or SANs of reasonable perf
298. ta directory MySQL configuration file or mysqld startup script Used to retrieve files from the database instance during backup operations and to copy files back to the database instance during restore operations Automatically retrieved from database connection for hot and warm backups and taken from MySQL configuration file for cold backups ID and password of privileged MySQL user You record this during installation of your own databases or get it from the DBA when backing up databases you do not own Not needed when doing an offline cold backup which works directly on the files using OS level file permissions For cold backups you log in as an administrative user Specified via the password option of the mysqlbackup Prompted from the terminal if the password option is present without the password argument Path under which to store backup data You choose this See Section 4 1 3 Designate a Location for Backup Data for details By default this directory must be empty for mysqlbackup to write data into it to avoid overwriting old backups or mixing up data from different backups Use the with timestamp option to automatically create a subdirectory with a unique name when storing multiple sets of backup data under the same main directory Owner and permission information for backed up files for Linux Unix and OS X systems In the MySQL data directory If you do the
299. ta has been restored to a desired point in time Alternatively you can bring your full backup up to date with your incremental backup First apply to the full backup any changes that occurred while the backup was running mysqlbackup backup dir full backup 2010 12 08 _ 17 14 11 apply log Many lines of output lt 101208 17 15 10 mysqlbackup Full backup prepared for recovery successfully 56 Restoring Backups Created with the use tts Option 101208 17 15 10 mysqlbackup mysqlbackup completed OK Then we apply the changes from the incremental backup mysqlbackup incremental backup dir incr backup 2010 12 08_17 14 48 backup dir full backup 2010 12 08_17 14 11 apply incremental backup many lines of output 101208 17 15 12 mysqlbackup mysqlbackup completed OK Now the data files in the full backup directory are fully up to date as of the time of the last incremental backup You can keep updating it with more incremental backups so it is ready to be restored anytime When an incremental backup is being restored using either the copy back and apply log or apply incremental backup command the binary log and also the relay log in the case of a slave server if included in the incremental backup is also restored to the target server by default This default behavior is overridden when either 1 the skip binlog option or the skip relaylog option for the relay log i
300. table The table mysql backup_progress that holds details of running backup operations When a backup job finishes the details are recorded in the history table See Also backup history table R raw backup The initial set of backup data not yet ready to be restored because it does not incorporate changes that occurred while the backup was running The apply operation transforms the backup files into a prepared backup that is ready to be restored See Also apply prepared backup redo log A set of files typically named ib_logfiled and ib_logfilel that record statements that attempt to change data in InnoDB tables These statements are replayed automatically to correct data written by incomplete transactions on startup following a crash The passage of data through the redo logs is represented by the ever increasing LSN value The 4GB limit on maximum size for the redo log is raised in MySQL 5 6 See Also LSN regular expression Some MySQL Enterprise Backup features use POSIX style regular expressions for example to specify tables databases or both to include or exclude from a partial backup Regular expressions require escaping for dots in filenames because the dot is the single character wildcard no escaping is needed for forward slashes in path names When specifying regular expressions on the command line surround them with quotation marks as appropriate for the shell environment to prevent expansion of characters such as asterisks
301. table_name are matched by the regular expression are taken as busy tables which will be backed up in the second or the normal phase of the backup Tables whose fully qualified names are NOT matched by the regular expression are taken as inactive tables which will be backed up in the first or the optimistic phase of the backup See Section 4 3 6 Making an Optimistic Backup for details on the concept use cases and command samples for an optimistic backup MySQL Enterprise Backup will throw an error if the option is used but no regular expression is supplied with it When both the opt imistic time and the optimistic busy tables options are used and they come into conflict on determining which tables are to be optimistic optimistic busy tables takes precedence over opt imistic time 13 11 Message Logging Options mysqlbackup writes important progress and error information to the stderr stream The information is often very valuable for tracking down problems that occur during an operation Starting from MySQL Enterprise Backup 3 9 the output to the stderr stream is also saved to a log file by default for most mysqlbackup operations so that the error information can be easily accessed in any debug process The message logging works like a tee process on a Unix like system in which the output of a program is split to be both displayed and saved to a file The log file thus produced is named in the fol
302. tart and stop times but by their corresponding binary log positions mysqlbinlog start posit ion binary log position corresponding Lo t Stop position binary log position corresponding to tp binlog 000005 binlog 000006 binlog 000007 mys UOC Note that you need to pipe all the binary log files in a single connection to the server You can also dump all the SQL activities to a single file first and then pipe or play the file to the mysql client For more tips on using the binary log for point in time recovery see Point in Time Incremental Recovery Using the Binary Log 5 4 Restoring a Backup with a Database Upgrade or Downgrade You can facilitate a server upgrade or downgrade by using MySQL Enterprise Backup to make a backup of your server data restore it to a data directory and start a different version of MySQL server on the old data However you may encounter technical challenges during a server upgrade or downgrade and it is beyond the function of MySQL Enterprise Backup as a backup tool to ensure a successful server upgrade or downgrade Users interested in the topic are advised to consult the MySQL server manual especially the Upgrading MySQL and Downgrading MySQL sections Here are a number of things that users should pay attention to when restoring a backup with a database upgrade or downgrade Restoring a database to an older MySQL version i e server downgrading should only be performed
303. than client server network traffic The database communication controlled by the protocol option is low volume For example mysqlbackup retrieves information about database parameters through the database connection but not table or index data Data Size If certain tables or databases contain non critical information or are rarely updated you can leave them out of your most frequent backups and back them up on a less frequent schedule See Section 13 8 Partial Backup and Restore Options for information about the relevant options and Section 4 3 4 Making a Partial Backup for instructions about leaving out data from specific tables databases or 67 The Apply Log Phase storage engines Partial backups are faster because they copy compress and transmit a smaller volume of data To minimize the overall size of InnoDB data files consider enabling the MySQL configuration option innodb_file_per_table This option can minimize data size for InnoDB tables in several ways It prevents the TnnoDB system tablespace from ballooning in size allocating disk space that can afterwards only be used by MySQL For example sometimes huge amounts of data are only needed temporarily or are loaded by mistake or during experimentation Without the innodb_file_per_table option the system tablespace expands to hold all this data and never shrinks afterward It immediately frees the disk space taken up by an InnoDB table and it
304. the data during planned maintenance or when disaster strikes For example here are factors to consider for some of the key MySQL Enterprise Backup features e Parallel backups are the default in MySQL Enterprise Backup 3 8 a major performance improvement over earlier MySQL Enterprise Backup releases The read process and write are the primary sub operations of all MEB operations For example in a backup operation MySQL Enterprise Backup first reads the data from the disk then processes this data writes the data to disk and reads the data again for verification MySQL Enterprise Backup ensures that these sub operations are independent of each other and run in parallel to gain performance improvement Read process and write sub operations are performed in parallel using multiple threads of the same kind multiple read threads multiple process threads and multiple write threads resulting in better performance The performance improvement is typically greater when RAID arrays are used as both source and target devices and for compressed backups which can use more CPU cycles in parallel Parallel backup employs block level parallelism using blocks of 16MB Different threads can read process and write different 16MB chunks within a single file Parallel backup improves the performance of operations whether the instance contains a single huge system tablespace or many smaller tablespaces represented by ibd files created in the innodb_file_
305. the global files are read defaults file Only read default options from the given file defaults group suffix disable manifest Also read option groups with the usual names and a suffix of str Disable generation of manifest files for a backup operation dst entry Used with single file backups to extract a single file or directory to a user specified path encrypt Encrypt backup image and write it in an MEB Secure File exclude tables exec when locked Exclude in backup tables whose names match the regular expression REGEXP Execute the specified utility when all tables are locked near the end of the execution force 103 Force overwriting of data log or image files depending on the operation help Display help host Host name to connect include Legacy Backup only those per table innodb data files which match the regular expression REGEXP include tables Include in backup tables which match the regular expression REGEXP incremental Specifies that the associated backup or backup to image operation is incremental incremental backup dir incremental base Specifies the location under which to store data from an incremental backup The specification of base backup for incremental option incremental with redo log only Specifies the incremental backup of InnoDB tables to be based on copying redo log to the backup without i
306. the target directory for restoration might be needed before preforming a full restore for example when the backup data is used to set up a new MySQL server or to replace all data of an existing MySQL server See Section 5 2 Performing a Restore Operation 55 for details There are some special requirements when restoring backups created with the use tts option see Section 5 2 4 Restoring Backups Created with the use tts Option for details copy back and apply log 89 Restore Operations In a single step restores a single file backup specified by the backup image option or a backup from the directory specified by the backup dir option to a server s data directory and performs an apply log operation to the restored data to bring them up to date Comparing with a multi step approach for restoring a single file backup which typically consists of performing the successive steps of extract uncompress apply log and copy back for restoring compressed image or extract apply log and copy back for uncompressed image the command makes the restoration process simpler and faster and also saves the disk space required The following are some special requirements for different kinds of backup restoration using copy back and apply log e To restore a compressed directory or image include the uncompress option in the command line e To restore a single file backup besides specifying the location of t
307. ting information on items in the bucket e s3 ListBucketMultipartUploads For listing multipart uploads in progress to the bucket e s3 GetOb ject For retrieving objects from the bucket e s3 PutObject For adding objects to the bucket sd cloud object key S3_OBJECT_KEY The Amazon S3 object key for the backup image cloud access key id 953_KEY ID AWS access key ID for logging onto Amazon S3 cloud secret access key S3_ACCESS KEY AWS secret access key for the AWS access key id specified with cloud access key id s cloud aws region S3_REGION Region for Amazon Web Services that mysqlbackup accesses for S3 Options used only for OpenStack Swift using them when the argument for cloud service is anything other than openstack will cause mysqlbackup to throw an error e cloud container SWIFT_CONTAINER The Swift container for the backup image s cloud object SWIFT_OBJECT The Swift object for the backup image Note that names of objects in a container have to be unique cloud user id SWIFT_OR_KEYSTONE_USER User ID for accessing Swift The user credentials are authenticated using the Swift TempAuth identity system when the cloud tempauth url 137 option is used and by the OpenStack Keystone identity service when the cloud identity url 137 option is used e cloud password SWIFT_OR_KEYSTONE_PASSWORD 136 Options for Special Backup Types Passwo
308. tion must be ina format that as publicly documented and with an implementation available to the public in source code form and must require no special password or key for unpacking reading or copying 7 Additional Terms Additional permissions are terms that supplement the terms of this License by making exceptions from one or more of its conditions Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License to the extent that they are valid under applicable law If additional permissions apply only to part of the Program that part may be used separately under those permissions but the entire Program remains governed by this License without regard to the additional permissions When you convey a copy of a covered work you may at your option remove any additional permissions from that copy or from any part Ole AXE e Additional permissions may be written to require their own removal in certain cases when you modify the work You may place additional permissions on material added by you to a covered work for which you have or can give appropriate copyright permission Notwithstanding any other provision of this License for material you add to a covered work you may if authorized by the copyright holders of that material supplement the terms of this License with terms a Disclaiming warranty or limiting liability differently from the terms of sections 15 an
309. to perform the backup again using some non default settings for the following mysqibackup options e page reread time MS Try set the value to for example 0 05 for faster rereads during checksum failures page reread count retry_limit Try set the value to for example 1000 to allow more rereads during checksum failures before MySQL Enterprise Backup gives up and throws an error Scrambled data in memory can cause the problem even though the data on disk is actually uncorrupted Reboot the database server and the storage device to see if the problem persists If the problem persists after the database server and the storage device have been restarted you might really have a corruption on your disk You might consider restoring data from an earlier backup and roll forward the recent changes to bring the database back to its current state e If you want to make MySQL Enterprise Backup finish a backup anyway before you go and investigate the root cause of the issue you can rewrite the checksum values on the disk by running the innochecksum utility on the server innochecksum no checksum write crc32 The option no checksum disable the verification function of the tool and the option write crc32 makes innochecksum rewrite the checksum values on the disk IMPORTANT Do not treat corruption problems as a minor annoyance Find out what is wrong with the system that causes the corruption however such trouble
310. tor 0 ccccecccceeeeeeeeeeeeeeaeeeeeeeeeeeees 29 4 1 3 Designate a Location for Backup Data cccccceceeeeeeeee ee ee ee eeeeeeeeeeeeaeaaeeneeeeeeeeeaeaaea 30 4 2 The Typical Backup Verify Restore Cycle ccecececcceeeeeeeeeeeee ee aeeeeeeeeeeeeeeaaaaeeeeeseeeeeeaaa 30 4 2 1 Backing Up an Entire MySQL Instance ccccceceeeee cece eeeeeeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeeaes 30 4 2 2 Verifying a BACkUp cencerro neces ag EE ARN 32 4 2 3 Restoring a Database at its Original Location cceeeeee ee eeeeeeeeeeeeeeeeaeeaeeeeeeeeeeeeaes 32 4 3 Backup Scenarios and Examples 0 ccccccececceeeeeeeeeeeeese aaa eeeeeeeeeeeeaaeaeeeeeeeeeeeeaaaaeeeseeeeeees 34 4 3 1 Making a Full Backup 0 0 cccccececeeeeeeeeeee settee eeeeeeeeee ee aaaaeeeeeeeeeeeeaeaaaaneeeeeeeeeaeaaea 34 4 3 2 Making a Differential or Incremental Backup ccceeeeeeeeeeeeeeeeeeeeeeeaaeaeeeeeeeeeeeeaaa 35 4 3 3 Making a Compressed Backup ceseeeeeeeeeaeeeeeeeeeeeeeee ae aaeaeeeeeeeeeeeeaaaaneneeeeeeseeaaa 39 4 3 4 Making a Partial Backup cc ecccceeceeneuae cece sees cece E EENE aE 40 4 3 5 Making a Single File Backup cccccccceeeeeeeeeeeee ee aa ea eeeeeeeeeeeeaeaaeaneeeeeeeeeaeaaaneneeeees 45 4 3 6 Making an Optimistic Backup cccceceeeeeeeee ee ee ee ae ete eeeeeeee ee aaeaeeeeeeeeeeeeaaaaeeeeeneeeees 49 4 3 7 Making a Back Up of In Memory Database Data 0
311. ture is primarily intended for InnoDB tables or non InnoDB tables that are read only or rarely updated Incremental backups detect changes at the level of pages in the InnoDB data files as opposed to table rows each page that has changed is backed up Thus the space and time savings are not exactly proportional to the percentage of changed InnoDB rows or columns 37 Making a Differential or Incremental Backup For non InnoDB files the entire file is included in an incremental backup if that file has changed since the previous backup which means the savings for backup resources are less significant when comparing with the case with InnoDB tables You cannot perform incremental backups with the compress option Examples of Incremental Backups This example uses mysqibackup to make an incremental backup of a MySQL server including all databases and tables We show two alternatives one using the incremental base option and the other using the start 1sn option With the incremental base option you do not have to keep track of LSN values between one backup and the next Instead you can just specify the directory of the previous backup either full or incremental and mysqibackup figures out the starting point for this backup based on the metadata of the earlier one Because you need a known set of directory names you might want to use hardcoded names or generate a sequence of names in your own backup script rat
312. ut copying the actual data files For example the mysqldump command produces a logical backup because its output contains statements such as CREATE TABLE and INSERT that can re create the data Contrast with physical backup See Also backup physical backup 178 LSN Acronym for log sequence number This arbitrary ever increasing value represents a point in time corresponding to operations recorded in the redo log This point in time is regardless of transaction boundaries it can fall in the middle of one or more transactions It is used internally by InnoDB during crash recovery and for managing the buffer pool In the MySQL Enterprise Backup product you can specify an LSN to represent the point in time from which to take an incremental backup The relevant LSN is displayed by the output of the mysqlibackup command Once you have the LSN corresponding to the time of a full backup you can specify that value to take a subsequent incremental backup whose output contains another LSN for the next incremental backup See Also crash recovery hot backup incremental backup redo log M MRG file A file containing references to other tables used by the MERGE storage engine Files with this extension are always included in backups produced by the mysqlbackup command of the MySQL Enterprise Backup product MYD file A file that MySQL uses to store data for a MyISAM table See Also MYI file MYI file A file th
313. various hardware configurations such as RAID or non RAID storage devices write threads num_threads Command Line Format write threads NUMBER Permitted Values Type numeric Default 1 Min 1 Value Max 15 Value Specifies the number of threads to use for writing data to disk Default currently 1 This default applies to these kinds of operations copy back extract and backup It is ignored when you use any of the single file backup options 1 ist image or validate If you specify a value of 0 it is silently adjusted to 1 The maximum is 15 if you supply a negative value it is silently adjusted to 15 For appl y 1log operations the number of write threads is always 0 regardless of this option setting See Section 7 1 Optimizing Backup Performance and Section 7 2 Optimizing Restore Performance for advice about recommended combinations of values for read threads process threads and write threads for various hardware configurations such as RAID or non RAID storage devices e limit memory MB 125 Performance Scalability Capacity Options Command Line Format limit memory MB Permitted Values Type numeric Default 100 for apply log without uncompression 300 for other operations Min 0 Value Max 999999 Value Specify maximum memory in megabytes that can be used by mysqlbackup Formerly applied only to a
314. ve Abort backup and remove the backup directory e warn Write a warning message every 30 seconds and retry backup until disk space becomes available Default abort skip unused pages Skip unused pages in tablespaces when backing up InnoDB tables This option is applicable to the backup and backup to image operations but not to incremental backups The option is ignored by the backup and apply log operation Note that backups created with the skip unused pages option cannot be restored using copy back and apply log Unused pages are free pages often caused by bulk delete of data By skipping the unused pages during backups this option can reduce the backup sizes and thus the required disk space and I O resources for the operations However subsequent apply 1log operations on the backups will take more time to complete as the unused pages are inserted back into the tables during the operations skip binlog Skip including the binary log files in the backup during a backup operation or skip copying the binary log files onto a server during a restore operation Binary log files together with the binary log index file are included by default for all kinds of online backups full incremental compressed partial single file etc See Section 1 4 Files that Are Backed Up for details Use this option to skip backing up binary logs if resource performance or other issues 127 Performance Scalability C
315. ve file t gz archived with tar and compressed with gzip or as a platform specific installer Installing on Unix and Linux Systems For all Linux and Unix systems the product is available as a tgz file Unpack this file as follows tar xvzi package tgz mysqlbackup is unpacked into a subdirectory You can either copy them into a system directory preserving their execute permission bits or add to your SPATH setting the directory where you unpacked it libz so 5 which can be installed on your system by installing for example the Note R On FreeBSD 10 1 there is a dependency for mysqlbackup on the shared library compat8x libraries For certain Linux distributions the product is also available as an RPM archive When you install the RPM using the command sudo rpm i package_name rpm the mysqlbackup Client is installed in the directory opt mysql meb 3 12 You must add this directory to your PATH setting Installing on Windows Systems The product can be installed together with other MySQL products with the MySQL Installer for Windows It can also be installed separately with either an individual msi installer or zip file When installing with a msi installer specify the installation location preferably under the same directory where other MySQL products have been installed Choose the option Include directory in Windows PATH so that you can run mysqlbackup from any directory When installing with a zip file simp
316. ver Typically used to service user queries to minimize the query load on the master With MySQL Enterprise Backup you might take a backup on one server and restore on a different system to create a new slave server with the data already in place You might also back up data from a slave server rather than the master to minimize any slowdown of the overall system See Also master replication streaming A backup technique that transfers the data immediately to another server rather than saving a local copy Uses mechanisms such as Unix pipes Requires a single file backup with the destination file specified as standard output See Also single file backup suspend An optional stage within the backup where the MySQL Enterprise Backup processing stops to allow for user specific operations to be run The mysqlbackup command has options that let you specify commands to be run while the backup is suspended Most often used in conjunction with backups of InnoDB tables only where you might do your own scripting for handling frm files See Also frm file InnoDB 183 system backup to tape An API for media management software Abbreviated SBT Several mysqibackup options with sbt in their names pass information to media management software products such as Oracle Secure Backup See Also Oracle Secure Backup SBT system tablespace By default this single data file stores all the table data for a database as well as all the metadat
317. versions may give you additional or different permissions However no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version 15 Disclaimer of Warranty 162 GNU General Public License Version 3 0 29 June 2007 and GCC Runtime Library Exception Version 3 1 31 March 2009 THERE IS NO WARRANTY FOR THE PROGRAM TO THE EXTENT PERMITTED BY APPLICABLE LAW EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND OR OTHER PARTIES PROVIDE THE PROGRAM AS IS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESSED OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS ROR A PARTICULAR PURPOSES Tell TINIE LIS UIT SS AS ARO THE OPAC IL IEG AND PERFORMANCE OF THE PROGRAM IS WITH YOU SHOULD THE PROGRAM PROVE DEFECTIVE YOU ASSUME THE COST OF ALL NECESSARY SERVICING REPAIR OR CORRECTION 6 Limitation of Liability N NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER OR ANY OTHER PARTY WHO MODIFIES AND OR CONVEYS THE PROGRAM AS PERMITTED ABOVE BE LIABLE TO YOU FOR DAMAGES INCLUDING ANY GENERAL SPECIAL INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS EVEN
318. when the original and the final server versions are in the same release series for example going from 5 5 30 to 5 5 29 Downgrading to a lower series for example from 5 6 33 to 5 5 33 might cause server crashes or data corruption Restoring a database to a newer MySQL version i e server upgrading requires the following steps the skipping of which might crash the target server e Back up the data on the older server e Restore the data to the directory you plan to use as the newer server s data directory by running a copy back and apply log operation on the backup e Restart the older server using the intended data directory for the newer server as its own data directory With this step the older server prepares the data for an upgrade by performing some clean up steps on the data similar to what the server would do during a crash recovery e Perform a slow shutdown for the older server by issuing the SET GLOBAL innodb_fast_shutdown 0 statement and then shutting the server down This will ensure that all dirty pages are flushed and hence there will be no redo log processing for the newer server Install the newer server 59 Restoring a Backup with a Database Upgrade or Downgrade Start the newer server e Run upgrade steps as documented in the MySQL reference manual on the restored data Make sure the mysql_upgrade that comes with your newer server is applied e Check data 60 Chapter 6 Using M
319. x_fadvise system call 6 prepared backup 7 53 181 privileges 29 process threads option 125 progress indicator 131 progress table 182 progress interval 134 R RAID 65 68 raw backup 7 53 182 read threads option 124 redo log 182 regular expression 182 relay log 182 relay log index 128 relaylog info file 129 release notes 151 replication 61 62 63 182 repository 182 restore 182 restoring a backup 53 at original location 32 backup created with the use tts option 57 examples 54 mysqlbackup options 89 overview 17 point in time recovery 58 preparation 53 189 row format 182 S SBT 183 sbt database name option 123 sbt environment option 123 sbt lib path option 123 selective backup 183 selective restore 183 server 183 server repository 183 show progress 131 single file backup 6 45 93 121 183 skip binlog 127 skip relaylog 128 skip unused pages 127 slave 61 62 183 slave info option 137 sleep option 126 space for backup data 6 src entry option 122 start Isn option 114 storage access network 52 streaming 47 183 streaming backups 6 suspend 183 suspend at end option 137 system backup to tape 184 system tablespace 7 184 T table 184 tablespace 184 tape backups 48 73 third party contributions 153 transportable tablespace 184 TRG file 7 TRG file 184 TRN file 7 troubleshooting fo
320. xt log file on the restored server See the description for innodb_log_file_size in the MySQL server manual The value for this parameter saved as innodb_log_file_size inthe backup my cnf file is derived as follows e Use the backup_innodb_log_file_size value from command line or configuration file if specified e Else use the innodb_log_file_size value from the backed up server if it is an online backup e Else use the specified innodb_log_file_size value from the mysqlibackup command line or configuration file e backup_innodb_page_size SIZE 110 Metadata Options Specifies for an offline backup the page size for all InnoDB tablespaces on the restored server This option should be specified carefully because the page size must be the same as that of the backed up MySQL instance or the backup could become useless For an online backup the value is taken from the value of the innodb_page_size option on the backed up server Value of this option is saved in the backup my cnf file to be used for restoring the database backup_innodb_undo_logs NUMBER Specifies for an offline backup the number of rollback segments in the InnoDB system tablespace on the restored server This option should be specified carefully because the value must be the same as that of innodb_undo_logs on the backed up MySQL instance or the backup could become useless For an online backup the value for the parameter is taken from the value of the i
321. y dat adir unless another location is specified using the innodb_log_group_home_dir option during restore The value of the parameter is derived as follows If backup_innodb_log_group_home_dir is not specified its value will be backup dir datadir e If backup_innodb_log_group_home_dir is an absolute path its value is used as is e If backup_innodb_log_group_home_dir is a relative path the path is taken to be relative to that is underneath backup dir An empty string for the option produces an error e backup_innodb_undo_directory PATH 109 Backup Repository Options The relative or absolute directory path where separate tablespaces are created for the InnoDB undo logs during the backup When unspecified the option takes up the same value as backup_innodb_log_group_home_dir specify this option only if you want to put the undo logs at some other location If the value of the parameter is different from backup dir datadir itis stored in the backup my cnf file as innodb_undo_directory for information so that mysqlbackup can understand the structure of the backup when it performs various operations on the backup This parameter is applicable only for backup operations during a restore the InnoDB undo log tablespaces are restored under the data directory specified by datadir unless another location is specified by the innodb_undo_directory option during restore e with timestamp
322. y kind provided that the above copyright notice and this paragraph are included on all such copies and derivative works However this 171 zlib License document itself may not be modified in any way such as by removing the copyright notice or references to the Internet Society or other Internet organizations except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed or as required to translate it into languages other than English The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns This document and the information contained herein is provided on an AS IS basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society E 12 zlib License The following software may be included in this product zlib Oracle gratefully acknowledges the contributions of Jean loup Gailly and Mark Adler in creating the zlib general purpose compression library which is used in this product zlib h interface of the
323. y updated to point to the files locations in the backup directory is included into the backup under the datadir directory The binary log files are compressed and saved with the bz extension when being included in a compressed backup The binary log files and the index file when included in a backup are always copied into the restored server s data directory during a restore operation Use the skip binlog option to skip the restoring of the binary log E Note If any binary log files are missing on the server you are backing up you should use the skip binlog option to avoid mysqlbackup throwing an error for 11 Files that Are Backed Up File Name Pattern or Extension Relation to Original Data Files Notes the missing files relay log files Relay log files from a slave server which are included in a backup of a slave server by default except when the backup is created with the use tts option Their inclusion saves the time and resources required for fetching the relay logs from the master when the slave is being restored Saved under the datadir directory under the backup directory Use the skip relaylog option to exclude relay logs in the backup For offline backup use the relay log index option to specify the absolute path of the index file on the MySQL server that lists all the used relay log files if it is different from the default valu
324. ySQL Enterprise Backup with Replication Table of Contents 6 1 Setting Up a New Replication Slave ccceceeceeeece cence eeeeeeee ee ae aa eaeeeeeeeeeeseaaeaeeeeeeeeeeeaaaaeneeeeeeees 61 6 2 Backing up and Restoring a Slave Database 0 cccceceeeeeeneneeeeeeeeeeeeaeaaeeeeeeeeeeeeaeaaeateeeereeeeaeaae 62 6 3 Restoring a Master Database seesinane E ENAERE ANESSE ARERR AEN 63 Backup and restore operations are especially important in systems that use MySQL replication to synchronize data across a master server and a set of slave servers In a replication configuration MySQL Enterprise Backup helps you manage images for the entire system set up new slave servers or restore a master server in an efficient way that avoids unnecessary work for the slave servers On the other hand having multiple slave servers to choose from gives you more flexibility about where to perform backups When the binary log is enabled you have more flexibility about restoring the database to a specific point in time even a time that is later than that of the last backup 6 1 Setting Up a New Replication Slave MySQL Enterprise Backup allows you to set up a replication slave by backing up the master and restoring the backup on a new slave server without having to stop the master For servers NOT using GTID 1 Take a backup of the master transfer it to the slave use mysqlbackup with the apply log option to prepare it and put the restored backup and

MySQL Enterprise Backup User`s Guide (Version 3.12.1)

Contents

Download Pdf Manuals

Related Search

Related Contents