This is the first step in the restoration process.
If users are restoring from a Full Backups and no incremental backups exist, then the backup set just prior to the time entered will be used to restore the data.
When incremental backups exist, ZMC for MySQL provides the ability to restore till the specified time. One of the more common reasons for a restore is to roll back the database to the point before a particular event (such as a mistake or malicious activity) damaged the database. In that case, you should use the Database Events viewer to launch the restore, and all of this information will be automatically prefilled on the Restore What page.
If the Restore from time is not specified, ZRM restores the most recent full backup and also looks at the subsequent incremental backup for transactions to restore to fulfill the user-specified Restore to time.
For example: A full backup was completed on Oct 8 at 16:17:29 and the next incremental backup occurred on Oct 8 at 18:00:00. If you specify a Restore to time of Oct 8, 16:17:29 and do not specify a "restore from" time, ZRM restores from the full backup dated Oct 8, 16:17:29 and all transactions that are present in the next incremental backup (Oct 8, 18:00:00) that occurred at Oct 8, 16:17:29.
Restoration of specific table(s) is not supported with InnoDB storage engine tables. The InnoDB table space contains information about all tables in the database and will have to be restored.