Applicable Products
- QuTS hero h5.3.0 or later
- Virtualization Station 4.0 Beta or later
Introduction
VM High Availability (VMHA) is a feature in Virtualization Station that enables automatic failover of virtual machines between two QNAP NAS devices. It helps ensure service continuity in case of hardware failure by minimizing downtime.
This tutorial guides you through the complete setup process, including preparing your environment, creating a VMHA device pair, creating and managing VMHA groups, configuring failover, and troubleshooting common issues.
VMHA Requirements
System Requirements
| Component | Requirement |
|---|
| Operating system | QuTS hero h5.3.0 or later on both NAS devices. Note For best compatibility, it is recommended to use NAS devices that are running the same version of QuTS hero. |
| Processor | Both NAS devices must use CPUs from the same vendor (e.g., Intel® or AMD®). |
| Memory | The destination NAS must have enough memory to run the migrated virtual machines from the source NAS during failover. |
| Storage | Both NAS devices must have sufficient space for Virtualization Station to create a shared folder to store the VMHA disk images. Disk images must be stored on the NAS’s internal storage only, and external storage cannot be used. |
Network Requirements
| Component | Requirement |
|---|
| Network connections | At least two independent network connections are required between the two NAS devices. These must be on different subnets: one for the management link and one for the availability link (used for data synchronization). |
| IP addresses | All interfaces used for HA must use static IPv4 addresses. IPv6 and VLAN settings must be disabled. |
| Firewall ports | If a firewall is in use, ensure that TCP ports 16500-16550 are open between the two NAS devices to allow HA communication. For a complete list of service ports used by QNAP systems, see What network ports are used by QTS, QuTS hero, and QuTScloud systems. |
| Availability link | A network speed of at least 2.5 Gbps is strongly recommended, as link speed directly affects VM performance. For best performance, use a direct Ethernet connection between the NAS devices, avoiding switches when possible. |
| SSH service | The SSH service must be enabled on both NAS devices. For details, see Configuring SSH connections in the QuTS hero User Guide. |
Preconfiguration Requirements
- Configure compatible virtual switches on both NAS devices using Network & Virtual Switch. While the virtual switch names do not need to match, the interface assignments and network settings must be aligned. For details, see Virtual switch configuration in the QuTS hero User Guide.
- Ensure that both NAS devices are running the same version of QuTS hero. If the firmware versions differ, VMHA might not function as expected. To update the NAS firmware, see Firmware update in the QuTS hero User Guide.
- Configure both NAS devices to use the same NTP server for time synchronization. For details, see Configuring time settings in the QuTS hero User Guide.
- Ensure required ports are open or forwarded if using firewalls or NAT.
Warning
- VMHA cannot be enabled if either NAS is part of a Hero HA cluster. Ensure that both devices are in standalone mode by unpairing any existing Hero HA configuration before proceeding.
- Both NAS devices must run the same version of Virtualization Station. If the versions differ, such as after a system or app update, all HA protection groups will be paused automatically until version consistency is restored.
Procedure
Setting up virtual machine high availability (VMHA) involves three main steps to ensure that your virtual machines remain operational if the source NAS becomes unavailable.
- Create an HA Device Pair: Connect two NAS devices to form a high availability group. This step only pairs the two NAS devices, including verifying requirements, configuring the network connection for synchronization, and binding the virtual switches used by the VM. It does not include the future HA synchronization direction for the VMs.
- Create an HA Availability Group: Defines which virtual machine to protect, sets up the synchronization direction, and allocates storage on both NAS devices. This group manages the backup and recovery process for the VM.
- Configure the Failover Policy: Specifies the conditions that will automatically trigger failover, such as hardware issues or high resource usage.
Completing these steps ensures that selected virtual machines can be automatically restarted on the destination NAS in the event of a failure, minimizing service disruption.
Create an HA Device Pair
- Open Virtualization on the local NAS.
- Go to High Availability.
- Click Configure Paired Devices.
The Configure Paired Devices for VM Availability wizard opens. - Click Start.
- Review the requirements for paired devices.
- Click Next.
- Configure the local device settings.
Important
If you are using a direct physical connection (such as a dedicated Ethernet cable between the two NAS devices), do not select the adapters to configure the M-link (management link). Assigning an IP address in this scenario can cause Virtualization Station to report connection errors.
- Specify the IP address of the local device.
- Specify the device port number.
- Optional: Select Use SSL connection.
- Specify the device username.
- Specify the device password.
- Click Next.
- Configure the remote device settings.
- Specify the IP address of the remote device.
- Specify the device port number.
- Optional: Select Use SSL connection.
- Specify the device username.
- Specify the device password.
- Optional: Click Test.
Virtualization Station tests the local and remote device connection.
- Click Next.
The Configure Paired Devices and Their Credentials window appears.
- Review the local and remote device settings.
- Click Next.
The Configure Availability Link (A-Link) window appears.
- Select the A-link adapters for the local and remote device.
Note
Click List All to view all the adapters linked to the local or remote device.
- Click Test.
Virtualization Station tests the A-link connectivity. - Click Next.
The Configure VM Network Settings window appears. - Configure the VM network settings for the paired devices.
- Click Add.
The Pairing VM Networks window appears.
- Select the virtual switches for the local and remote devices.
Important
- The virtual switch or switches you select in this step determine which VMs can be protected by HA. Only VMs connected to the selected virtual switches will be available for selection.
- The wizard filters out incompatible virtual switches automatically. This includes switches that are not linked to a physical network adapter, reserved for system use (such as Docker or LXD), or configured with NAT or DHCP server functions.
If a virtual switch is missing from the list, review its settings in Network & Virtual Switch.
- Click Add.
Virtualization Station adds the virtual switches to the paired devices.
- Click Next.
The Other Settings window appears. - Configure the failover policy settings.
For details, see Configuring Failover Policy Settings. - Click Next.
- Review the settings.
- Click Finish.
Virtualization Station creates the HA device pair.
Tip
To manage the configured VMHA device pair, go to High Availability > Paired Devices.
- Go to Actions > Edit Paired Devices to update the configuration.
- Go to Actions > Unpair Paired Devices to remove the pairing.
Configure an HA Availability Group or Plan
Note
The Beta version of Virtualization Station 4.0 allows each NAS to create up to two HA availability groups, with each group limited to a single virtual machine.
- Log in to your local NAS.
- Open Virtualization Station.
- Next to Create Virtual Machine, click
. - Click Create Availability Group.
The Availability Groups window appears. - Click Start.
The Create Availability Group window appears. - Select the synchronization direction.

Note
The synchronization direction defines which NAS acts as the source and which NAS receives the VM data as a high-availability backup. The list of virtual machines displayed during the selection step depends on the chosen source NAS.
- Click Next.
- Configure the HA group settings.
- Specify an HA group name.
Note
A shared folder with the same name as the HA protection group is created in the selected storage pool on both the local and remote NAS devices. Ensure that the folder name is unique on each device to prevent naming conflicts.
Warning
Do not rename this folder for any VM that is already protected, as this may cause unexpected issues.
- Select the source device storage pool.
- Select the destination device storage pool.
- Specify the allocated quota for shared folder.
Note
Click Use Available Pool Capacity to automatically assign the smaller of the available capacities from the selected local and remote storage pools.
- Click Create.
The High Availability (HA) Group Configuration window appears. - Verify the configured group settings.
- Click Next.
The Virtual Machines window appears.
- Under the source device (local or remote device), click List Available.
- Select one or more virtual machines to include in the VMHA deployment.
- Click Next.
The Settings window opens. - Optional: Select Automatically resume the plan.
This option automatically restarts the HA plan after a reboot or interruption. - Click Next.
The Summary window opens. - Review the HA group settings.
- Click Create.
Virtualization Station creates the HA availability group.
Configure Failover Policy Settings
- Open Virtualization Station.
- Go to High Availability > Failover Policy.
- Configure the monitoring interval. This defines how frequently the system checks for failover conditions.
- Optional: Under Triggered Events, select the conditions that should trigger a failover. You can configure the following settings:
- Backup power mode: Initiates failover when the device runs on an Uninterruptible Power Supply (UPS).
- PSU redundancy loss: Initiates failover when the redundant power supply unit is disconnected or malfunctioning.
- System fan failure: Initiates failover when a system fan is not functioning properly.
- CPU load average exceeds threshold: Initiates failover when average CPU usage exceeds a defined percentage over a set duration.
- Memory load average exceeds threshold: Initiates failover when average memory usage exceeds a defined percentage over a set duration.
- Disk health error: Initiates failover when a virtual machine disk experiences a health issue or when a shared folder volume encounters an error.
- Network virtual switch error: Initiates failover when the virtual switch encounters a network-related error.
- Click Apply.
Virtualization Station saves and applies the failover policy settings to all the VMHA availability groups.
VMHA Monitoring, Troubleshooting, and Diagnostics
Monitor and Manage VMHA Groups
You can view the status of all VMHA groups, perform actions such as pause, resume, edit, or delete, and monitor synchronization progress and resource usage across both NAS devices.
Perform VMHA Actions
After an HA protection group is created, you can monitor and manage its status from the High Availability > Plans page.
- Open Virtualization Station.
- Go to High Availability > Plans.
- Under Action, click
. - Identify a VMHA group or plan.
- Perform any of the following VMHA plan tasks.
| Task | Description |
|---|
| Switchover | Switches VMs between two NAS devices while keeping them online and operational, without requiring a reboot or suspension. |
| Pause | Temporarily suspends VMHA synchronization and failover protection for the HA group. |
| Delete | Removes the VMHA group and disables protection for the associated VM. |
| Resume | Restarts VMHA synchronization and failover monitoring for the group. |
| Edit | Opens the VMHA group settings for configuration changes. |
Note
If the Virtualization Station versions on the two NAS devices become inconsistent, a warning banner will appear on this page. All HA protection groups will be automatically paused until version consistency is restored.
Status Descriptions
| Status | Description |
|---|
Normal | The VMHA group is operating normally with no issues. |
Syncing | Initial or scheduled synchronization is in progress between the source and destination NAS. |
Pause | Synchronization is temporarily halted. The availability group is not actively syncing, but its configuration is preserved. Note This state can occur automatically if Virtualization Station is stopped or the NAS is shut down. |
Warning | VMHA protection is still active, but one or more issues may affect failover. Review and address the underlying causes promptly. |
Error | One or more critical failures have occurred. The VMHA group is no longer functioning correctly and requires immediate attention. |
Diagnose and Troubleshoot Common VMHA Conditions
To ensure stable and reliable HA operation, monitor system conditions and avoid configuration changes that may affect failover readiness.
Common Warning Conditions
| Warning | Description | Impact |
|---|
| Insufficient memory on the destination NAS | The available memory on the destination NAS is not enough to start the protected VM during a failover. | Failover will fail unless memory resources are increased or freed. |
| Degraded availability link | The availability link throughput has dropped below 50 Mbps or latency has exceeded 1 millisecond. | Reduced sync performance and increased recovery point objective (RPO). |
| Device pair configuration issues | Misconfigurations such as unstable management links or subnet mismatches between paired Virtual Switches. | Failover reliability may be compromised if not corrected. |
Warning
Do not modify or delete any virtual switch that is part of a VMHA pair. Changing or removing a paired virtual switch will result in a loss of network connectivity for the protected VM after failover and may cause the HA group to enter an error state.
Troubleshoot VMHA Group Issues
| Issue | Recommendation |
|---|
| Virtualization Station version mismatch | Ensure both NAS devices are running the same version of Virtualization Station. Check App Center for updates. Restart the app if needed. |
| Insufficient CPU or memory on source or destination NAS | Check system resource usage on both the source and destination NAS. Failover may fail if either system lacks sufficient CPU or memory to complete the process. Shut down unused VMs or services to free up resources. If necessary, consider upgrading the system memory. |
| Slow synchronization speeds or high latency | Use a direct network cable between NAS devices, or assign the availability link to a dedicated, high-speed subnet. |
| Virtual switch pairing errors | Open Network & Virtual Switch and confirm both switches are on the same subnet and have no conflicting settings (e.g., NAT or DHCP). |
| Cluster fails to create or join | Ensure both NAS devices are not already members of another Hero HA or VMHA cluster. Unpair any existing clusters before proceeding. |
Manage VMHA Logs
You can view and download VMHA-related logs to assist with troubleshooting, auditing, or verifying the system’s failover behavior. These logs provide detailed records of synchronization events, status changes, and system alerts, helping administrators diagnose issues and maintain operational visibility.
- Open Virtualization Station.
- Go to High Availability > Logs.
- Perform any of the following tasks.
- Search logs: Enter keywords in the search bar to filter log entries by event type, VM name, or timestamp.
- Download logs: Click Save under Actions to export the current VMHA log data as a CSV file for offline analysis or support.
Further Reading
適用產品
- QuTS hero h5.3.0 or later
- Virtualization Station 4.0 Beta or later
簡介
VM 高可用性 (VMHA) 是 Virtualization Station 中的一項功能,能夠在兩台 QNAP NAS 裝置之間自動進行虛擬機的容錯移轉。它有助於在硬體故障時透過減少停機時間來確保服務的連續性。
本教學將引導您完成整個設置過程,包括準備環境、建立 VMHA 裝置配對、建立和管理 VMHA 群組、配置容錯移轉,以及排除常見問題。
VMHA 要求
系統需求
| 元件 | 需求 |
|---|
| 作業系統 | 兩台 NAS 裝置上均需安裝 QuTS hero h5.3.0 或更新版本。 註 為了獲得最佳相容性,建議使用運行相同版本 QuTS hero 的 NAS 裝置。 |
| 處理器 | 兩臺 NAS 裝置必須使用來自相同供應商的 CPU(例如 Intel® 或 AMD®)。 |
| 記憶體 | 目標 NAS 必須有足夠的記憶體來在容錯移轉過程中運行從來源 NAS 遷移的虛擬機。 |
| 儲存空間 | 兩台 NAS 裝置必須有足夠的空間讓 Virtualization Station 建立共用資料夾以存儲 VMHA 磁碟映像。磁碟映像必須僅存儲在 NAS 的內部儲存空間上,不能使用外部儲存空間。 |
網路需求
| 元件 | 需求 |
|---|
| 網路連線 | 兩台 NAS 設備之間至少需要兩個獨立的網路連線。 這些連線必須位於不同的子網中:一個用於管理連線,另一個用於可用性連線(用於資料同步)。 |
| IP 位址 | 所有用於 HA 的介面必須使用靜態 IPv4 位址。IPv6 和 VLAN 設定必須停用。 |
| 防火牆埠 | 如果使用防火牆,請確保兩台 NAS 設備之間的 TCP 埠 16500-16550 是開放的,以允許 HA 通訊。 如需 QNAP 系統使用的服務埠完整列表,請參見QTS、QuTS hero 和 QuTScloud 系統使用的網路埠。 |
| 可用性連線 | 強烈建議網路速度至少為 2.5 Gbps,因為連線速度直接影響 VM 效能。為了獲得最佳效能,請在 NAS 裝置之間使用直接的乙太網連線,盡量避免使用交換器。 |
| SSH 服務 | 必須在兩台 NAS 設備上啟用 SSH 服務。如需詳細資訊,請參見設定 SSH 連線中的QuTS hero 使用者指南。 |
預配置需求
- 使用網路與虛擬交換器在兩台 NAS 設備上配置相容的虛擬交換器。雖然虛擬交換器名稱不需要匹配,但介面分配和網路設定必須一致。如需詳細資訊,請參見虛擬交換機設定中的QuTS hero 使用者指南。
- 確保兩台 NAS 設備運行相同版本的 QuTS hero。如果韌體版本不同,VMHA 可能無法如預期運作。要更新 NAS 韌體,請參見韌體更新中的QuTS hero 使用者指南。
- 配置兩台 NAS 設備使用相同的 NTP 伺服器進行時間同步。如需詳細資訊,請參見設定時間中的QuTS hero 使用者指南。
- 確保開啟或轉發所需的連接埠,如果使用防火牆或 NAT。
警告
- 如果任一 NAS 是 Hero HA 叢集的一部分,則無法啟用 VMHA。在繼續之前,請確保兩個設備都處於獨立模式,解除任何現有的 Hero HA 配置。
- 兩台 NAS 設備必須運行相同版本的 Virtualization Station。如果版本不同,例如在系統或應用程式更新後,所有 HA 保護群組將自動暫停,直到版本一致性恢復。
程式
設置虛擬機高可用性 (VMHA) 涉及三個主要步驟,以確保當源 NAS 無法使用時,您的虛擬機仍然可運行。
- 建立 HA 裝置對: 連接兩台 NAS 設備以形成高可用性群組。此步驟僅配對兩台 NAS 設備,包括驗證要求、配置同步的網絡連接以及綁定 VM 使用的虛擬交換機。不包括未來 VM 的 HA 同步方向。
- 建立 HA 可用性群組: 定義要保護的虛擬機,設置同步方向,並在兩台 NAS 設備上分配儲存空間。此群組管理 VM 的備份和恢復過程。
- 設定故障轉移政策: 指定將自動觸發容錯移轉的條件,例如硬體問題或高資源使用率。
完成這些步驟可確保選定的虛擬機器在發生故障時能自動在目標 NAS 上重新啟動,從而將服務中斷降至最低。
建立 HA 裝置配對
- 在本地 NAS 上開啟 Virtualization。
- 前往高可用性。
- 按一下配置配對設備。
配置 VM 可用性的配對設備精靈開啟。 - 按一下開始。
- 檢閱配對裝置的要求。
- 按一下下一步。
- 配置本地裝置設定。
重要
如果您使用直接物理連接(例如兩台 NAS 設備之間的專用乙太網線),請勿選擇適配器來配置 M-link(管理鏈接)。在此情況下分配 IP 位址可能會導致 Virtualization Station 報告連接錯誤。
- 指定本地裝置的 IP 位址。
- 指定裝置的連線埠號碼。
- 選擇性:選擇使用 SSL 連線。
- 指定裝置的使用者名稱。
- 指定裝置密碼。
- 按一下下一步。
- 設定遠端裝置的設定。
- 指定遠端裝置的 IP 位址。
- 指定裝置的埠號。
- 選擇性:選取使用 SSL 連線。
- 指定裝置使用者名稱。
- 指定裝置密碼。
- 選擇性:按一下測試。
Virtualization Station 測試本地和遠端裝置的連線。
- 按一下下一步。
[設定配對裝置及其憑證]視窗隨即顯示。
- 檢視本地和遠端裝置的設定。
- 按一下下一步。
[設定可用性連結 (A-Link)]視窗隨即顯示。
- 選擇本地和遠端裝置的 A-link 配接器。
註
按一下列出所有 以檢視連線到本地或遠端裝置的所有配接器。
- 按一下測試。
Virtualization Station 測試 A-link 連接性。 - 按一下下一步。
[設定 VM 網路設定]視窗隨即顯示。 - 設定配對裝置的 VM 網路設定。
- 按一下新增。
[配對 VM 網路]視窗隨即顯示。
- 選擇本地和遠端裝置的虛擬交換器。
重要
- 您在此步驟中選擇的虛擬交換器將決定哪些 VM 可以受到 HA 保護。只有連線到所選虛擬交換器的 VM 才能供選擇。
- 精靈會自動篩選出不相容的虛擬交換器。這包括未連接到實體網路配接器、保留給系統使用(例如 Docker 或 LXD)、或配置了 NAT 或 DHCP 伺服器功能的交換器。
如果列表中缺少虛擬交換器,請在網路與虛擬交換器中檢視其設定。
- 按一下新增。
Virtualization Station 將虛擬交換器新增到配對裝置。
- 按一下下一步。
[其他設定]視窗隨即顯示。 - 設定容錯移轉政策設定。
如需詳細資訊,請參見設定故障轉移政策設定。 - 按一下下一步。
- 檢視設定。
- 按一下完成。
Virtualization Station 建立 HA 裝置配對。
提示
要管理已配置的 VMHA 裝置配對,請前往高可用性>配對裝置。
- 前往動作 >編輯配對裝置以更新配置。
- 前往動作 >取消配對裝置以移除配對。
配置 HA 可用性群組或計畫
註
Beta 版本的 Virtualization Station 4.0 允許每台 NAS 建立最多兩個 HA 可用性群組,每個群組限於單一虛擬機器。
- 登入您的本地 NAS。
- 開啟Virtualization Station。
- 在建立虛擬機器旁邊,點選。

- 點擊建立可用性群組。
可用性群組視窗隨即顯示。 - 點擊開始。
建立可用性群組視窗隨即顯示。 - 選擇同步方向。

註
同步方向定義哪臺 NAS 作為來源,哪臺 NAS 接收 VM 資料作為高可用性備份。在選擇步驟中顯示的虛擬機器列表取決於所選的來源 NAS。
- 點選下一步。
- 配置 HA 群組設定。
- 指定 HA 群組名稱。
註
在本地和遠端 NAS 設備上選定的儲存空間儲存池中,會建立與 HA 保護群組同名的共用資料夾。確保每個設備上的資料夾名稱是唯一的,以防止命名衝突。
警告
不要重新命名已受保護的 VM 的資料夾,因為這可能會導致意外問題。
- 選擇來源裝置儲存空間儲存池。
- 選擇目的裝置儲存空間儲存池。
- 指定共用資料夾的分配配額。
注意
按一下使用可用的儲存池容量,以自動分配所選本地和遠端儲存空間儲存池中較小的可用容量。
- 按一下建立。
高可用性 (HA) 群組設定視窗隨即顯示。 - 驗證已配置的群組設定。
- 按一下下一步。
虛擬機器視窗隨即顯示。
- 在來源裝置(本地或遠端裝置)下,按一下列出可用專案。
- 選擇一個或多個虛擬機器以納入 VMHA 部署。
- 按一下下一步。
設定視窗隨即開啟。 - 選擇性:選擇自動恢復計畫。
此選項會在重新啟動或中斷後自動重新啟動 HA 計畫。 - 按一下下一步。
摘要視窗隨即開啟。 - 檢閱 HA 群組設定。
- 按一下建立。
Virtualization Station 建立 HA 可用性群組。
配置容錯移轉政策設定
- 開啟 Virtualization Station。
- 前往高可用性>容錯移轉政策。
- 配置監控間隔。這定義了系統檢查容錯移轉條件的頻率。
- 選擇性:在觸發事件中,選擇應觸發容錯移轉的條件。您可以配置以下設定:
- 備份電源模式:當裝置使用不斷電系統 (UPS) 運行時,啟動容錯移轉。
- PSU 冗餘損失:當備援電源供應器斷開或故障時,啟動容錯移轉。
- 系統風扇故障:當系統風扇運行不正常時,啟動容錯移轉。
- CPU 負載平均值超過閾值:當平均 CPU 使用率在設定的時間內超過定義的百分比時,啟動容錯移轉。
- 記憶體負載平均值超過閾值:當平均記憶體使用率在設定的時間內超過定義的百分比時,啟動容錯移轉。
- 磁碟健康錯誤: 當虛擬機器磁碟出現健康問題或共用資料夾卷發生錯誤時,啟動容錯移轉。
- 網路虛擬交換器錯誤: 當虛擬交換器遇到與網路相關的錯誤時,啟動容錯移轉。
- 按一下套用。
Virtualization Station 儲存並套用容錯移轉策略設定至所有 VMHA 可用性群組。
VMHA 監控、故障排除和診斷
監控和管理 VMHA 群組
您可以檢視所有 VMHA 群組的狀態,執行暫停、恢復、編輯或刪除等操作,並監控同步進度和跨 NAS 裝置的資源使用情況。
執行 VMHA 操作
建立 HA 保護群組後,您可以從高可用性 > 方案頁面監控和管理其狀態。
- 開啟 Virtualization Station。
- 前往高可用性>方案。
- 在操作,按一下。

- 識別 VMHA 群組或方案。
- 執行以下任一 VMHA 方案任務。
| 任務 | 說明 |
|---|
| 切換 | 在兩個 NAS 裝置之間切換虛擬機器,同時保持其線上和執行,無需重新啟動或暫停。 |
| 暫停 | 暫時中止 HA 群組的 VMHA 同步和容錯移轉保護。 |
| 刪除 | 移除 VMHA 群組並停用相關虛擬機器的保護。 |
| 恢復 | 重新啟動群組的 VMHA 同步和容錯移轉監控。 |
| 編輯 | 開啟 VMHA 群組設定以進行配置更改。 |
註
如果兩個 NAS 裝置上的 Virtualization Station 版本不一致,則此頁面會顯示警告橫幅。所有 HA 保護群組將自動暫停,直到版本一致性恢復。
狀態說明
| 狀態 | 說明 |
|---|
正常 | VMHA 群組執行正常,沒有問題。 |
同步中 | 源和目的地 NAS 之間正在進行初始或排程的同步。 |
暫停 | 同步暫時停止。可用性群組未積極同步,但其配置已儲存。 註 如果 Virtualization Station 停止或 NAS 關機,則可能自動發生此狀態。 |
警告 | VMHA 保護仍然有效,但一個或多個問題可能會影響容錯移轉。請立即檢查並解決根本原因。 |
錯誤 | 發生一個或多個嚴重故障。VMHA 群組不再正常執行,需要立即處理。 |
診斷和排除常見 VMHA 狀況
為確保穩定和可靠的 HA 運行,請監控系統狀況並避免可能影響容錯移轉準備的配置更改。
常見警告狀況
| 警告 | 說明 | 影響 |
|---|
| 目的地 NAS 記憶體不足 | 目標 NAS 的可用記憶體不足以在容錯移轉期間啟動受保護的 VM。 | 除非增加或釋放記憶體資源,否則容錯移轉將失敗。 |
| 可用性連結降級 | 可用性連結輸送量已降至 50 Mbps 以下或延遲超過 1 毫秒。 | 同步效能降低,復原點目標 (RPO) 增加。 |
| 裝置配對配置問題 | 配置錯誤,例如不穩定的管理連結或配對虛擬交換器之間的子網不匹配。 | 如果不加以修正,容錯移轉的可靠性可能會受到影響。 |
警告
請勿修改或刪除任何屬於 VMHA 配對的虛擬交換器。更改或移除配對的虛擬交換器將導致受保護的 VM 在容錯移轉後失去網路連接,並可能使 HA 群組進入錯誤狀態。
疑難排解 VMHA 群組問題
| 問題 | 建議 |
|---|
| Virtualization Station 版本不匹配 | 確保兩台 NAS 裝置運行相同版本的 Virtualization Station。檢查 App Center 是否有更新。如有需要,重新啟動應用程式。 |
| 來源或目標 NAS 的 CPU 或記憶體不足 | 檢查來源和目標 NAS 的系統資源使用情況。如果任一系統缺乏足夠的 CPU 或記憶體來完成過程,容錯移轉可能會失敗。關閉未使用的 VM 或服務以釋放資源。如有必要,考慮升級系統記憶體。 |
| 同步速度慢或延遲高 | 在 NAS 裝置之間使用直接網路線,或將可用性連結分配給專用的高速子網。 |
| 虛擬交換器配對錯誤 | 開啟網路與虛擬交換器並確認兩個交換器在相同的子網上,且沒有衝突的設定(例如 NAT 或 DHCP)。 |
| 叢集無法創建或加入 | 確保兩台 NAS 裝置尚未成為其他 Hero HA 或 VMHA 叢集的成員。在繼續之前,解除任何現有的叢集配對。 |
管理 VMHA 日誌
您可以查看和下載與 VMHA 相關的日誌,以協助進行故障排除、稽核或驗證系統的容錯移轉行為。這些日誌提供同步事件、狀態變更和系統警報的詳細記錄,幫助系統管理員診斷問題並維持操作可見性。
- 開啟 Virtualization Station。
- 前往高可用性>日誌。
- 執行以下任務之一。
- 搜尋日誌:在搜尋欄中輸入關鍵字,以事件型別、VM 名稱或時間戳記篩選日誌條目。
- 下載日誌:按一下儲存在動作下,將目前的 VMHA 日誌資料匯出為 CSV 檔案,以便離線分析或支援。
進一步閱讀