使用 VMware SRM 的 RecoverPoint:容錯移轉作業在「建立可寫入儲存」步驟失敗

Summary: 在「建立可寫入的儲存裝置」步驟中一段時間後,VMware Site Recovery Manager(SRM) 容錯移轉或測試容錯移轉作業會失敗: 錯誤 - 無法建立複本裝置的快照。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 分鐘),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ță.