Planned Migration cannot auto mount datastore without running Test

[NelsonIft]

Hi folks,

We have been performing successful SRM tests for a while using vSphere 6.0 and SRM 6.0 and using Array based replication.

After the Disater Recovery completed, we want to role Protected Site back to site A by running a Planned Migration, but our datastore cannot auto mount in Recovery step without running Test first.

Is the "Test failover" must before Recovery every time?

Error message in html report:

Error - Failed to recover datastore 'snap-08afa473-N1'. Cannot mount recovered VMFS volume 'N1' on any host. Recovered VMFS volume 'N1' is not visible or not mounted on host '172.22.111.140'. Cannot mount VMFS volume '59032081-f069f320-2f81-d05099c0566a' on host '172.22.111.140'. An error occurred during host configuration.

The attachment is the vmware-dr.log in site A, line 21354SRM get new devices, but line 21921 got error.

Checking if anyone has any suggestions?

[admin]

A Test Failover should not be required here. After a Disaster Recovery from A to B if any errors were encountered then you must run a Planned Migration from A to B again and fix any problems. If this step is not performed then Reprotect will not be available in order to perform a fail back from B to A.

Is that where you are encountering the error? i.e. Planned Migration from A to B? I don't think Test Failover option should even be available if you have just performed a DR...

[NelsonIft]

Hi p_hall,

We have completed the Disaster Recovery, and its Reprotect, so the protected site is role switch to site B.

Then we want to role switch back to site A, the error occur when run Planed Migration - Recovery.  Recovery show the red error message, and datastore auto mount failed.  In that time we can deattach then attach the datastore manually.

If run Test first then run Recovery, Recovery result will be fine.

Thanks for your help!

[admin]

I would guess it's just a timing thing. Maybe just increasing the number of host rescans (hostRescanRepeatCnt ) or adding a rescan delay value (hostRescanDelaySec) might achieve the same thing.

Site Recovery Manager 6.1 Documentation Center

I'm not sure why adding a Test Failover step helps though 😕

[NelsonIft]

We have modified hostRescanRepeatCnt to 2 before, now I will try to modify value for more times.