Sets a backup profile that defines what should be backed up, where the backup should be stored, and when (the frequency) it should be backed up. With an active MySQL connection tab open, click and then from the menu to view the main Online Backup screen in the current tab.
The following figure shows an example of the main Online Backup screen with an example of a full and a partial backup job configured for the current MySQL instance.
The Online Backup screen is separated into three sections:
Backup Jobs: Used for managing backup jobs for the MySQL server. A backup job (profile) is a configuration file used to store information about what is backed up, where the backup is stored, and optionally when backups will be performed.
Right-click a backup job is an alternative way to access the available actions, such as, , and . Right-clicking also offers two additional options:
/bin/mysqlbackup --defaults-file="/var/lib/meb/foo.cnf" --show-progress=stdout backup --with-timestamp
Backup Job Details: Displays information about the state of a specific (selected) backup job. It includes information from the page, and information specific to the selected backup.
Recent Activity: Historical information about the backup operations performed on the server. View the backup log by right-clicking an entry and choosing
View Backup Log
A progress dialog is generated for the backup operation.
The following information applies to theoperation. is used to modify existing jobs.
The Backup Profile Name and its associated Comments field are used to identify the profile of the backup job. Each backup job name is listed on the main screen. The scheduling screen separates the configuration information into four subtabs: Schedule, Contents, Options, and Advanced.
Schedule Tab. The Schedule subtab optionally sets a backup schedule for both full and incremental backups. The schedule uses the Windows Tasks Scheduler on Microsoft Windows, and a cron job on Linux and macOS. It is scheduled using the operating system user that is scheduling the backup, which is typically the MySQL user.
A full backup is slower than the incremental backup that merges with a full backup. A common scenario is to set a full backup as weekly, and an incremental backup as daily. For additional information about backup performance, see Optimizing Backup Performance.
Full backup: All schemas and tables are backed up (see the figure that follows).
Partial: Select the schemas and tables (objects) that you want to back up. Choose Select objects to included/excluded to open the table inclusion (and exclusion) options. For additional information about the include, exclude, and Transportable Tablespace options, see the MySQL Enterprise Backup documentation titled Partial Backup and Restore Options.
Backup Storage Directory: By default, the Backup Storage Directory is stored under a sub-folder using the name of the Backup Profile Name in the
MySQL Backup Home Directorysetting.
A new sub-folder is created for each backup, named with its timestamp. An example subdirectory is "2016-02-22_17-49-18" where 17:49:18 is the time.
Incremental backups are also stored in the Backup Storage Directory directory, but in their own
inc/sub-folder. Each incremental backup also creates its own timestamped sub-folder within
Compress Backup: Optionally compress non-incremental InnoDB backups.
Apply Log after backup: After a backup is completed, an
apply-logoperation is needed before it can be completed. This can be done after a backup, before recovery, or at any other time. Disabled by default.
Skip Unused Pages: Use this option to reduce the backup size by removing unused pages that are typically generated by bulk deletes. Disabled by default.Note
Enabling this increases the restoration time because the removed unused pages must be added back during the recovery process.
Incremental Backups Using Only the Redo Log (incremental-with-redo-log-only): Specifies that an incremental backup is to be created using only the redo log.
Encrypt Password: Sets a password that is required to back up and restore encrypted tables.
These additional options are not validated.
To recover backups, see Section 6.7.3, “Backup Recovery”.