Updated on 2024-11-07 GMT+08:00

Creating a Migration Project

Scenarios

After the source database evaluation is complete, select the target database based on the evaluation result, enter related information, and create a migration project. Each migration project corresponds to an evaluation project. You can create multiple migration projects based on an evaluation project.

To create a migration project, perform the following steps:

Precautions

The target database performance is affected during migration. You are advised to use the target database in a non-production environment or perform the migration during off-peak hours.

Prerequisites

  • You have permissions to create a migration project in the UGO console. To obtain permissions, see Permission Management.
  • There is at least one evaluation project whose Evaluation Status is Completed. Create Migration Project.
  • The type and version of the target database to be used must be the same as those confirmed in the evaluation project.
  • The target database to be connected is normal and has no arrears or suspension.
  • Ensure that the destination database can be accessed and the target database user must have the permission to create, delete, or modify databases objects, such as schemas, tables, programs, indexes, users, functions, and views. For details, see Viewing the Permission Check Report.

Confirming the Target Database

  1. Log in to the UGO console.
  2. In the navigation pane, choose Schema Migration > DB Evaluation.
  3. Locate the project whose Project Status is In progress. Confirm Target DB Pending. Click the project name or click Confirm Target DB Pending.
  4. On the displayed page, select your desired target database and click Confirm DB Selection.
  5. Click Confirm.
  6. After the target database is confirmed, a dialog box is displayed.

    • Click Create Now to go to the Create Migration Project page.
    • Click Create Later to stay on the current page.

  • After you confirm the target database, Confirm DB Selection and Re-Evaluate buttons are unavailable. The confirmed target database cannot be modified. Exercise caution when you select a target database.
  • After you confirm the target database, Project Status changes to Completed. Create Migration Project.

Creating a Database Migration Project

  1. Log in to the UGO console.
  2. In the navigation pane, choose Schema Migration > Object Migration.
  3. Click Create Project in the upper right corner.
  4. On the Create Project page, configure parameters. For details, see Table 1.

    Figure 1 Creating a migration project

  5. Click Test Connection.

    • If the connection test is successful, the Next button is available.
    • If the connection test fails, an error message is displayed.

  6. Click Next to go to the Precheck page.

    Figure 2 Performing a pre-check
    • For check items in the Failed status, click View Details in the Operation column, perform operations as prompted, and click Recheck. The Next button is activated only when all check items are in the Success or Alarm status.
    • If you have known the possible impact of unhandled check items and still want to create a project, click Skip Failed Check Items. When the results of failed check items change to Alarm, and the Next button is activated.
    • If the target database type is GaussDB, the following checks are performed:
    • If the target database type is not GaussDB, the following checks are performed:

  7. Click Next in the lower right corner.

    Figure 3 Confirming information

    The database migration scope, migration project details, and target database information are displayed.

  8. Confirm the information and click Create. After the creation is successful, click OK. to the Object Migration page.

    After a migration project is created, the permission check is automatically triggered when the target database is not GaussDB. If the check is successful, the project status is Ready.

    If the permission check fails, the project status is Not ready. You can manually check permissions.

Parameters

Table 1 Parameter description

Parameter

Description

Project Name

The project name must be unique.

The name is unique. It can contain 5 to 50 characters and must start with a letter and end with a digit or letter. Only letters (case-insensitive), digits, underscores (_), and hyphens (-) are allowed.

(Optional) Exception Notification Mode

SMN Topic

Specifies whether to report exceptions through Simple Message Notification (SMN).

To create an SMN topic, see Creating a Topic.

NOTE:

Follow-up Operation

After the topic is created, you can add a subscription. After the subscription has been confirmed, alarm notifications will be sent to the subscription endpoint via SMN.

Notification scenario:

When the account is frozen or unfrozen, SMN can be used to send notifications.

Enterprise Project

If you have been associated with an enterprise project, select the target project from the Enterprise Project drop-down list.

You can also go to the project management console to create a project. For details about how to create a project, see Enterprise Management User Guide.

Permission Check

If the target database type is not GaussDB, Skip Permission Check is displayed and is not selected by default. If Skip Permission Check is selected, the View Permission Check Report button is grayed out.

NOTE:

To create objects in the target database, you must have some database permissions, such as creating tables and functions. If you skip the permission check, the system does not check whether you have these permissions.

The migration may fail due to lack of permissions when SQL statements are converted on the target database.

Evaluation Project

Select the evaluation project where a target database has confirmed.

  • Target DB: The confirmed target database type is displayed. Each tenant can connect to a maximum of five target databases at the same time.
  • Target DB Version: The confirmed target database version is displayed.

DB Connection Mode

If you select Public network, the source database will be connected using an EIP. Select Hostname or Host IP Address for Host Type and Set Host Port.

  • If the target database network is restricted by the IP address whitelist, add the EIP to the target database network whitelist to ensure that UGO can connect to the target database.
    • EIP in AP-Singapore: 110.238.109.54
    • EIP in LA-Santiago: 159.138.116.198
  • Host IP Address: Enter the IP address of the target database host.
    • If the target database type is GaussDB Primary/Standby, you can enter only the IP address of the primary node or the IP addresses of the primary node and multiple standby nodes. Use commas (,) to separate the IP addresses. When you connect to the database, the system automatically selects the IP address of the primary node.
    • If the target database type is GaussDB Distributed, you can enter one or more CN IP addresses separated by commas (,). The first IP address is preferentially used to connect to the database. If the previous IP address is abnormal, the next IP address will be used to connect to the database. If the first IP address of the CN can be connected but the CN node is abnormal and cannot be written, the connection test is normal, but an error message is displayed during permission check and object migration.
  • Host Name: Enter a host name.
    • The host name cannot be empty.
    • You can enter multiple hostnames and use commas (,) to separate them. All hostnames can contain up to 1,024 characters.
    • A host name can contain a maximum of 253 characters and cannot contain the following special characters: !@#$%^&*()+=[]{}|\:;<>,?/

If you select VPC Endpoint for DB Connection Mode, you also need to set VPC Endpoint and Port Mapping.

If you select Auto assigned by instance, select a value from the Database Instance drop-down list.

  • Click View DB Instance to go to the instance management page of the target database and view instance information.
  • Click View instances that cannot be selected. A dialog box is displayed, showing the unavailable instance names and reasons.
    NOTE:

    Auto assigned by instance is available only to whitelisted users. To use this function, you need to submit a service ticket. To configure the whitelist permission, in the upper right corner of the management console, submit an application by choosing Service Tickets > Create Service Ticket.

DB Name

Name of the database.

The name can contain 2 to 128 characters and must start with a letter, digit, period (.), underscore (_), or hyphen (-). Only letters, digits, periods (.), underscores (_), hyphens (-), dollar signs ($), and number signs (#) are allowed. The name can be enclosed in double quotation marks ("").

Username

Username of the target database. It is recommended that the user has the administrator permissions.

Password

Password for accessing the target database.

Schemas to Migrate

  • Select Select all: Select schemas to be collected by UGO from the source database.
  • Deselect Select all: whether to reselect the schemas selected in the evaluation project.

By default, Select all is selected.

SSL Type

  • No SSL: SSL is disabled and there may be potential security risks.
  • SSL No Auth: Transmission will be encrypted without authentication.
  • One-way SSL: The target database will be authenticated and transmission will be encrypted.
    • Truststore password: Enter the password of the truststore used to access the certificate.
    • Click Add File to upload the root certificate file of the target database.
NOTE:
  • If you select One-way SSL, enter the correct uploaded file and entered password, which are private information of users. If the target database type is GaussDB or PostgreSQL, upload a PEM root certificate file. No password is required.
  • Secure Socket Layer (SSL) provides a secure connection between the network and application layers. In mutual SSL authentication, an SSL connection between a client and a server is established only if they validate each other's identity using digital signatures. If SSL is disabled, your data may be at risk.

(Optional) Tags

Use predefined tags in Tag Management Service (TMS). Predefined tags are visible to all service resources that support the tagging function. For details, see Tag Management Service User Guide.

Enter a key and a value, and click Add.

A maximum of 10 tags can be added. For details, see Managing Tags.