After the recovery is complete, you must validate that the environment and application functionality is restored.

Procedure

  1. Verify that the vRealize Automation services are registered on both virtual appliances.
    1. Log in to the vRealize Automation Console on https://<IP of VM>:5480/ by using root credentials.
    2. Click the Services tab to verify that the vRealize Automation services have the status of Registered and the IaaS service is running.
  2. Verify that the PostreSQL replication is connected.
    1. Log in to the vRealize Automation Console on https://<IP of VM>:5480/ by using root credentials.
    2. Click the vRA Settings tab and click Database.
    3. Verify that the Connection Status is CONNECTED.
  3. Verify that RabbitMQ is registered correctly on all virtual appliances.
    1. Click vRealize Automation Settings > Messaging tab.
    2. Verify that all virtual appliances have a Running status of Yes.
    3. Verify that the Connection Status is CONNECTED.

    If RabbitMQ fails to register correctly, see KB 2106969 to reset RabbitMQ.

  4. Verify virtual appliance and IaaS service last connected status.
    1. Click the vRA Settings tab.
    2. Verify that each virtual appliance node has a Last Connected time of 30 seconds or less.
    3. Verify that each IaaS node has a Last Connected time of three minutes or less.
  5. Verify that there are no errors displayed in Event Viewer > Administrative Events.
  6. Verify that the Web IaaS service is initialized.
    1. In your browser, navigate to https://localhost/wapi/api/status .
    2. Verify that the displayed file contains the string "serviceIntitializationStatus":"REGISTERED".
  7. Verify that the Model Manager Web log repository contains no exceptions.
    1. Navigate to C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Web\Logs\Repository.
    2. Verify that the file contains no exceptions.
    3. Verify that the file contains the following strings:
      Model TrackingModel service has been initialized.
      Model MetaModel service has been initialized.
      Model CoreModel service has been initialized.
  8. Verify that the VMware vCloud Automation Center service is running.
  9. Verify that the manager service log contains no errors.
    1. Navigate to C:\Program Files (x86)\VMware\vCAC\Server\Logs\All.log.
    2. Verify that there are no exception errors after the string Manager service started for processed workflows.
  10. In your browser, navigate to https://localhost/VMPS2Proxy, and verify that it contains an XML file similar to the following:
    - <wsdl:service name="ProxyAgentService">
       - <wsdl:port name="BasicHttpBinding_VMPSProxyAgent" binding="tns:BasicHttpBinding_VMPSProxyAgent">
          <soap:address location="https://us06-2-ims1.vmware.com/VMPS2proxy"/>
  11. Verify that the DEM Orchestrator services are running.
  12. Navigate to C:\Program Files (x86)\VMware\vCAC\Distributed Execution Manager\DEMOName-hostname DEO\Logs\hostname DEO_All.log, and verify all processed and scheduled workflows.
  13. Verify that the DEM Worker services are running.
  14. Navigate to C:\Program Files (x86)\VMware\vCAC\Distributed Execution Manager\DEMName\Logs\DEMNAME_All.log, and verify all executed workflows.
  15. Verify that the Proxy Agent services are running.
  16. Navigate to C:\Program Files (x86)\VMware\vCAC\Agents\AgentName\logs\vSphereAgent.log, and verify that the agent can successfully connect to the manager service and that it is attempting to connect to the endpoint.
  17. Verify that you can log in to all tenants with external directory credentials if available or vsphere.local credentials.
  18. In the vRealize Automation Console, verify that the Infrastructure tab loads successfully.
  19. In the vRealize Automation Console, click the Monitoring tab and verify that the DEM services have a green status.
  20. If you are validating vRealize Automation version 7.2, click the Containers tab in the vRealize Automation Console, and verify that the tab load successfully and displays all connected servers.