Migration Implementation

更新时间:
复制 MD 格式

This topic describes considerations, migration limitations, and the procedure for data migration of CPFS for Lingjun instances.

Considerations

When using Data Online Migration to migrate data from CPFS for Lingjun instances, note the following:

  • Migration consumes resources at both source and destination, which may affect your workloads. For mission-critical services, set a rate limit or run the task during off-peak hours.

  • The service checks files at source and destination before migration. If a same-name file exists at both locations and the task is configured to overwrite, the destination file is overwritten directly. Back up or rename files with different content to prevent data loss.

  • Online migration preserves the last modified time of source files. If a lifecycle rule is configured on the destination bucket, it may delete or transition migrated files based on their last modified time.

Migration Limitations

  • For limitations on migrating data from CPFS for Lingjun instances to Alibaba Cloud OSS, see Migration Limitations.

  • For limitations on migrating data from Alibaba Cloud OSS to CPFS for Lingjun instances, see Migration Limitations.

  • For limitations on migrating data between CPFS for Lingjun instances, see Migration Limitations.

Step 1: Select a region

  1. Log on to the Alibaba Cloud Data Online Migration Management Console using the created RAM user.

  2. In the upper-left corner of the top menu bar, select the region where your agent is deployed.

    Important
    • Channels, agents, data addresses, and migration jobs are not shared across regions. Choose carefully.

    • Prefer the region where your agent is located. If that region is unavailable, choose the closest available region to deploy your migration job.

Step 2: Create a channel

Important

For migrations between CPFS for Lingjun instances, use different channels and agents for the source and destination.

  1. In the navigation pane on the left, choose Data Online Migration > Channel Management, then click Create Channel.

  2. In the Create Channel dialog box, configure the following parameters, then click OK.

    Parameter

    Required

    Description

    Name

    Yes

    The name of the tunnel.

    • The name cannot be empty and can be up to 100 characters in length.

    • The name can contain letters, digits, hyphens (-), and underscores (_).

    Bandwidth Limit

    Yes

    The maximum bandwidth that the tunnel can use.

    • If you do not configure this parameter, the default value 0 is used, which indicates that the bandwidth for the tunnel is not limited.

    • If you configure this parameter, enter a value based on the note in the console.

    Important

    The bandwidth that is available for the tunnel depends on the actual bandwidth of the network connection.

    Requests per Second

    Yes

    The maximum number of requests per second over the tunnel.

    • If you do not configure this parameter, the default value 0 is used, which indicates that the number of requests per second over the tunnel is not limited.

    • If you configure this parameter, enter a value based on the note in the console.

    Warning

    We recommend that you evaluate the capabilities of the storage system of the data source before you configure this parameter. If you set this parameter to a great value, your business is affected. We recommend that you enter a value based on the note in the console.

Note

For more information about channels, see Channel Management.

Step 3: Create an agent

  1. In the navigation pane on the left, choose Data Online Migration > Agent Management, then click Create Agent.

  2. In the Create Agent dialog box, configure the following parameters, then click OK.

    Parameter

    Required

    Description

    Name

    Yes

    The name of the agent.

    • The name must be 3 to 63 characters long.

      • The name can contain lowercase letters, digits, hyphens (-), and underscores (_). The name is case-sensitive.

      • The name must be UTF-8 encoded and cannot start with a hyphen (-) or an underscore (_).

    Network Type

    Yes

    The network connectivity method for the agent. Select Internet (public network).

    Important

    When migrating LocalFS-type CPFS for Lingjun instance data, Network Type must be set to Internet (public network). Although labeled as public network, data is actually migrated over Alibaba Cloud’s internal network.

    Deployment Method

    Yes

    Deployment method. Only independent process mode is supported.

    Channel

    Yes

    The tunnel to associate with the agent. Each agent is bound to exactly one tunnel, and its bandwidth is limited by the tunnel's total bandwidth.

    For example, a tunnel named tunnel-1 has a maximum bandwidth of 10 Gbit/s. If tunnel-1 is associated with three agents, agent-1, agent-2, and agent-3, the sum of their bandwidth cannot exceed 10 Gbit/s. If agent-1 is allocated 3 Gbit/s of bandwidth, agent-2 and agent-3 have only 7 Gbit/s of bandwidth available to share. Plan bandwidth allocation accordingly.

  3. Generate the command to deploy and run the agent. For details, see Generate agent deployment script.

Note

For more information about agents, see Agent Management.

Step 4: Provide agent deployment information

  1. After generating the command to deploy and run the agent, contact the CPFS for Lingjun O&M engineer and provide the following information:

    • The CPFS for Lingjun instance ID.

    • The deployment command obtained in Step 3: Create an agent.

    • The directory to migrate on the CPFS for Lingjun instance—either the root directory ("/") or a subdirectory (for example, "/data1/").

  2. Have the CPFS for Lingjun O&M engineer deploy the agent. After deployment, wait for the O&M engineer to provide the mapped path. Then verify that the agent status is Normal.

  3. Once the agent is confirmed as Normal, proceed to Step 5: Create a CPFS for Lingjun instance data address.

Step 5: Create a CPFS for Lingjun instance data address

Important
  • LocalFS-type CPFS for Lingjun instance data can serve as either a source or destination address.

  • Before creating a CPFS for Lingjun instance data address, wait for the O&M engineer to provide the mapped path after agent deployment and confirm the agent status is Normal.

  1. In the navigation pane on the left, choose Data Online Migration > Address Management, then click Create Address.

  2. In the Create Address panel, configure the following parameters, then click OK.

    Parameter

    Required

    Description

    Name

    Yes

    • The name must be 3 to 63 characters in length.

    • The name is case-sensitive and can contain only lowercase letters, digits, hyphens (-), and underscores (_).

    • The name cannot start with a hyphen (-) or an underscore (_).

    Type

    Yes

    Select LocalFS.

    Directory to Migrate

    Yes

    Enter the mapped path provided by the CPFS for Lingjun O&M engineer after agent deployment. Use an absolute path that starts and ends with a forward slash (/). Environment variables are not supported.

    For example, if the source prefix is /example/src/ and it contains a file named example.jpg, and the destination prefix is example/dest/, the full path of the migrated file will be example/dest/example.jpg.

    Warning

    Verify the directory path carefully. An incorrect path prevents data from being read and causes the job to fail.

    Channel

    Yes

    Select the channel created in Step 2: Create a channel.

    Agent

    Yes

    Select the agent created in Step 3: Create an agent.

Step 6: Create an OSS address

Step 7: Create a migration job

For detailed steps to create a migration job, see Step 4: Create a migration job.

Important

On the Configuration Complete page, take a screenshot of the configuration and share it with the CPFS for Lingjun O&M engineer. Only after the O&M engineer confirms the settings are correct should you click OK and wait for the migration job to execute.

Step 8: Verify data

Migration Service transfers data but does not guarantee consistency or integrity. After migration completes, validate all migrated data to ensure consistency between source and destination.

Warning

After the migration task is complete, you must verify the migrated data at the destination. You are solely responsible for any data loss and all associated consequences if you delete the source data before confirming the integrity of the destination data.