0 Replies Latest reply on May 12, 2020 7:49 PM by oneilv

    vSphere Replication or SRM Re-protect errors seen in vSphere 6.7 U3

    oneilv Enthusiast
    vExpert

      Versions used

      vSphere 6.7 U3e

      SRM 8.2 appliance based

      vSphere Replication appliance 8.2@

       

      Issue - Reprotect task in SRM fails with errors below:

      Recovery StepResultStep StartedStep CompletedExecution Time1. Restore protected site hosts from standbySuccess2020-05-13 01:50:26 (UTC 0)2020-05-13 01:50:26 (UTC 0)00:00:002. Configure storage to reverse directionError

                   - Unable to reverse replication for the virtual machine 'ABC'. A generic error occurred in the vSphere Replication Management Server. Exception details: 'Unexpected status code: 503'.2020-05-13 01:50:26 (UTC 0)2020-05-13 01:50:29 (UTC 0)00:00:032.1. Protection Group XYZ

                   - Unable to reverse replication for the virtual machine 'ABC'. A generic error occurred in the vSphere Replication Management Server. Exception details: 'Unexpected status code: 503'.2020-05-13 01:50:26 (UTC 0)2020-05-13 01:50:29 (UTC 0)00:00:032.1.1. Configure VR replicationError

                   - Unable to reverse replication for the virtual machine 'ABC'. A generic error occurred in the vSphere Replication Management Server. Exception details: 'Unexpected status code: 503'.2020-05-13 01:50:26 (UTC 0)2020-05-13 01:50:29 (UTC 0)00:00:032.1.1.1. XYZError

                   - Unable to reverse replication for the virtual machine 'ABC'. A generic error occurred in the vSphere Replication Management Server. Exception details: 'Unexpected status code: 503'.2020-05-13 01:50:26 (UTC 0)2020-05-13 01:50:29 (UTC 0)00:00:03

       

      Findings: The issue is seen when the vSAN health service (vmware-vsan-health) stops running at one site on the VCSA. A quick putty session to both VC and running the command control-service --status --all should show you if this service is running or in a stopped state. Then on the VC where it is in a stopped state run the command to start service-control --start -vmware-vsan-health.

      Once the service is running, check the status of the vSphere replication and re-try the Reprotect task in SRM and it should start working.

       

      Not sure if this related to the known issue with the vmware-vsan-health service on the VCSA 6.7U3e.

       

      Cheers,

       

      Onil Varghese