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 客户服务 以获取进一步帮助。
进一步阅读
