- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
-
New Edition
- Permissions Management
- Settings Management
- Surveys
- Resource Discovery
- Application Management
- Migration Preparations
- Migration Solutions
- Migration Plans
- Migration Clusters
- Migration Workflows
- Big Data Migration (from MaxCompute to DLI)
- Big Data Verification
-
Old Edition
- Permissions Management
- Settings Management
- Migration Surveys
- Resource Discovery
- Application Management
- Big Data Lineage
- Migration Solutions
- Migration Plans
- Migration Clusters
- Migration Workflows
- Big Data Migration
- Big Data Verification
-
New Edition
-
MgC Agent Usage Guide
- MgC Agent Overview
- Downloading and Installing the MgC Agent (Formerly Edge)
- Local Discovery and Collection
- Connecting the MgC Agent to MgC
- Agent-based Discovery
-
Collector-based Discovery
- Creating a Collection Task
- Managing Collectors
-
Configuring Collector Parameters
- Kubernetes Static Collector (app-discovery-k8s)
- Kubernetes Conntrack Collector (app-discovery-k8s-conntrack)
- Kubernetes Pod Network Collector (app-discovery-k8s-pod-net)
- Process and Network Collector (app-discovery-process-netstat)
- Windows Process and Network Collector (app-discovery-process-netstat-win)
- RabbitMQ Collector (app-discovery-rabbitmq)
- Kafka Collector (app-discovery-kafka)
- Eureka Collector (app-discovery-eureka)
- Redis Collector (app-discovery-redis)
- MongoDB Collector (app-discovery-mongodb)
- MySQL-General Log Collector (app-discovery-mysql-generallog)
- MySQL-JDBC Collector (app-discovery-mysql-jdbc)
- Nginx Configuration Collector (app-discovery-nginx)
- Cloud VPC Log Collector (app-discovery-cloud-vpc-log)
- Nacos Collector (app-discovery-nacos)
- Application Configuration Collector (app-discovery-application-config)
- Best Practices
-
FAQs
- What Are the Requirements for the Server for Installing the MgC Agent (Formerly Edge)?
- How Do I Run the MgC Agent in Compatibility Mode?
- What Can I Do If the MgC Agent (Formerly Edge) Is Offline?
- Why Can't the MgC Agent (Formerly Edge) Start After Being Installed?
- How Do I Upgrade the MgC Agent (Formerly Edge) to the Latest Version?
- How Do I Uninstall the MgC Agent (Formerly Edge)?
- How Do I Restart the MgC Agent (Formerly Edge)?
- How Do I Check the Current MgC Agent Version (Formerly Edge)?
- How Do I Obtain Run Logs of the MgC Agent (Formerly Edge) on Linux?
- How Do I Fix the Error "The collector is not installed" When a Discovery Task Fails?
- How Do I Obtain the Hive Metastore Credential Files?
- What Can I Do If the Port Required by the MgC Agent Is Occupied and the Installation Fails?
- What Can I Do If AK/SK Verification Fails?
- How Do I Configure WinRM and Troubleshoot WinRM Connection Problems?
- What Do I Do If the Credential List Is Empty When I Create a Data Connection for Big Data Verification?
-
Best Practices
- Configuring Permissions Required for Server Migration
-
Server Migration
- Network Requirements for Server Migration
- Migrating On-premises Servers to Huawei Cloud
- Migrating Servers from Alibaba Cloud to Huawei Cloud
- One-stop Cross-AZ ECS Migration
- Migrating Servers Across AZs on Huawei Cloud
- Migrating Servers to FlexusX Instances (Original HECS X Instances)
- Keeping Private IP Addresses of Servers Unchanged After the Migration
- Batch Modifying and Restoring the Host Configurations for Linux Source Servers
- Batch Modifying and Restoring the Host Configurations for Windows Source Servers
-
Storage Migration
- Migrating Data from Other Cloud Platforms to Huawei Cloud
- Migrating Data from Multiple Source Buckets by Prefix
- Migrating Archive (Cold) Data
- Migrating Data from SFS 1.0 to SFS 3.0
- Performing a NAS-to-NAS Migration and Service Cutover
- Migrating File Systems in Batches
- Migrating Data from MinIO to Huawei Cloud OBS over HTTP
- Migrating Data from Ceph to Huawei Cloud OBS over HTTP
- Reducing Disk Capacity for Target Servers
- Resizing Disks and Partitions for Target Servers
- Collecting Details of Azure Kubernetes Service (AKS) Resources
- Collecting Details of Google Cloud GKE Resources
- Collecting Details of AWS Container Resources
- Collecting Details of Self-built Oracle Databases
-
Verifying Big Data Consistency After Migration
- Verifying the Consistency of Data Migrated from MaxCompute to DLI
- Verifying the Consistency of Data Migrated Between MRS ClickHouse Clusters
- Verifying the Consistency of Data Migrated from Alibaba Cloud EMR ClickHouse to Huawei Cloud MRS ClickHouse
- Verifying the Consistency of Data Migrated from Alibaba Cloud ApsaraDB for ClickHouse to Huawei Cloud MRS ClickHouse
- Verifying the Consistency of Data Migrated from Alibaba Cloud ApsaraDB for ClickHouse to Huawei Cloud CloudTable ClickHouse
- Verifying the Consistency of Data Migrated Between MRS Doris Clusters
- Verifying the Consistency of Data Migrated Between MRS Doris Clusters or from CDH or EMR to MRS Doris
- Verifying the Consistency of Data Migrated from Alibaba Cloud MaxCompute to Huawei Cloud DLI
- Verifying the Consistency of Data Migrated Between MRS HBase Clusters
- Verifying the Consistency of Data Migrated from Delta Lake (with Metadata) to MRS Delta Lake
- Verifying the Consistency of Data Migrated from Delta Lake (without Metadata) to MRS Delta Lake
- Migrating Big Data Without Using the Internet
- BigData Migration Cockpit
-
FAQs
-
Product Consultation
- How Do I Assign the Permissions Required for Using MgC to IAM Users?
- Where Is MgC Available?
- How Do I Prepare for Using MgC?
- How Do I Fix the Error "Failed to access IAM. Check the current user's IAM permissions"?
- Why Can't I Sign the Privacy Statement and Use MgC?
- How Does MgC Ensure Data Security?
- Does Data Collection Affect My Source Services?
-
Network Settings
- What Can I Do If a Source Server Fails the Migration Readiness Check Because Its IP address or Port Is Unreachable?
- What Can I Do If a Source Server Fails the Migration Readiness Check Because the Username or Password Is Incorrect?
- How Do I Fix the Error "Deliver Command to Edge Failed" When a Source Server Fails the Migration Readiness Check?
- What Can I Do If a Source Server Fails the Migration Readiness Check Due to an Unreachable Port, Incorrect Firewall Settings, or Insufficient Access Permissions?
- What Can I Do If Deep Collection Fails on a Source Server Due to Disabled WinRM or an Unreachable IP Address or Port?
-
Server Migration
- How Do I View the Migration Progress When the Migration Workflow Is in the Running State?
- Why the Workflow Status Is Always "Running"?
- How Do I Fix the Error "Edge is not accessible" When a Step in the Migration Workflow Fails?
- How Do I Fix the Error "Server Require to Bind Credential First..." When the Migration Workflow Fails on a Source Server?
- How Do I Handle Resource Exceptions during a Batch Server Migration?
- What Are the Known Errors Related to Server Migration Workflows and How Can I Fix Them?
- What Can I Do If an Error Occurs During the Migration of a VMware Server?
- What Are the Information Mappings Between MgC and SMS?
- Why Is the Migration Progress Inconsistent Between MgC and SMS?
- What Do I Do If I Use a sudo User to Migrate a Source Server and the Server Fails the Source Environment Check?
- What Can I Do If the StartUpAgent Step Fails and the Error Message "System.OutOfMemoryException" Is Displayed?
- How Do I Fix the Error "SMS-Workflow.0503: SMS migration task failed. SMS.xxxx?"
- What Do I Do If Some Disks Are Not Attached to the Target Server After the Migration Is Complete?
-
Storage Migration
- What Are the Restrictions on Using MgC for Storage Migration?
- What Are the Requirements for the Source and Target Environments?
- How Do I Choose the Right Specifications for a Migration Cluster?
- What Affects the Migration Speed of Large Objects?
- What Affects the Migration Speed of Small Objects?
- How Do I View Key Metrics that Affect the Migration Speed?
- Why Is My Storage Migration Workflow Stalled for a Long Time?
- When I Migrate HTTP/HTTPS Data to Huawei Cloud OBS, How Are the Objects with the Same Name but Different URLs Processed?
- When I Migrate Data from OBS to NAS on Huawei Cloud, How Are Objects with the Same Name but Different Capitalization Processed?
- What Are the Constraints on the Length of Object Paths for Migrations Between OBS, NAS, and SMB Storage Systems on Huawei Cloud?
- How Do I Resolve the Problem that a Migration Cluster Fails to Be Created?
- How Do I Obtain Credentials for Accessing Microsoft Azure?
- What Do I Do If the Storage Migration Workflow Fails and "COMPARISON_ATTRIBUTE_NOT_SAME" Is Displayed?
- How Do I Choose Storage Classes?
- What Do I Do If a Migration Task Fails?
- Cross-AZ Migration
- Migration Surveys
-
Resource Discovery
- Known Resource Discovery Problems and Solutions
- Where Can I Find the Collection Failure Cause?
- What Can I Do If an Internet Discovery Task Fails and the Error Message "Network connection timed out" or "Other exception" Is Displayed?
- How Do I Collect Data from a Data Source Again If the Previous Collection Fails?
- How Do I Obtain the Cloud Platform Credentials (AK/SK Pairs)?
- How Do I Obtain the Information for Adding Azure Credentials to MgC?
- How Do I Obtain the Required Credentials Before Using MgC to Perform a Deep Collection for My Azure Object Storage Resources?
- How Do I Configure the Permissions Required for Collecting Details of Azure Containers?
- How Do I Convert the Encoding Format of a CSV File to UTF-8?
- What Can I Do If the Collected Disk Information Is Empty or Incorrect After a Deep Collection Is Performed for a Windows Source Server?
- What Can I Do If the Collected OS Information Is Incorrect After a Deep Collection Is Performed for a Windows Source Server?
- What Can I Do If an RVTools Import Fails?
- What Do I Do If the Deep Collection Succeeds on a Source Server but Some Specifications Information Is Not Collected?
-
Target Recommendations
- Where Can I Find the Assessment Failure Cause?
- Why Can't I Manually Select Target Server Specifications and Disk Types?
- What Can I Do If a Server Assessment Fails and the System Displays a Message Indicating No Proper Specifications Are Matched?
- What Can I Do If a Server Assessment Fails Because the Target Server Specifications Do Not Support Windows Images?
- What Types of Databases Can I Assess Using MgC?
- How Does MgC Generate Target Recommendations?
- Big Data Migration
-
Big Data Verification
- What Do I Do If the Credential List Is Empty When I Create a Data Connection for Big Data Verification?
- Why Are 0 or -1 Displayed in the Hive Verification Results?
- Why Does a Field in Hive Fail the Sum Verification?
- Why Do a Large Number of Tables Fail to Be Verified in a DLI Verification Task?
- How Do I Optimize the Verification Task When the Delta Lake Data Volume Is Large?
- How Do I Replace Packages Before I Create a Connection to a Secured HBase Cluster on the Target Cloud?
- How Do I Replace Packages When I Create a Verification Task for an MRS 3.1.0 Cluster Using Yarn?
- Known Issues and Solutions
-
Product Consultation
- General Reference
Show all
Copied.
Creating a Batch File Storage Migration Plan
Follow this section to configure a migration plan for batch migrating file systems.
The Batch Object Storage Migration template can be used to migrate multiple file systems in a batch. If only one file system needs to be migrated, create a migration workflow directly.
Preparations
- Creating a migration project
Create a migration project on the MgC console. For details, see Managing Migration Projects.
- Creating a migration cluster
Create a dedicated migration cluster for this migration. A cluster consists of a master node and several list and migration nodes. For details about how to create a cluster, see Creating a Migration Cluster.
- Creating target file systems
Create target file systems for receiving migrated source data. For details, see Creating a General Purpose File System or Creating an SFS Turbo File System.
Notes
- Only one migration workflow can be created for a migration plan.
- A maximum of 100 file systems can be added to a migration plan.
- Target file systems included in a migration plan must be in the same region.
Procedure
- Sign in to the MgC console.
- In the navigation pane, choose Design > Migration Plans.
- Click Create Migration Plan in the upper right corner of the page.
- In the Batch File Storage Migration card, click Configure Migration Plan.
- In the Basic Settings area, set parameters listed in Table 1.
- Click Add. A new row will be added below, allowing you to configure a source file system. Each click of this button will add another row, enabling you to include multiple source file systems in this plan.
Figure 1 Adding a source file system
- Configure a source file system based on Table 2.
Table 2 Parameters for configuring a source file system Parameter
Description
Remarks
Storage Type
Supported source storage types include NAS_GFS, NAS_NFS_V3_PROTOCOL, and NAS_NFS_V3_MOUNT.
-
Migration Method
Select a migration method.
- Full migration: This method is used to migrate all data in a specific path in the source file system.
- List migration: This method is used to migrate files and directories recorded in lists.
-
List Path
If the list migration method is used, enter the path to the list files. If the full migration method is used, leave it blank.
A list file must meet the following requirements:
- A list file cannot exceed 30 MB.
- A list file must be a .txt file.
- A list file must be in UTF-8 without BOM.
- Each line in a list file can contain only one file or directory name, and the name must be URL encoded.
- Each line in a list file cannot exceed 16,384 (16 × 1,024) bytes, or the migration will fail.
- A list file can contain a maximum of 10,000 lines.
File System Address
Enter the mount address of the source file system.
- If the storage type is NAS_GFS, the file system address can include a host name, domain name, (optional) subdomain, port, and path.
- If the storage type is NAS_NFS_V3_PROTOCOL or NAS_NFS_V3_MOUNT, the file system address must match any of the following formats:
- <IP-address>:/
- <IP-address>:/<path>
- <domain-name>:/
- <domain-name>:/<path>
For a full migration, the combination of a source file system address and the path to be migrated must be unique. For a list migration, the combination of a source file system address and the list path must be unique. In both cases, the prefix matching rule is applied.
For example, if you have added the file system address 192.168.0.1:/a with a migration path /abc/a, an error will be reported if you add the file system address 192.168.0.1:/a with a migration path /abc. To overwrite an existing path, you need to delete the existing address and path combination first.
Path
Enter the directory where files and directories to be migrated are located. The format is /Folder name.
If the list migration method is selected, enter / in the Path text box.
- Each time after you configure a source file system, click Save in the Operation column. After all source file systems to be migrated are configured, click Next.
- In the list, click Modify in the Operation column to configure a target file system for each source file system.
Table 3 Parameters for configuring a target file system Parameter
Description
Remarks
Source Path
This path is automatically generated by combining the source file system address with the path to be migrated.
-
Storage Type
Only NAS_NFS_V3_MOUNT is supported.
File System Address
- If a General Purpose file system is used as the target, enter the mount address of the file system. To obtain the mount address, go to the file system list and click the
icon next to the address in the Mount Point column.
- If an SFS Turbo file system is used as the target, enter the shared path of the file system. To obtain the shared path, go to the SFS Turbo file system list, click
next to the path in Shared Path column.
Combinations of target file system addresses and paths can be duplicated.
Path
Enter the directory for storing files and directories migrated. The format is /Folder name.
-
- If a General Purpose file system is used as the target, enter the mount address of the file system. To obtain the mount address, go to the file system list and click the
- Each time after you configure a target file system, click Save in the Operation column. After you configure a target file system for each source file system, click Next. You can assess how large of a migration cluster is required for the migration and then create a migration cluster with the recommended specifications. Alternatively, you can skip this step and use an existing migration cluster. For details about how to create a cluster, see Creating a Migration Cluster.
- Click Next to select an existing migration cluster. All resources in this plan will be migrated using this cluster.
- Click Select Cluster. The Select Cluster page is displayed on the right.
- In the cluster list, select the cluster to be used and click OK. The cluster must be in a healthy state. If you want to modify an existing cluster to meet your requirements, see Managing a Migration Cluster.
Figure 2 Selecting a migration cluster
- Click OK. After migration plan is created, you can see it in the list.
- If you need to modify the plan settings, click Design in the Operation column.
- After Completed appears in the Progress column, click Create Workflow in the Operation column to create a migration workflow to migrate all source file systems in the plan in a batch.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot