VMware Cloud Director Availability 4.x.
A cleanup of the Ongoing Replications followed by un-pairing a remote site is needed before proceeding with the removal or replacement of VMware Cloud Director Availability Instances from the Cloud Site. Else, it leads to the error message - "VM already protected" after installing a NEW VMware Cloud Director Availability Instances backed by Cloud Director.
To proceed with the removal / replacement of VMware Cloud Director Availability Instance from Cloud Site:
Step1: Stop all replications from and to the VMware Cloud Director Availability instance you are removing.
Step2: Delete the established trust with all peer sites.
Step3: Delete the established trust with all on-premises sites from the cloud site.
Note:
Step4: Remove the VMware Cloud Director Availability plug-in from VMware Cloud Director.
Step5: If the management interface of VMware Cloud Director Availability is not available, remove the VMware Cloud Director Availability plug-in from VMware Cloud Director by using its Service Provider Admin Portal.
Step6: For the VMware Cloud Director Availability instance you are removing, delete all the virtual machines of its appliances from the vCenter Server instance.
This VMware Cloud Director Availability instance is now uninstalled from the cloud site backed by VMware Cloud Director.
For more details on the VMware Cloud Director Availability product documentation, see: https://techdocs.broadcom.com/us/en/vmware-cis/cloud-director/availability/4-7/what-is-vcda.html