Step 4: Customizing virtual machine configurations

When migrating multiple virtual machines in a single migration task, you can click Batch edit in the upper left corner of the dialog box to set configurations for all virtual machines at once.

Select a storage policy for the virtual volumes on the destination virtual machines. The Arcfra Virtualization Engine on the destination cluster will create virtual volumes according to the storage policy configured here.
- Redundancy policy
  - Replication: Includes 2 replicas and 3 replicas.
  - Erasure coding: The system will automatically select the recommended erasure coding configuration based on the number of nodes in the cluster after migration. You can also click the drop-down box to re-select the configuration.
    
    Note:
    
    If the destination cluster is an active-active cluster, only the 3-replica redundancy policy is supported.
- Provisioning: Includes thin provisioning and thick provisioning.
The Estimated data space required value displayed at the bottom of the page will be updated based on the storage policy you select. If this data shows 0, check the browser cache and refresh the data.
Determine whether to configure virtual NICs for the destination virtual machines.
- Manually configure static IP (displayed only when the destination site has an Arcfra VMTools image): This option allows you to manually configure the IP address, subnet mask, and the gateway for virtual NICs.
  
  If the source virtual machines have VMware Tools installed and are in the Running state, enabling this option will automatically enter the IP address, subnet mask, and gateway of virtual NICs of the source virtual machines. These configurations can be manually modified. You can reset the configurations to the NIC configurations of the source virtual machines by clicking Set as the source virtual machine IP on the right. After you complete the configurations, the DNS settings of the source virtual machines, if accessible, will also be configured for the destination virtual machines.
  Note:
  - Due to differences in NIC naming rules between VMware ESXi and AVE, when virtual machines are migrated from VMware ESXi to AVE, the names of the virtual NICs might change, rendering the original virtual NIC configurations ineffective. Therefore, it is recommended to tick Manually configure static IP if you want to keep the original NIC configurations or manually configure the virtual NICs for the destination virtual machines.
  - Once Manually configure static IP is ticked, the destination virtual machines will automatically start and install Arcfra VMTools.
  - After the migration is complete, if the static IP of the virtual NICs on the destination virtual machines do not take effect, check whether the content of the virtual NIC configuration files is correct.
- Keep MAC address: This option will retain the MAC addresses of the virtual NICs of the source virtual machines for the destination virtual machines.
  
  Note:
  
  Once enabled, if the source and the destination virtual machines are within the same LAN, ensure that they will not be in the Running state simultaneously after the migration, otherwise there might be network access issues for the virtual machines.
Determine whether to perform data consistency check and whether to automatically start the destination virtual machines once the migration completes.

If you enable Perform data checksum, a data consistency check will be performed after the data migration is complete, along with a longer shutdown time for the source virtual machines. The time taken for data check depends on the actual data size migrated by Arcfra Migration Tool. The larger the data size, the longer the check.
Click Create.

After the migration task is successfully created, the page will be automatically redirected to the In progress page, which displays the execution status of the migration task. You can refer to the Managing in-progress migration tasks section to perform corresponding operations on the migration task.