What's in this release

What's new

• Supports deploying the migration tool with a controller-worker architecture:
  • The controller provides the web console and is responsible for creating and scheduling migration plans, as well as monitoring their status.
  • The worker performs the actual data migration. Each environment includes one local worker by default and supports adding remote workers to increase transfer concurrency.
• Supports completing system initialization and creating an administrator account when you access the controller for the first time. After the initialization is complete, you can use this account to log in to the controller console.
• Adds the Overview page as the default page displayed after login. This page provides a real-time summary of the global migration status and system running status.
• Adds the Plans page to substitute for the previous migration task creation process. When you create a migration plan, the wizard now includes the following 7 steps instead of the previous 4 steps:
  • Configuring the basic information.
  • Selecting the source site.
  • Selecting virtual machines.
  • Configuring the target cluster.
  • Configuring network mappings.
  • Configuring virtual machines.
  • Scheduling the migration plan.
• Supports configuring synchronization schedule for full migration, incremental synchronization, and cutover when creating a migration plan:
  • Full migration can be either triggered immediately or delayed until a specified time.
  • Incremental synchronization can be triggered either manually or automatically on a periodic basis with a minimum synchronization interval of 1 hour.
  • A specified time window can be configured for the controller to perform automatic incremental synchronization.
• Supports assigning different virtual machines in the same plan to different target clusters when creating a migration plan. The system will automatically select the worker node to perform the migration based on the status and current load of workers. Manual specification is no longer required.
• Adds the migration plan list, migration plan details page, and migration task details page for a single virtual machine to display the migration plan status at different granularities. Canceling migration plans manually is also supported.
• Adds the System configuration page for operations including changing the current account password, and configuring DNS servers used by the controller.
• Adds the Workers page for viewing the health status and concurrency information of all registered worker nodes.
• Supports exporting the execution records of migration plans to the local computer in CSV or PDF format.
• Adds support for migrating Anolis OS 7.9, SUSE Linux Enterprise Server 15 SP7 64-bit, or Debian 13.5 virtual machines.

Improvements

• Moves the DNS server configuration entry to the System configuration page. After the DNS configuration is saved, the changes take effect immediately on the local worker, and other worker nodes will automatically synchronize the changes in 30 seconds.
• Optimizes batch operation capabilities on the migration plan list and details pages. Now operations can be performed in batches on the migration plan details page, including incremental synchronization, cutover, and archive cleanup.
• Optimizes how the migration plan progress is displayed. The migration plan list and details pages can display the overall plan progress, virtual machine status distribution, and migration stage of each virtual machine, making it easier to understand the migration progress.

Resolved issues

• Migration tasks could fail when slow VMware snapshot deletion triggered a timeout. The issue has been resolved in this release.
• After driver injection succeeded, virtual machines were created with the scsi bus by default, which caused migrated virtual machines to fail to start because the bus type was incompatible. The issue has been resolved in this release.
• Redis had known security vulnerabilities. The issue has been resolved in this release by upgrading Redis to version 8.6.3.
• VMware virtual machine NICs that use NSX-T networks could not be correctly identified. The issue has been resolved in this release.
• Driver injection could fail when /etc/rc.local did not exist. The issue has been resolved in this release.
• The accounts API returned encrypted passwords. The issue has been resolved in this release.
• The iSCSI target created by the migration tool had Adaptive IQN Whitelist disabled, which restricted storage connections and thus could affect migration. The issue has been resolved in this release.
• The estimated data space value on the assigned virtual machines page was inaccurate. The issue has been resolved in this release.
• IP ranges were not supported when configuring IP addresses in batches. The issue has been resolved in this release.
• DVS (distributed virtual switch) port group networks could not be correctly identified. The issue has been resolved in this release.
• If the server.yaml configuration file contained errors, the controller could not start, causing the login page to unexpectedly display an error. The issue has been resolved in this release.
• Accessing Arcfra Migration Tool through HTTP port 80 would fail. The issue has been resolved in this release.
• In specific scenarios where a virtual machine triggered UNMAP operations, CBT (Changed Block Tracking) returned changed blocks close to the full disk size, causing the amount of incremental migration data to increase abnormally and the migration time to increase significantly. The issue has been resolved in this release.
• Migration tasks in the Pending dispatch state could still be selected again and triggered repeatedly for migration. The issue has been resolved in this release.
• The vCPU count of virtual machines in a migration plan was always displayed as 1. The issue has been resolved in this release.