Recover data to the master instance through a temporary instance

Last Updated: Apr 01, 2018

The data recovery function can minimize the damage caused by database misoperations. We recommend that you recover data to the master instance through a temporary instance.

Creating a temporary instance does not affect the current production instance but offers a temporary instance for data access. We recommend that you recover data to a temporary instance and verify the data before migrating the data to the master instance. This avoids the impact of data recovery on services.

Note:

  • The temporary instance inherits the account and password of the backup file.

  • The network type of temporary instance is classic network.

  • The temporary instance uses its instance name as the password.

  • Only one temporary instance can be generated at the same time. Before you create a temporary instance, delete any existing temporary instance.

  • The temporary instance is valid for 48 hours.

Procedure

  1. Log on to the RDS console and select the region where the target instance is located.

  2. Click the ID of the target instance to go to the Basic information page.

  3. Select Backup And Recovery in the left-side navigation pane to go to the Backup and recovery page, and then select the Temporary instance tab.

  4. Select the recovery time point, and click Create temporary instance.

  5. Click OK in the dialog box to create a temporary instance.

  6. After the temporary instance is created, go to the Instance list page.

  7. Click the ID of the target instance to go to the Basic information page.

  8. Click Create a data migration task in the upper right corner to go to Data Transmission console.

  9. Select Data migration in the left-side navigation pane to go to the Migration task list page.

  10. Click Create migration task.

  11. Enter the task name, source database and target database information, and click Authorize whitelist and enter into next step.

    Parameters description:

    • Task name: custom task name or default value.

    • Source database information:

      • Instance type: Specifies the instance type of a database. Select RDS Instance.

      • Instance region: The region where the master instance is located.

      • RDS instance ID: Click the drop-down list and select the temporary instance ID.

      • Database account: It is consistent with the account name of the master instance. Make sure that this account has the read/write privilege to all the data to be migrated.

      • Database password: It is consistent with the password of the master instance account.

    • Target database information:

      • Instance type: RDS Instance by default.

      • Instance region: The region where the master instance is located.

      • RDS instance ID: ID of the target RDS instance. Click the drop-down list and select the master instance mapped to the temporary instance.

      • Database account: The master instance account name. Make sure that this account has the read/write privilege to all the data to be migrated.

      • Database password: The password of the master instance account.

  12. Select the migration type, choose the migration object from the Migration objects column, and click > to add the migration object to the Selected column. And then click Pre-check and start.

    Note:

    • During data migration, the data (structure) of the source database is copied to the target database without affecting the data (structure) of the source database.

    • DDL operations are not supported during data migration. DDL operations may lead to a migration failure.

    • MySQL DTS incremental migration can only be performed for MySQL. The duration of a DTS incremental migration task is 15 days at most. If the task is not terminated after 15 days, the system resources may be recovered.

    To modify the migration object name in the target database, you can click Edit on the right side of the Selected list to modify the name.

    Note: Pre-check failure is described as follows. If pre-check is passed, go to step 10.

  13. If the system displays the pre-check failure result, click ! next to the check item with Check Result as Failed to check the detailed failure information, and perform troubleshooting accordingly.

  14. After troubleshooting, select the current migration task on the Migration task list page and click Start.

  15. After pre-check is passed, click OK to automatically run the migration task.

Thank you! We've received your feedback.