Data Protection Health Service - Replication - Site pair connectivity

Products

• VMware Cloud Foundation
• VMware Live Recovery

Issue/Introduction

This article introduces the new Data Protection Health check 'Replication - Site pair connectivity' in vSAN and provides details on why it might report the error and how to fix the error state

Environment

• VMware Cloud Foundation 9.1
• VMware Live Recovery 9.1

Resolution

Q: What does the 'Replication - Site pair connectivity' check do? 

• This check verifies the network connectivity between all VMware vCenter instances currently configured for replication.
• It ensures that the source and destination sites can communicate effectively to maintain data protection standards.

Q: What does it mean when it is in an error state?

• An error state indicates that communication has been lost with the remote vCenter Server.
•  If this issue is not resolved, the immediate risks include:  

1. 1. Loss of Data Protection: Snapshots may be missed, leading to gaps in data recovery points.  
   2. Compliance Failure: Both incoming and outgoing protection groups will become non-compliant with their defined snapshot policies.

Q: How does one troubleshoot and fix the error state?

• To resolve the communication loss, follow the diagnostic steps below in order:

1. 1. Verify Appliance Status:  Confirm that the Protection and Recovery appliance is currently running and accessible via the network.
   2. Test Network Connectivity:

1. 1. 1. Log in to the Protection and Recovery appliance VM directly.
      2. Use standard network utility tools (such as ping or traceroute) to verify that the appliance can reach the remote vCenter server.

              3. Check Firewall Rules:

1. 1. 1. Ensure that the remote vCenter Server's firewall is not blocking the Protection and Recovery appliance. Specifically, check that the appliance has access to the remote Server management interface URL:https://remote-vcenter-server-host:5480
      2. Check Data Protection Service Health: Ensure all necessary daemon is running OR check Failure Reason for the root cause: