Failed in step 'Change Recovery Site Storage to Writeable', when you run Recovery in SRM.
Failed to recover datastore 'xxx'. VMFS volume residing on recovered device 'xxx' cannot be found. ....
Generally, you can rerun Recovery in SRM after the user responses listed below.
- Verify that every protected volume in the Remote Copy Consistency Group has at least one VM or VM link in the protection group. If one volume in the consistency group does not have a VM or VM link, SRM will not report this volume to SRA, and SRA will not be able to map it to the correct VMware hosts, which causes a failure. You can remove the volume from the consistency group or add a VM or VM link into the volume as you need.
- If SRA is running is Preconfigured Mode, you need to verify that storage-admin had already mapped all the remote copy target volumes to the VMware hosts on the recovery site. For SR 2.2.1 and earlier, you also need to verify that a Flash Copy had been established for each remote copy target volume, and all the FlashCopy target volumes had been mapped to the VMware hosts.
- If there is "cannot find .... after HBA rescan.", it probably caused by HBA rescan timeout. You can increase the storageProvider.hostRescanTimeoutSec in the SRM Advance Settings.
- If the error reproduces again after you change the storage configurations, such as start/stop/switch the remote copies or consistency groups, then you need to reset the SRA-STATUS file on both sites.
- Do NOT reset SRA-STATUS if there are any recovery plans pending for Cleanup or Reprotect
- How to reset SRA-STATUS:
- Remove SRA-STATUS file in the SRA install path on both SRM machines. The default SRA install path is C:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra\IBMSVC
- Remove all the *.d files in <SRM install path>\bin\ on both SRM machines. The default SRM install path is C:\Program Files\VMware\VMware vCenter Site Recovery Manager