FAQ: vSAN Data Protection Pairing Behavior in Mixed DR Environments
Article ID: 434214
Updated On:
Products
Issue/Introduction
vSAN Data Protection (DP) Integration with Existing SRM/VR – Workflow and Pairing Clarifications
Environment
VMware Live Recovery Appliance 9.0.5
Cause
vSAN Data Protection pairing issues with the existing SRM/VR pairing.
Resolution
Q: If SRM/VR site pairing already exists, is it required to break the pairing before enabling vSAN DP?
A: No, it is not required to break the existing SRM/VR pairing.
Q: Is there a supported in-place workflow to extend existing pairing to vSAN DP?
A: Yes. Existing SRM/VR pairing can be reused and extended for vSAN DP, provided that:
The same DPVA instances are used.
Pairing is performed via the vSAN DP UI, which integrates the services.
Additional Technical Note:
DPVA < 9.1:
vSAN DP UI → Uses APS service
SRM/VR UI → Does not use APS
DPVA ≥ 9.1:
Both vSAN DP UI and DR UI use the APS service, making workflows equivalent
Q: In a mixed environment (SRM/VR + vSAN DP), which component owns site pairing?
A:
There is no strict single owner, but behavior depends on DPVA version:
DPVA < 9.1: vSAN DP UI is the preferred authoritative interface
DPVA ≥ 9.1: Both DR UI and vSAN DP UI are equivalent
Q: Should all pairings be initiated from vSAN DP UI?
A:
Recommended (especially DPVA < 9.1): Yes
DPVA ≥ 9.1: Either UI (DR or vSAN DP) is supported
Q: What is the correct order for vSAN DP configuration?
A: The supported and required sequence is:
Step 1: Site Pairing (via vSAN DP UI)
Step 2: Cluster Pairing
Q: Is this sequence mandatory?
A: Yes, this sequence is mandatory for proper vSAN DP setup.
Q: Should site pairing always be performed from the vSAN DP UI?
A:
DPVA < 9.1:
vSAN DP UI is strongly preferred
If pairing was done via DR UI, re-pairing in vSAN DP UI is supported and will succeed
DPVA ≥ 9.1:
Either DR UI or vSAN DP UI can be used
Q: Can SRM/VR pairing from DR UI be reused in vSAN DP?
A: Yes, it is supported.
Re-running pairing in vSAN DP UI will invoke APS service and align configurations
This process can effectively repair or normalize existing SRM/VR pairing
Q: Is failure like “LS certificate cannot be null” expected when pairing vSAN DP over existing SRM/VR?
A: No, this is not expected behavior.
Q: What is the likely cause?
A:
Common cause: Pairing was not performed using
[email protected]
Q: What should be done?
A:
Retry pairing using the correct administrative account
Ensure proper certificate handling during pairing workflow
Key Takeaways
Existing SRM/VR pairing does not need to be removed
vSAN DP pairing can extend existing configurations
Site pairing must be done before cluster pairing
vSAN DP UI is preferred, especially for DPVA < 9.1
Errors like certificate issues are configuration-related, not design limitations
Additional Information
Feedback
