Applicable Products
- QuTS hero h5.3.0 or later
- High Availability Manager
Scenario
In a high-availability (HA) cluster, if data synchronization from the active node to the passive node fails, High Availability Manager may display a synchronization error on the Cluster page, and the cluster may lose fault tolerance or behave abnormally.
Solution
- Check the physical heartbeat connection.
- Verify the network cable status: Ensure the network cable used for the heartbeat connection is securely connected and not loose, damaged, or oxidized.
- Use a direct connection: Make sure the heartbeat cable directly connects the two nodes without passing through any network devices (such as switches).
- Check the passive node status.
- Verify the passive node is online: If the passive node is powered off, unresponsive, or disconnected from the network, synchronization will fail. Make sure it is powered on and properly connected to the active node.
- Check storage health: If the passive node has disk issues or a faulty storage pool, synchronization will be blocked. Go to Storage Manager to check the disk and pool status on the passive node.
- Check system load and resources.
- System resource bottlenecks: If either node experiences high CPU or memory usage, synchronization performance may be affected. Use Resource Monitor to check the system load.
- Heavy background tasks: Tasks such as snapshot creation, RAID rebuilding, or large data transfers may delay synchronization. Wait until these tasks are complete and check again.
- Review system logs for error messages.
- Open QuLog Center and review system logs related to high availability to identify the root cause of connection or synchronization issues.
- Restart the passive node.
- If the hardware and network are functioning correctly but synchronization is still stuck, try safely restarting the passive node to trigger synchronization.
If you have tried all the above steps and still cannot resolve the issue, contact QNAP Customer Service for further assistance.
Further Reading
適用產品
- QuTS hero h5.3.0 or later
- High Availability Manager
情境
在高可用性 (HA) 叢集中,如果從主節點到備援節點的資料同步失敗,High Availability Manager 可能會在叢集頁面上顯示同步錯誤,且叢集可能會失去容錯能力或異常運作。
解決方案
- 檢查實體心跳連線。
- 確認網路纜線狀態:確保用於心跳連線的網路纜線已牢固連線,且未鬆動、損壞或氧化。
- 使用直接連線:確保心跳纜線直接連線兩個節點,而不經過任何網路裝置 (例如交換器)。
- 檢查備援節點狀態。
- 確認備援節點線上:如果備援節點關機、無反應或與網路斷開連線,則同步將失敗。確保其已開機並正確連線到主節點。
- 檢查儲存空間健康狀況:如果備援節點有磁碟問題或儲存空間池故障,則同步將被阻止。前往儲存空間管理員檢查備援節點上的磁碟和池狀態。
- 檢查系統負載和資源。
- 系統資源瓶頸:如果任一節點出現高 CPU 或記憶體使用率,則同步效能可能會受到影響。使用資源監控檢查系統負載。
- 繁重的背景任務:如快照建立、RAID 重建或大量資料傳輸等任務可能會延遲同步。等待這些任務完成後再檢查。
- 檢查系統日誌以尋找錯誤訊息。
- 打開 QuLog Center 並檢查與高可用性相關的系統日誌,以識別連接或同步問題的根本原因。
- 重新啟動備援節點。
- 如果硬體和網路正常運作但同步仍然卡住,嘗試安全地重新啟動備援節點以觸發同步。
如果您已嘗試所有上述步驟但仍無法解決問題,請聯絡 QNAP 客戶服務 以獲得進一步協助。
進一步閱讀