.ibz file ib-file set I/O-bound ibbackup_logfile ibdata file ibtmp file ib_logfile 6157 This data cannot be used for manual recovery; for that type of operation, use the  binary log . See Also binary log, log group, redo log.  A set of files, typically named  ib_logfile0  and  ib_logfile1 , that form the  redo log . Also sometimes referred to as the  log group . These files 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  InnoDB temporary tablespace data file  for non-compressed  InnoDB temporary tables  and related objects. The configuration file option,  innodb_temp_data_file_path , allows users to define a relative path for the temporary tablespace data file. If  innodb_temp_data_file_path  is not specified, the default behavior is to create a single auto-extending 12MB data file named  ibtmp1  in the data directory, alongside  ibdata1 . See Also data files, temporary table, temporary tablespace. Growth of the  ibdata  files is influenced by the  innodb_autoextend_increment  configuration option. See Also change buffer, data dictionary, doublewrite buffer, file-per-table, .ibd file, innodb_file_per_table, system tablespace, undo log.  A set of files with names such as  ibdata1 ,  ibdata2 , and so on, that make up the  InnoDB system tablespace . For information about the structures and data that reside in the system tablespace  ibdata  files, see Section 15.6.3.1, “The System Tablespace” .  A supplemental backup file created by the  MySQL Enterprise Backup  product during a  hot backup  operation. It contains information about any data changes that occurred while the backup was running. The initial backup files, including  ibbackup_logfile , are known as a  raw backup , because the changes that occurred during the backup operation are not yet incorporated. After you perform the  apply  step to the raw backup files, the resulting files do include those final data changes, and are known as a  prepared backup . At this stage, the ibbackup_logfile  file is no longer necessary. See Also apply, hot backup, MySQL Enterprise Backup, prepared backup, raw backup. See Also database, file-per-table, general tablespace, redo log, system tablespace, temporary tablespace, undo tablespace.  The set of files managed by  InnoDB  within a MySQL database: the  system tablespace ,  file-per-table tablespace files, and  redo log  files. Depending on MySQL version and  InnoDB  configuration, may also include general tablespace ,  temporary tablespace , and  undo tablespace  files. This term is sometimes used in detailed discussions of  InnoDB  file structures and formats to refer to the set of files managed by  InnoDB  within a MySQL database. See disk-bound. See Also compressed backup, compressed row format, file-per-table, .ibd file, MySQL Enterprise Backup, tablespace. The compression applied during backup is distinct from the  compressed row format  that keeps table data compressed during normal operation. A compressed backup operation skips the compression step for a tablespace that is already in compressed row format, as compressing a second time would slow down the backup but produce little or no space savings.  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.