Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 6/25/2020Categories: TroubleshootingTotal Views: 2780Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

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.

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.

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.

Related Information

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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vRealize Automation 7.x プロビジョニングの失敗の根本原因の特定 (79611)

KB
•
Workspace ONE Email Notification Service 2 (ENS2) 1.7.1 for On Premises リリースのお知らせ (78691)

KB
•
VMware Workspace ONE Admin Assistant 2.0.1 for macOS リリースのお知らせ (78735)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Availability

Related Versions:

VMware Cloud Director Availability 4.x

Take Our Survey

Support Assistant