Movatterモバイル変換

Metadata for ARCHIVE tables. Contrast with.ARZ file. Files with this extension are always included in backups produced by themysqlbackup command of theMySQL Enterprise Backup product.

See Also.ARZ file.

Data for ARCHIVE tables. Contrast with.ARM file. Files with this extension are always included in backups produced by themysqlbackup command of theMySQL Enterprise Backup product.

See Also.ARM file.

The operation that transforms araw backup into aprepared backup by incorporating changes that occurred while the backup was running, using data from thelog.

See Alsolog,prepared backup,raw backup.

A licensed products that performshot backups of MySQL database servers. It offers the most efficiency and flexibility when backing upInnoDB tables; it can also back up MyISAM and other kinds of tables. It is included as part of the MySQL Enterprise Edition subscription.

See AlsoInnoDB.

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 therestore operation.

With MySQL,physical backups are performed by theMySQL Enterprise Backup product, andlogical backups are performed by themysqldump 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 ashot,warm, orcold depending on how much they interfere with normal database server operation. (Hot backups have the least interference, cold backups the most.)

See Alsological backup,mysqldump,physical backup,warm backup.

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.

Contrast withserver repository.

See Alsorepository,server repository.

A smallconfiguration file generated byMySQL Enterprise Backup, containing a minimal set of configuration parameters. This file records the settings that apply to this backup data. Subsequent operations, such as theapply 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 Alsoapply,configuration file.

An informal name for thebinary log file. For example, you might see this abbreviation used in e-mail messages or forum discussions.

A technique that produces smallerbackup files, with size reduction influenced by thecompression 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 ofInnoDB 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 therestore process.

See Alsobackup,compression level,.ibd file,InnoDB,restore.

A setting that determines how muchcompression 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 Alsocompression.

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 macOS systems, andmy.ini on Windows systems. TheMySQL Enterprise Backup stores its default configuration settings in this file, under a[mysqlbackup] section. For convenience, 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 Alsomy.cnf,my.ini.

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 thedoublewrite buffer. When the database is shut down normally, this type of activity is performed during shutdown by thepurge operation.

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 of the InnoDBsystem tablespace.

Because theMySQL Enterprise Backup product always backs up the system tablespace, all backups include the contents of the data dictionary.

See AlsoMySQL Enterprise Backup,system tablespace.

A set of tables and related objects owned by a MySQL user. Equivalent to“schema” in Oracle Database terminology.MySQL Enterprise Backup can perform apartial backup that includes some databases and not others. The full set of databases controlled by a MySQL server is known as aninstance.

See Alsoinstance.

In apartial backup, to select a set of tables, databases, or a combination of both to be omitted from the backup. Contrast withinclude.

The operation that retrieves some content from animage file produced by asingle-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 themysqlbackup optionsextract andimage-to-backup-dir, respectively.

See Alsoimage,single-file backup.

The format used by InnoDB for its data files namedibdata1,ibdata2, and so on. Each file format supports one or more row formats.

See Alsoibdata file,row format.

Abackup that includes all thetables in each MySQL database, and all the databases in a MySQL instance. Contrast withpartial backup andincremental 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 Alsobackup,incremental backup,table.

The tablemysql.backup_history that holds details of completedbackup operations. While a backup job is running, the details (especially the changing status value) are recorded in theprogress table.

See Alsobackup,progress table.

Each InnoDBtablespace created using thefile-per-table setting has a filename with a.ibd extension. This extension does not apply to thesystem tablespace, which is made up of files namedibdata1,ibdata2, and so on.

See Alsosystem tablespace,tablespace.

A set of files with names such asibdata1,ibdata2, and so on, that make up the InnoDBsystem tablespace. These files contain metadata about InnoDB tables, and can contain some or all of the table and index data also (depending on whether thefile-per-table option is in effect when each table is created). For backward compatibility these files always use theAntelope file format.

See Alsosystem tablespace.

The file produced as part of asingle-file backup operation. It can be a real file that you store locally, or standard output (specified as-) when the backup data isstreamed directly to another command or remote server. This term is referenced in severalmysqlbackup options such asbackup-dir-to-image andimage-to-backup-dir.

See Alsosingle-file backup,streaming.

In apartial backup, to select a set of tables, databases, or a combination of both to be backed up. Contrast withexclude.

A backup that captures only data changed since the previous backup. It has the potential to be smaller and faster than afull backup. The incremental backup data must be merged with the contents of the previous backup before it can be restored. SeeSection 4.3.3, “Making a Differential or Incremental Backup” for usage details. Relatedmysqlbackup options are--incremental,--incremental-with-redo-log-only,--incremental-backup-dir,--incremental-base, and--start-lsn.

See Alsofull backup.

The type of MySQLtable that works best withMySQL Enterprise Backup. These tables can be backed up using thehot 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, theCREATE TABLE statement creates InnoDB tables by default.

See Alsotable.

The full contents of a MySQL server, possibly including multipledatabases. Abackup operation can back up an entire instance, or apartial backup can include selected databases and tables.

See Alsodatabase.

See Alsowarm backup.

Several types of log files are used within the MySQL Enterprise Backup product. The most common is the InnoDBredo log that is consulted duringincremental backups.

See Alsoincremental backup,redo log.

SeeLSN.

Abackup that reproduces table structure and data, without copying the actual data files. For example, themysqldump command produces a logical backup, because its output contains statements such asCREATE TABLE andINSERT that can re-create the data. Contrast withphysical backup.

See Alsobackup,physical backup.

Acronym forlog sequence number. This arbitrary, ever-increasing value represents a point in time corresponding to operations recorded in theredo 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 duringcrash recovery and for managing the buffer pool.

In theMySQL Enterprise Backup product, you can specify an LSN to represent the point in time from which to take anincremental backup. The relevant LSN is displayed by the output of themysqlbackup 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 Alsocrash recovery,incremental backup,redo log.

A file containing references to other tables, used by theMERGE storage engine. Files with this extension are always included in backups produced by themysqlbackup command of theMySQL Enterprise Backup product.

A file that MySQL uses to store data for a MyISAM table.

See Also.MYI file.

A file that MySQL uses to store indexes for a MyISAM table.

See Also.MYD file.

The record of the environment (for example, command-line arguments) and data files involved in a backup, stored in the filesmeta/backup_create.xml andmeta/backup_content.xml, respectively. This data can be used by management tools during diagnosis and troubleshooting procedures.

Seesource.

A class of software programs for managing backup media, such as libraries of tape backups. One example isOracle Secure Backup. AbbreviatedMMS.

See AlsoOracle Secure Backup.

The typical name for the MySQLconfiguration file on Linux, Unix, and macOS systems.

See Alsoconfiguration file,my.ini.

The typical name for the MySQLconfiguration file on Windows systems.

See Alsoconfiguration file,my.cnf.

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 storage engines also. The backup process for InnoDB tables (hot backup) is less disruptive to database operations than for MyISAM tables (warm backup).

See AlsoInnoDB,warm backup.

The primary command of theMySQL Enterprise Backup product. Different options performbackup andrestore operations.

See Alsobackup,restore.

A MySQL command that performslogical backups, producing a set of SQL commands to recreate tables and data. Suitable for smaller backups or less critical data, because therestore operation takes longer than with aphysical backup produced byMySQL Enterprise Backup.

See Alsological backup,physical backup,restore.

A backup that is NOT created usingtransportable tablespace (TTS), that is, not with the--use-tts option.

See Alsotransportable tablespace,TTS backup.

A file containing database server configuration information. Files with this extension are always included in backups produced by the backup operations of theMySQL Enterprise Backup product.

An Oracle product for managingbackup media, and so classified asmedia management software (MMS). AbbreviatedOSB. ForMySQL Enterprise Backup, OSB is typically used to manage tape backups.

See Alsobackup,media management software,OSB.

Abbreviation forOracle Secure Backup, amedia management software product (MMS).

See AlsoOracle Secure Backup.

A file containing partition definitions. Files with this extension are always included in backups produced by themysqlbackup command of theMySQL Enterprise Backup product.

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). SeeSection 1.2, “Overview of Backup Types” for an overview,Section 20.10, “Performance / Scalability / Capacity Options” for the relevantmysqlbackup options, andChapter 13,Performance Considerations for MySQL Enterprise Backup for performance guidelines and tips.

Abackup that copies the actual data files. For example, theMySQL Enterprise Backup command produces a physical backup, because its output contains data files that can be used directly by themysqld server. Contrast withlogical backup.

See Alsobackup,logical backup.

The time corresponding to the end of abackup operation. Aprepared 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 Alsobackup,prepared backup,restore.

The set of backup data that is entirely consistent and ready to be restored. It is produced by performing theapply operation on theraw backup.

See Alsoapply,raw backup.

The tablemysql.backup_progress that holds details of runningbackup operations. When a backup job finishes, the details are recorded in thehistory table.

See Alsobackup,history table.

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. Theapply operation transforms the backup files into aprepared backup that is ready to be restored.

See Alsoapply,prepared backup.

A set of files, typically namedib_logfile0 andib_logfile1, 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-increasingLSN value. The 4GB limit on maximum size for the redo log is raised in MySQL 5.6.

See AlsoLSN.

Some MySQL Enterprise Backup features use POSIX-style regular expressions, for example to specify tables, databases, or both toinclude orexclude from apartial 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 by the shell wildcard mechanism.

See Alsoexclude,include.

In areplication configuration, a database server that receives updates from asource server. Typically used to service user queries, to minimize the query load on the source server. WithMySQL Enterprise Backup, you might take a backup on one server, and restore on a different system to create a new replica server with the data already in place. You might also back up data from a replica server rather than the source, to minimize any slowdown of the overall system.

See Alsoreplication,source.

A common configuration for MySQL deployments, with data and DML operations from asource server synchronized with a set ofreplica servers. With MySQLEnterprise Backup, you might take a backup on one server, and restore on a different system to create a new replica server with the data already in place. You might also back up data from a replica server rather than the source, to minimize any slowdown of the overall system.

See Alsoreplica,source.

We distinguish between theserver repository and thebackup repository.

See Alsobackup repository,server repository.

The converse of thebackup operation. The data files from aprepared backup are put back into place to repair a data issue or bring the system back to an earlier state.

See Alsobackup,prepared backup.

The disk storage format for a row from an InnoDB table. As InnoDB gains new capabilities such as compression, new row formats are introduced to support the resulting improvements in storage efficiency and performance.

Each table has its own row format, specified through theROW_FORMAT option. To see the row format for each InnoDB table, issue the commandSHOW 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 theinnodb_file_per_table option, so that each table is stored in a separate tablespace.

Acronym forsystem backup to tape.

See Alsosystem backup to tape.

Another name forpartial backup

See Alsoselective restore.

Another name forpartial restore

See Alsoselective backup.

A MySQLinstance controlled by amysqld daemon. A physical machine can host multiple MySQL servers, each requiring its ownbackup operations and schedule. Some backup operations communicate with the server through aconnection.

See Alsoinstance.

Contrast withbackup repository.

See Alsobackup repository,repository.

A backup technique that packs all the backup data into one file (the backupimage), for ease of storage and transfer. Thestreaming backup technique requires using a single-file backup.

See Alsoimage,streaming.

Seereplica.

In areplication configuration, a database server that sends updates to a set ofreplica servers. It typically dedicates most of its resources to write operations, leaving user queries to the replicas. WithMySQL Enterprise Backup, typically you perform backups on the replica servers rather than the source, to minimize any slowdown of the overall system.

See Alsoreplica,replication.

A backup technique that transfers the data immediately to another server, rather than saving a local copy. Uses mechanisms such as Unix pipes. Requires asingle-file backup, with the destination file specified as- (standard output).

See Alsosingle-file backup.

An API formedia management software. AbbreviatedSBT. Severalmysqlbackup options (withsbt in their names) pass information tomedia management software products such asOracle Secure Backup.

See AlsoOracle Secure Backup,SBT.

By default, this single data file stores all the table data for a database server, as well as all the metadata for InnoDB-related objects (thedata dictionary).

Turning on theinnodb_file_per_table option causes each newly created table to be stored in its owntablespace, reducing the size of, and dependencies on, the system tablespace.

Keeping all table data in the system tablespace has implications for theMySQL Enterprise Backup product (backing up one large file rather than several smaller files), and prevents you from using certain InnoDB features that require the newerBarracuda file format. on the

See Alsodata dictionary,file format,ibdata file,tablespace.

A file containingtrigger parameters. Files with this extension are always included in backups produced by themysqlbackup command of theMySQL Enterprise Backup product.

Although a table is a distinct, addressable object in the context of SQL, forbackup purposes we are often concerned with whether the table is part of thesystem tablespace, or was created under thefile-per-table setting and so resides in its owntablespace.

See Alsobackup,system tablespace,tablespace.

ForInnoDB tables, the file that holds the data and indexes for a table. Can be either thesystem tablespace containing multiple tables, or a table created with thefile-per-table setting that resides in its own tablespace file.

See AlsoInnoDB,system tablespace.

A feature that allows atablespace to be moved from one instance to another. Traditionally, this has not been possible for InnoDB tablespaces because all table data was part of thesystem tablespace. In MySQL 5.6 and higher, theFLUSH TABLES ... FOR EXPORT syntax prepares an InnoDB table for copying to another server; runningALTER TABLE ... DISCARD TABLESPACE andALTER 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 thespace ID) as the tablespace is imported. SeeImporting InnoDB Tables for usage information.

Use the--use-tts option to create a backup with transportable tablespace. See alsoSection 5.1.5, “Restoring Backups Created with the--use-tts Option”.

Short form fortransportable tablespace.

See Alsotransportable tablespace.

A backup that is created usingtransportable tablespace (TTS), that is, with the--use-tts option.

See Alsonon-TTS backup,transportable tablespace.

Abackup taken while the database server is running, but that restricts some database operations during the backup process. For example, tables might become read-only. For busy applications and websites, you might prefer ahot backup.

See Alsobackup.