Skip to main content

Restore (logical backup data)

In the event of a misoperation or failure of the database, user can restore the backup data to the database through NineData's backup and restore service.

Prerequisite​

Restrictions​

  • The target data source to be restored must be the same as the data source type of the backup data. For example, backup data for MySQL does not support restore to SQL Server data sources.
  • The restored target data source version must be greater than or equal to the data source version of the backup data. For example, MySQL 8.0 backup data does not support restore to MySQL 5.6 data sources.
  • The current SQL Server data source does not support incremental backups when performing logical backups, so point-in-time restore is not supported.
  • During full restore, if the database contains views (VIEW), functions (FUNCTION), stored procedures (PROCEDURE), and triggers (TRIGGER), do not execute the configuration mapping object in step 5, otherwise the task will fail.
  • Triggers (TRIGGERs) and events (EVENTs) created during incremental backups cannot be recovered, but the resulting data will be recovered normally.
  • During restore, if the database contains views (VIEW), functions (FUNCTION), stored procedures (PROCEDURE), triggers (TRIGGER), and events (EVENT), the definer (DEFINER) information of the above objects will be modified to the current restore The account that accesses the database in the task.
  • When restore, if there is a foreign key (FOREIGN KEY) in the table, the foreign key constraint is not enforced.

Steps​

  1. Log in to NineData console.

  2. On the left navigation bar, click Backup > Restore.

    tip

    User can also click Backup > Backup Set. On the Full Backup Set tab, find the ID of the backup set that has been backed up, and click Restore in the Actions column on the right.

  3. On the Restore Method tab, configure according to the table below and click Next.

    Parameters
    		Description
    NameEnter the name of the restore task. For the convenience of subsequent search and management, try to use a meaningful name. Up to 64 characters are supported.
    SourceBackup objects, you can quickly find Backup Task by selecting the Source.
    Backup TaskA backup job, created when backing up a data source, contains all the data needed for restore.
    Restore MethodThe following restore methods are supported:
    • Restore by Time (only supported by MySQL): This method is based on full backup data and logs, and can recover full data and subsequent incremental data. For the specific restore time period, see the console.
    • Backup Set : This method is only based on the full backup data, and supports restore to the point in time when the full backup is completed, excluding incremental data.
    Restore Time (MySQL only)It can be configured when the Restore Method is Restore by Time , and user can select the point in time to which the data will be recovered. The second-level RPO can be achieved, and the data at any point in time between the start of the backup and the current point in time can be restored.
    Backup SetIt can be configured when the Restore Method is Backup Set. This option does not contain incremental data.
    TargetTo restore the object, select which data source to restore the backup data to.
    TypeIt can be configured when the Restore Method is Backup Set. Select the content to be restored, and support single-selection or multiple-selection of Schema and Full Data. User can also click to show the Advanced settings and select the processing strategy when there is a table with the same name or the same data.
    Advanced
    • Schema Conflict
      • Ignore Conflict and Continue : When a table with the same name exists, ignore and continue the restore task.
      • If object exists, STOP : When a table with the same name exists, stop the restore task.
    • Data Conflict
      • Ignore Conflict and Continue : When the same data exists, ignore this piece of data and continue to restore other data.
      • If data exists, STOP : When the same data exists, stop the restore task.
      • Delete and Rewrite : delete the piece of data and rewrite it.

  4. On the Restore Objects tab, confirm the content to be restored. User can select Backup to restore all data, or select multiple Customized Objects and selectively restore, and click Next.

  5. On the Mapping tab, configure the table name after the target table is restored to the target data source, and click Save and Pre-Check.

  6. On the Pre-check tab, wait for the system to complete the pre-check. After the pre-check passes, click Launch.

    tip
    • If the pre-check fails, user need to click the Details in the Actions column to the right of the target check item to correct the failure, and then perform the pre-check again.

  • Warnings can be repaired or ignored according to specific circumstances.

    :::

  1. On the Launch tab, a message is displayed indicating that Launch Successfully. Click View Details to view the execution status of the restore tasks; click Back to List to return to Restore list.
Last updated on