Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Updating vSAN Storage Policy FTT Level for Horizon on VMware Cloud on AWS (76366)

Last Updated: 10/25/2023Categories: TroubleshootingTotal Views: 9986Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When running Horizon on VMware Cloud on AWS, in order to conform to the terms of the Service Level Agreement of VMware Cloud on AWS and be eligible for SLA credits, you must ensure the right storage policy with FTT (Failures To Tolerate) level is set.

You must have a minimum configuration for all VM storage policy Numbers of Failures To Tolerate (FTT) = 1 when the cluster has 3, 4 or 5 hosts, and a minimum configuration of FTT = 2 when the cluster has 6 to 16 hosts.

By default, Horizon creates a set of vSAN storage policies (as they appear in vCenter Server):

FULL_CLONE_DISK_<guid>

FULL_CLONE_DISK_FLOATING_<guid>

OS_DISK_FLOATING_<guid>

REPLICA_DISK_<guid>

VM_HOME_<guid>

These policies are created when first needed based on the pool type created, and are applied to the relevant Horizon objects during pool creation. Values of the policies above are documented here . With the exception of FULL_CLONE_DISK_FLOATING, the current value of FTT for the other Horizon storage policies is 1.

Resolution

To resolve this issue:

Once your cluster size reaches 6 hosts or more, update all of the Horizon storage policies above with FTT = 2:

To update, go to vCenter Server and navigate to VM Storage Policies.

Select the one of the Horizon policies listed above.

Click Edit Settings to open up the policy edit wizard.

In step 3: vSAN screen, you have 2 options:

If you are not storage constrained, then select 2 failures – RAID 1 (Mirroring). This creates an extra copy of all your data and increase your current storage consumption by 50%.

If you are storage constrained, then select 2 failures – RAID 6 (Erasure Coding). This increases your existing CPU consumption by 15% or more but not increase your storage consumption.

Repeat steps above until you have updated all Horizon policies.

Related Information

Default Storage Policy Profiles for vSAN Datastores

Page last reviewed: October 2023
Next review due: December 2023

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
Downloading and Installing the standalone VMware Remote Console (VMRC) in vSphere (2091284)

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 Horizon

VMware Cloud on AWS

Related Versions:

VMware Horizon 8

VMware Horizon 7

Take Our Survey

Support Assistant