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.
- Ensure that the VM has successfully failed over from Site-A to Site-B.
- Delete the replication from the Cloud Director Availability Portal.
- 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.
- When configuring the settings for the new replication, select the appropriate SLA profile for Site-A.