当出现一些意外故障时,vSphere Replication 会在日志中加入一条一般错误消息。

某些意外 vSphere Replication 故障会导致显示以下错误消息:VRM Server 一般错误。请查看文档了解任何故障排除信息 (VRM Server generic error. Please check the documentation for any troubleshooting information)

除了一般错误以外,该消息提供有关该问题的更多详细信息,类似于以下示例。

  • VRM Server 一般错误。请查看文档了解任何故障排除信息。详细的异常为:“org.apache.http.conn.HttpHostConnectException:连接到 https://vCenter_Server_address 被拒绝”(VRM Server generic error. Please check the documentation for any troubleshooting information. The detailed exception is: org.apache.http.conn.HttpHostConnectException: Connection to https://vCenter_Server_address refused)。此错误涉及连接 vCenter Server 的问题。

  • 错误 - VRM 组 virtual machine name 的 VR 同步失败。同步监控已中止。请验证源主机和目标 VR 服务器之间的复制通信连接。连接问题解决后,将自动恢复同步 (Error - VR synchronization failed for VRM group virtual machine name. Sync monitoring aborted. Please verify replication traffic connectivity between source host and target VR server. Sync will automatically resume when connectivity issues are resolved)。此问题涉及同步操作错误。

  • 错误 - 无法撤消复制虚拟机“virtual machine name”。VRM Server 一般错误。请查看文档了解任何故障排除信息。详细的异常为:“org.hibernate.exception.LockAcquisitionException:Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.请重新运行事务”(Error - Unable to reverse replication for the virtual machine 'virtual machine name'. VRM Server generic error. Please check the documentation for any troubleshooting information. The detailed exception is: 'org.hibernate.exception.LockAcquisitionException: Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction)。此问题涉及 Microsoft SQL Server 中的死锁。

vSphere Replication 遇到配置错误或基础架构错误时,会发送此消息。例如,网络问题、数据库连接问题或主机过载。

结果

有关该问题的信息,请检查详细的异常消息。根据消息的详细信息,可以尝试或重试失败的操作,重新启动 vSphere Replication,或更正基础架构。