Sets a backup profile that defines
be backed up,
where the backup should be
when (the frequency) it should be
backed up. The following figure shows an example of the main page.
The Online Backup page 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-clicking on a Backup Job is an alternative way to access the available actions, such as
Delete Job, and
Execute Backup. 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, and is used to modify existing jobs.
The Backup Profile Name and its associated Comments field are used to identify the backup job's profile, and this name is listed on the main page.
The Contents tab defines the schemas and tables to back up, and whether the job is a full or partial backup.scheduling page separates the configuration information into four tabs. The
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 (see the figure that follows). 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.
The Options tab includes settings to modify the default behavior of the backup process.
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.
Additional options include compression and
apply-log, and the option to Skip
Unused Pages. The following figure shows an example of
the Options tab.
The Schedule tab optionally sets a backup schedule for both full and incremental backups (see the figure that follows). 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.
The Advanced tab allows you to pass in additional MySQL Enterprise Backup options.
These additional options are not validated.
To recover backups, see Section 6.7.3, “Backup Recovery”.