ZMigrate Migration Service
Overview
Purpose
ZMigrate Migration Service migrates VM instances and their data from a VMware environment to the current ZStack Cloud cloud platform. During migration, you can continuously synchronize data from source VM instances and create test VM instances to verify the migration results before production cutover. This reduces service downtime and migration risks.
ZMigrate Migration Service is provided by the ZStack ZMigrate Migration Service application in Application Market and is independent of the existing Migration Service of the cloud platform. Identify the appropriate service by its page name and license module name.
Key capabilities
- Add a data gateway to establish a data transmission channel between the source environment, ZMigrate service, and target cloud platform.
- Connect to a VMware source platform and discover source hosts and VM instances.
- Configure target compute, storage, and network resources and create migration tasks in batches.
- Perform full or incremental synchronization to continuously synchronize data from source VM instances.
- Create test VM instances before production cutover to verify the operating system, network, applications, and data.
- Retain a rollback snapshot, shut down the source VM instance, and install VMTools as needed to complete service cutover.
Process monitoring and operation tracking
During migration, you can view the migration status, synchronization progress, data transfer rate, and task logs on the migration task list and details pages. The system also records configuration and execution operations for source platforms, data gateways, and migration tasks in Operation Logs on the cloud platform. You can use these logs to view the operator, client IP address, execution status, and failure information.
Before You Begin
Verify the account and licenses
- Log in to the cloud platform with a system administrator account.
- Verify that the cloud platform license is valid and that a valid ZMigrate module license is available.
- Verify that sufficient production or trial migration licenses are available for the number of VM instances that you plan to migrate.
Prepare the VMware source environment
- Prepare the management address, account, and password for accessing vCenter or ESXi.
- Verify that the operating system, disk, and network configurations of the VM instances to be migrated meet the migration requirements.
- Evaluate the disk capacity of the source VM instances, the volume of data changes generated by workloads, and the acceptable downtime. Plan the synchronization and cutover windows accordingly.
Prepare target cloud platform resources
- Prepare the zone, cluster, or host that will run the target VM instances.
- Verify that the target primary storage has sufficient available capacity.
- Prepare the target L3 network. If the target VM instances require security groups, create the security groups in advance.
- If you plan to clone the source VM network configuration, also prepare a temporary L3 network and available IP addresses for the migration.
Verify network connectivity
- The management network used to install the ZMigrate application must be able to communicate with the management node of the cloud platform.
- The data gateway must be able to access the VMware source platform and VM instances to be migrated, and communicate with the ZMigrate service and target cloud platform.
- For a new gateway VM instance, prepare an L3 network, IPv4 address, subnet mask, and default gateway.
Quick Start Workflow
A typical VMware VM instance migration includes the following steps:
- Install the ZStack ZMigrate Migration Service application from Application Market.
- Configure the ZMigrate license and verify that production or trial migration licenses are available.
- Add a data gateway. The data gateway discovers source resources and transfers migration data.
- Add a VMware source platform and use the data gateway to test connectivity.
- Select source hosts and VM instances, configure target compute, storage, and network resources and migration policies, and create migration tasks.
- Perform full synchronization. While source services remain running, perform incremental synchronization multiple times as needed.
- After the migration task reaches the Ready for Cutover status, we recommend that you create a test VM instance to verify operating system startup, network connectivity, applications, and application data.
- Perform the final synchronization and cutover during the planned service window, and verify the target VM instance.
- After services are stable, delete test VM instances, migration tasks, source platforms, and data gateways as needed.
Note: You must add a data gateway before you add a source platform. You must add a source platform before you create a migration task.Install ZStack ZMigrate Migration Service
Prerequisites
Use a ZStack Cloud system administrator account and prepare the following resources:
- An image storage with sufficient capacity.
- A zone, placement, and primary storage for deploying the application.
- A management network that can communicate with the cloud platform management node and an available IP address on that network.
Procedure
- From the ZStack Cloud main menu, choose .
- Locate ZStack ZMigrate Migration Service in all applications and click Install Application.
-
Configure the application.
- Name: Enter a name for the application instance.
- CPU Architecture: Select x86_64.
- Version: Select the ZMigrate version to install.
- CPU and Memory: Specify the offering of the VM instance that runs the application.
- Image Storage: Select the image storage for the ZMigrate application and related gateway and boot images.
- Zone and Placement: Select the zone, cluster, or host where the application will be deployed.
- Primary Storage: Select the primary storage for the application VM instance.
- Management Network: Select a network that can communicate with the cloud platform management node.
- IP Address: Specify an available IP address on the management network.
- Root Volume: Specify the root volume capacity of the application VM instance.
- Verify the configuration and click OK.
Results
After you submit the installation, you can view the application status and parameters in the installed applications. When the application status changes to Installed, you can use the ZMigrate Migration Service menu.Configure a ZMigrate License
ZMigrate Migration Service uses an independent ZMigrate module license, hereinafter referred to as the ZMigrate license. This license is independent of the Migration Service module license of the cloud platform.
In License Management, you can use ZMigrate Authorization Details to view the license quota, used quota, and expiration time for production and trial licenses. You can use Usage Details to view the migration resources that consume licenses and their activation and expiration times. Before you create migration tasks, verify that sufficient licenses are available for the number of VM instances that you plan to migrate.
A ZMigrate license belongs to a specific cloud platform and is not added to the shared pool of the license server. You can configure the license locally on the cloud platform, or use the centralized management portal of the license server to download a request code and upload a license for the corresponding cloud platform. When you use the license server, the license data and related operations are still processed by the ZMigrate service of the corresponding cloud platform. The license is not shared among cloud platforms.
Configure a Local License
Prerequisites
The ZStack ZMigrate Migration Service application is installed.Procedure
-
Go to License Management and download the cloud platform request code.
After you install the ZMigrate application, the system also provides zmigrate.key.
- Use zmigrate.key to apply for a ZMigrate module license.
- Return to License Management, click Upload License, and upload the ZMigrate license.
- Verify that the license card for ZMigrate Migration Service shows a valid status and that the license quota is correct.
Access ZMigrate Migration Service
Prerequisites
The ZStack ZMigrate Migration Service application is installed, and you are logged in with a system administrator account.Results
After you access the service, use Migrate resources to manage source platforms and data gateways. Use Migration tasks to create, synchronize, test, cut over, and manage migration tasks.Add a Data Gateway
About this task
A data gateway accesses the VMware source environment and transfers migration data. Add an available data gateway before you add a source platform.
Procedure
- From the ZStack Cloud main menu, choose .
- Select the Data Gateway tab and click Add Data Gateway.
-
Enter a name for the data gateway and select how to add the gateway.
- Create Gateway VM Instance: The cloud platform creates a gateway VM instance. Configure the zone, placement, CPU, memory, primary storage, disk capacity, L3 network, IPv4 address, subnet mask, and default gateway. The default values for CPU, memory, and disk capacity are 8 cores, 8 GB, and 100 GB. Adjust these values based on the migration scale.
- Use Existing IP: Enter the IP address of a deployed data gateway.
-
If you select Use Existing IP, click Test Connectivity to verify that the current cloud platform can connect to the data gateway.
If the test fails, check the gateway IP address, gateway service status, routing, and firewall settings. Verify that the gateway can access the VMware management address, cloud platform management node, and ZMigrate service.
- Verify the configuration and click OK.
Results
After submission, a data gateway that uses a new gateway VM instance enters the creation process. Wait until the connection status of the data gateway changes to Connected before you add a source platform.What to do next
When you create a gateway VM instance, verify that the IPv4 address is not in use and that the data gateway can access the VMware source environment, ZMigrate service, and target cloud platform.Add a Source Platform
Prerequisites
You have added a connected data gateway and prepared the vCenter or ESXi management address and access credentials.Procedure
- From the ZStack Cloud main menu, choose .
- Select the Source Platform tab and click Add Source Platform.
-
Configure the source platform.
- Name: Enter a name for the source platform.
- Platform Type: Displays VMware. The current version supports only VMware source platforms.
- Platform Address: Enter the IPv4 management address of vCenter or ESXi.
- Data Gateway: Select an added and connected data gateway.
- Account and Password: Enter the credentials for accessing the VMware platform.
- Description: Optional. Enter information such as the purpose of the source platform.
-
Click Test Connectivity.
If you change the platform address, account, or data gateway, the previous test result becomes invalid. Test the connectivity again.If the test fails, check the vCenter or ESXi management address, account and password, data gateway connection status, and network connectivity from the data gateway to the source platform.
- After the test succeeds, click OK.
Results
ZMigrate discovers source hosts and VM instances through the selected data gateway.View and Verify Source Platform Resources
Source platform list
After you add a source platform, verify that its connection status is Connected in the Source Platform list. The list also displays the platform type, source platform IP address, data gateway IP address, and creation time.
Source platform details
- Overview: View the connection status, platform type, number of running VM instances, source platform IP address, data gateway IP address, UUID, and creation time. You can also view the total and available capacity and utilization of CPU, memory, and storage.
- Host Information: View source host names, the number of running VM instances, and CPU, memory, and storage capacity and usage.
Verification items
- The source platform and data gateway are connected.
- The source hosts and VM instances to be migrated can be discovered.
- The capacity information is consistent with the VMware source environment.
Create Migration Tasks
Prerequisites
The source platform and data gateway are connected, the target compute, storage, and network resources are available, and sufficient production or trial migration licenses are available.Procedure
- From the ZStack Cloud main menu, choose .
- On the All tasks tab, click Create a new migration task.
-
Select source VM instances.
- License Type: Select Production License or Trial license. The page displays the number of available licenses of the selected type, the number of selected VM instances, and the number of additional licenses required.
- Source Platform: Select a connected VMware source platform.
- Source Host: Select the VMware host that contains the VM instances to be migrated.
- Select one or more VM instances from the source VM instance list. The list displays the name, IP address, operating system, disk capacity, default gateway, and UUID.
If a VM instance to be migrated is not displayed in the source VM instance list, verify that the source platform and data gateway are connected, the correct source host is selected, and the VM instance is not used by another migration task.
-
Configure target compute and storage resources.
Select the zone, cluster, host, primary storage, storage pool if applicable, disk bus, and CPU mode.
-
Configure the target network.
- Select the target L3 network and security group, and select automatic or static IP address assignment.
- If you use static IP addresses, specify an available and unique IPv4 address, subnet mask, and default gateway for each target VM instance. The system checks for missing, duplicate, or occupied IP addresses.
- If you use static IP addresses, the system automatically enables Automatically install VMTools, and you cannot disable it.
- To clone the source network configuration, select a temporary L3 network and configure a temporary IP address for each target VM instance.
- To retain the source MAC address, ensure that the source and target VM instances are not connected to the same network at the same time. This prevents MAC address conflicts.
-
Configure migration policies.
- Cutover immediately after synchronization is completed: When enabled, the system automatically performs cutover after data synchronization. It does not wait for you to create a test VM instance or manually perform cutover. Enable this option only when pre-cutover testing is not required and you have verified that the target resources and network configuration are available.
- Create a rollback snapshot: Specify whether to retain a rollback snapshot of the target VM instance during cutover.
- Automatically shut down the source VM instance and Shutdown mode: Specify whether to automatically shut down the source VM instance during cutover and select the shutdown mode.
- Automatically install VMTools: Specify whether to automatically install VMTools on the target VM instance. If you use a static IP address, this option is automatically enabled and cannot be disabled.
- Review the source VM instances, target resources, network, and migration policies, and submit the migration tasks.
Results
Each source VM instance corresponds to one migration task. When you select multiple source VM instances, the system creates multiple migration tasks and consumes one migration license for each task. The target VM instance created for each migration task uses the name of the corresponding source VM instance.Synchronize Migration Tasks
About this task
Synchronization copies data from source VM instances to the target cloud platform. Typically, perform full synchronization for the initial migration. While source services remain running, perform incremental synchronization to reduce the data difference during the final cutover.
Procedure
- Under , select the target migration task on the All tasks tab.
- Select a synchronization operation.
-
Select a synchronization mode.
- Full synchronization: Synchronizes all data from the source VM instance. If the task has completed initial synchronization, the system performs a comparison scan before another full synchronization. This scan typically takes a long time.
- Incremental synchronization: Synchronizes only data that has changed since the last synchronization.
- Confirm the synchronization.
Results
In the task list, you can view the migration status, sync rate, read/write rate, log process, and task synchronization time.What to do next
Before production cutover, perform incremental synchronization again. Stop writes to the source system as required by your service plan to reduce data differences during cutover.Create a Test VM Instance
Prerequisites
The migration task has completed data synchronization and has a recovery point that can be used to create a test VM instance.Procedure
- On the All tasks tab of Migration tasks, select the target migration task and click Create Test VM Instance.
- Configure the CPU and memory of the test VM instance.
-
Configure the test network.
Select an L3 network and security group, and specify the IPv4 address, subnet mask, and default gateway.
- Select the recovery point for creating the test VM instance.
-
Select a system conversion policy.
- Perform system conversion: Converts the system and installs drivers for the target cloud platform.
- Convert without installing driver: Performs system conversion without automatically installing drivers.
- Skip system conversion: Creates the test VM instance directly from synchronized data.
- Verify the configuration and create the test VM instance.
What to do next
Use a network isolated from the production service for the test VM instance. This prevents IP address or MAC address conflicts with the source VM instance that is still running.Verify Migration Results
Prerequisites
The test VM instance was created successfully. On the Tests tab of Migration tasks, verify that the test task is in a normal state, and then log in to the test VM instance.- Verify that the operating system starts normally and that the system time, CPU, and memory specifications are as expected.
- Verify the number, capacity, partitions, file systems, and critical data of root and data volumes.
- Verify the NICs, IP addresses, routes, DNS settings, and security group policies.
- Verify applications, services, middleware, and their dependent components.
- Verify the operating system drivers and VMTools status.
Results
After successful verification, you can schedule the production cutover.What to do next
If the test VM instance cannot start or be accessed, check the recovery point, system conversion policy, target L3 network, IP address, security group, and operating system drivers. Download diagnostic logs to troubleshoot the problem. After you modify the related configuration, synchronize the data again and create another test VM instance for verification.Perform Cutover
Prerequisites
The migration task is in the Ready for Cutover status, and the planned service window has started. Before cutover, we recommend that you create a test VM instance and complete workload verification.
Warning: After cutover, the system enables the target VM instance. If Automatically shut down the source VM instance is enabled, the system also shuts down the source VM instance by using the selected shutdown mode. Before cutover, verify the source data write status and target network configuration. Ensure that the source and target VM instances do not use the same IP address or MAC address at the same time.Procedure
- Stop or restrict writes to the source system and perform the final incremental synchronization according to your service plan.
- Verify that the target compute, storage, and network resources are available.
- On the migration task details page or configuration editing page, verify the cutover policies, including the source VM instance shutdown mode, rollback snapshot, and VMTools installation.
- On the All tasks tab, select one or more migration tasks and click Cutover.
- Review the migration tasks to be cut over and read the risk notice.
- Enter the lowercase word cutover in the confirmation dialog and click Confirm cutover.
Verify the Target VM Instance
Prerequisites
Cutover is complete. Go to the VM instance list on the cloud platform and locate the target VM instance.- Verify that the migration task status is Cutover Succeeded and that the target VM instance is created and running normally.
- Verify the CPU, memory, volumes, disk bus, and CPU mode.
- Verify the L3 network, IP address, MAC address, security group, routes, and DNS settings.
- Verify the operating system, drivers, and VMTools status.
- Verify application services, application access, and data consistency.
Results
After you verify data consistency and service stability, you can release the source resources or delete the migration task according to the migration plan.What to do next
Warning: Do not release source resources before service verification succeeds.If verification fails, stop directing new service traffic to the target VM instance, retain the source resources, and check the target network, drivers, VMTools, application services, and migration logs. Resolve the problem according to your service recovery plan. If you need assistance, contact official technical support.
View Migration Task Details
List information
Under , the All tasks tab displays the migration task name, migration status, source operating system, disk capacity, sync rate, read/write rate, log process, and task synchronization time.
Details
- Overview: View source VM instance information, VM instance configuration, and migration configuration.
- Task Logs: View task logs generated during migration and download diagnostic logs.
Key status information
- Migration status: Determine whether the task is in the synchronization, ready for cutover, cutover, or failure stage, and identify the operations that you can perform.
- Sync rate (%): View the percentage of source data that has been synchronized.
- Read/write rate (MB/sec): Evaluate the current data transfer performance and estimated completion time.
- Log process: Verify that migration-related processes are running normally.
- Task synchronization time: Determine whether the most recent data synchronization time meets the cutover requirements.
Note: Available operations vary by migration status. Before you perform synchronization, testing, cutover, or deletion, verify the task status and related risks.Edit a Migration Configuration
About this task
You can edit the configuration only for migration tasks in the Sync Stopped or Ready for Cutover status. You can modify the target network and cutover policies, but cannot modify target compute or storage resources.
Procedure
- On the All tasks tab of Migration tasks, locate the target migration task.
- From the task actions, select Edit configuration.
-
Modify the target network configuration as needed.
You can modify the target L3 network, CIDR, IP address, subnet mask, default gateway, security group, and whether to retain the source MAC address.
-
Modify cutover policies as needed.
You can modify whether to perform cutover immediately, create a rollback snapshot, automatically shut down the source VM instance, and automatically install VMTools. You can also modify the shutdown mode.
- Review the changes and save the configuration.
What to do next
After you modify the target network configuration, we recommend that you create another test VM instance to verify network connectivity and application availability.Manage Test VM Instances
Test task information
On the Tests tab of the Migration tasks page, you can view the test task name, migration status, source operating system, disk capacity, sync rate, read/write rate, log process, and task synchronization time.
Available operations
Test VM instances are intended only for pre-cutover verification and are not intended to run production workloads. When a test task is in the Test Task Running, Test Task Recovery Completed, or Test Task Failed status, you can delete the corresponding test VM instance from the actions menu.
Warning: A deleted test VM instance cannot be recovered, and its test resources are released. Before deletion, verify that you no longer need to retain the test environment or troubleshooting information.Download Diagnostic Logs
About this task
If synchronization, testing, or cutover of a migration task fails, download diagnostic logs to troubleshoot the problem.
Procedure
- On the All tasks tab of Migration tasks, locate the target migration task.
- Click the migration task name to open the task details page.
- Select the Task Logs tab and click Download diagnostic logs.
- After the download is complete, save the log file and analyze it together with the task status, failure time, and operation records.
What to do next
When you contact official technical support, provide the migration task name, source platform, data gateway, failure time, related operation records, and diagnostic logs.Delete Migration Tasks
About this task
You can directly delete tasks in the synchronization stage. For tasks in the Cutting Over, Cutover Succeeded, or Cutover Failed status, you must select a target VM instance processing policy.
For batch deletion, you cannot select tasks in the synchronization stage and tasks in the cutover stage at the same time. For tasks in the cutover stage, you can select only a target VM instance processing policy supported by all selected tasks.
Procedure
- On the All tasks tab of Migration tasks, select one or more tasks.
- Click Delete.
-
For tasks that have entered the cutover stage, select a target VM instance processing policy.
The system selects Keep the target instance and delete the migration task by default.
- Keep the target instance and delete the migration task: Deletes the migration task and related records, but retains the target VM instance. You can reconfigure the source VM instance and create a new migration task later.
- Delete the target instance and delete the migration task: Deletes the target VM instance, migration task, and related records. Deleted resources and records cannot be recovered.
- Delete the cutover program and roll back the target instance: Deletes the cutover program and restores the target VM instance to its pre-cutover state. This policy is supported only for tasks in the Cutting Over or Cutover Failed status that have Create a rollback snapshot enabled. State and data changes made during cutover are lost.
Note: For batch deletion, if any selected task is in the Cutover Succeeded status or does not have Create a rollback snapshot enabled, you cannot select Delete the cutover program and roll back the target instance. - Read the risk notice, verify the deletion scope and resource processing method, and enter the lowercase word delete as prompted.
- Click Confirm deletion.
Results
The system processes the deletion request in the background. View the result in the task center of the cloud platform. If some tasks in a batch deletion fail, view the failure reason for each task in the operation details.Manage Source Platforms
List information
On the page, you can view and manage added VMware source platforms.
The source platform list displays the name, connection status, platform type, source platform IP address, data gateway IP address, and creation time. You can search for a source platform by name, IP address, or UUID and filter source platforms by connection status.
Details
Click a source platform name to open its details page and view basic information, capacity information, and host information. If the source platform is disconnected, check the platform address and credentials, data gateway connection status, and network connectivity from the data gateway to the VMware management address.
Available operations
- Edit name: Change the source platform name.
- Modify configuration: Change the source platform address, access credentials, or data gateway. After you modify the configuration, test connectivity again. You can submit the configuration only after the test succeeds.
- Test Connectivity: Check the connection between the data gateway and source platform.
- Delete: Delete a source platform that is no longer used. For details, see "Delete a Source Platform."
Delete a Source Platform
Prerequisites
Verify that the target source platform is no longer used.Procedure
- On the Source Platform tab of Migrate resources, select the target source platform.
- Select the delete operation.
- Read the risk notice and confirm the deletion.
Manage Data Gateways
List information
On the page, you can view and manage data gateways.
The data gateway list displays the name, connection status, IP address, connection count, UUID, and creation time. You can search for a data gateway by name, IP address, or UUID and filter data gateways by connection status.
Connection status
If a data gateway is disconnected, verify that the gateway VM instance or existing gateway service is running normally. Also check network connectivity from the gateway to the VMware source platform, cloud platform management node, and ZMigrate service.
Available operations
- Refresh: Refresh the data gateway information and connection status.
- Edit name: Change the data gateway name.
- Test Connectivity: Check the connection between the cloud platform and data gateway.
- Delete: Delete a data gateway that is no longer used. For details, see "Delete a Data Gateway."
Delete a Data Gateway
Prerequisites
Verify that the target data gateway is no longer used.Procedure
- On the Data Gateway tab of Migrate resources, select the target data gateway.
- Select the delete operation.
- Read the risk notice and confirm the deletion.