RecoverPoint 与 VMware SRM:故障切换作在“Create writable storage”步骤失败

Summary: VMware Site Recovery Manager (SRM) 故障切换或测试故障切换作在“Create writable storage”步骤一段时间后失败: 错误 — 无法创建副本设备的快照。SRA 命令“testFailoverStart”失败。未能打开用户到站点管理 IP 的会话。

Acest articol se aplică pentru Acest articol nu se aplică pentru Acest articol nu este legat de un produs specific. Acest articol nu acoperă toate versiunile de produs existente.

Symptoms

由于 Site Recovery Manager (SRM) 测试失败,用户将 SRM 超时时间增加到 31 分钟以上,并且映像访问启用作所需的时间超过超时设置的时间。

SRM 测试故障切换或故障切换作可能会在步骤 4 失败:在此步骤经过一段时间(默认为 31 分钟)后,执行“Create writable storage snapshot”,SRM 恢复计划步骤中出现错误:

Error - Failed to create snapshots of replica devices. SRA command 'testFailoverStart' failed. Failed opening session for user to site mgmt IP.

来自 SRM 日志的错误 (C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs):

--> Feb 20, 2019 3:12:52 PM com.emc.santorini.log.KLogger log
--> INFO: Starting to run: TestFailoverStart command
--> Feb 20, 2019 3:43:53 PM com.emc.santorini.log.KLogger logWithException
--> WARNING: Caught SocketTimeoutException. Please check your network connection to the RPAs.
--> javax.xml.ws.WebServiceException: java.net.SocketTimeoutException: Read timed out
-->     at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.readResponseCodeAndMessage(Unknown Source)
-->     at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.createResponsePacket(Unknown Source)
-->     at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(Unknown Source)
-->     at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(Unknown Source)
-->     at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(Unknown Source)
-->     at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Unknown Source)
-->     at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Unknown Source)
-->     at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Unknown Source)
-->     at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Unknown Source)
-->     at com.sun.xml.internal.ws.client.Stub.process(Unknown Source)
-->     at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(Unknown Source)
-->     at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
-->     at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
-->     at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown Source)
-->     at com.sun.proxy.$Proxy36.testFailoverStartWithOpaques(Unknown Source)
-->     at com.emc.santorini.handlers.SantoriniLogic.testFailoverStart(SantoriniLogic.java:278)
-->     at com.emc.santorini.commands.TestFailoverStartCommand.execute(TestFailoverStartCommand.java:40)
-->     at com.emc.santorini.handlers.SantoriniCommandDispatcher.handleCommandAction(SantoriniCommandDispatcher.java:105)
-->     at com.emc.santorini.main.SantoriniMain.main(SantoriniMain.java:57)
--> Caused by: java.net.SocketTimeoutException: Read timed out
...

RecoverPoint 端无错误

 

Cause

默认 SRM 超时设置为 5 分钟,并且可以增加,当增加到 31 分钟以上时,可能会发生不同的超时 — 如果映像访问过程花费的时间超过 1860 秒(31 分钟),则可能会发生 SRA 超时WEB_SERVICE_REQUEST_TIMEOUT默认设置为 1860 秒。

 

Resolution

分辨率:
更改 SRA 超时以匹配 SRM 中请求的超时更改。
SRA 超时在 SRM 服务器上的以下位置设置: C:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra\array-type-recoverpoint\conf\cancun_run.properties file
应在两台 SRM 服务器上进行更改。

更改以下属性以匹配 SRM 超时(以秒为单位设置),在此示例中,它设置为 1 小时 - 3600 秒:

VERIFY_PAUSED_TSP_TIMEOUT=3600
VERIFY_REPLICATING_TIMEOUT=3600
VERIFY_TRANSFER_SNAP_SHIPPING_IDLE_TIMEOUT=3600

WEB_SERVICE_REQUEST_TIMEOUT=3600
提醒:进行此更改后,无需重新启动服务,下一次 SRM作将使用新设置。

Produse afectate

RecoverPoint

Produse

RecoverPoint, RecoverPoint CL, RecoverPoint EX, RecoverPoint SE
Proprietăți articol
Article Number: 000053724
Article Type: Solution
Ultima modificare: 21 Nov 2025
Version:  6
Găsiți răspunsuri la întrebările dvs. de la alți utilizatori Dell
Servicii de asistență
Verificați dacă dispozitivul dvs. este acoperit de serviciile de asistență.