"Replication with custom SLA settings can not be configured..." error when reversing a replication in Cloud Director Availability 4.0

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• Reversing a replication that was created using an SLA profile fails, and you see a similar error:

Replication with custom SLA settings can not be configured because it violates policy "Gold Policy" configured at site "Site-A".

• This issue occurs if you are using SLA profiles and have disallowed the use of custom SLA settings.

Environment

VMware Cloud Director Availability 4.x

Cause

This issue occurs because SLA profiles are site specific and when you reverse a replication there is no SLA profile in the other site that matches the one the replication was created with. When the reverse replication is created, it uses the SLA settings from the original replication as the custom SLA settings.

Resolution

This is an expected behaviour in Cloud Director Availability 4.0.

To reverse a replication, the replication policy in the original source site must be set to allow custom SLA settings.

Workaround:
If you are unable to change the replication policy to allow custom SLA settings, you can work around this behaviour by deleting the replication and configuring a new replication using the failed over VM as one you wish to protect.

1. Ensure that the VM has successfully failed over from Site-A to Site-B.
2. Delete the replication from the Cloud Director Availability Portal.
3. Configure a new replication from Site-B to Site-A using the failed over VM as the new source.

Note: If the original VM still exists in Site-A you can use this as a seed for the new replication.

4. When configuring the settings for the new replication, select the appropriate SLA profile for Site-A.

Additional Information

For more information on replication management, see the Using Replications section of the VMware Cloud Director Availability documentation.