A vSAN administrator is using the vSAN ReadyNode Sizer to build a new environment. While entering the cluster configurations, a fellow colleague inquires about the Operations Reserve option.
What is the purpose of using this option?
A vSAN administrator is using the vSAN ReadyNode Sizer to build a new environment. While entering the cluster configurations, a fellow colleague inquires about the Operations Reserve option.
What is the purpose of using this option?
The Operations Reserve option in the vSAN ReadyNode Sizer reserves space for internal operations. This includes tasks such as maintenance, background activities, and other housekeeping operations. By reserving this space, it ensures that there is enough capacity within the vSAN cluster to conduct these activities without impacting the available storage capacity for virtual machines and other data objects.
Operations Reserve The "Operations Reserve" (OR) setting accounts for the capacity needed to perform transient storage activities like storage policy changes, rebalancing, and other activities. The amount reserved will make some general assumptions about object size, and will also consider the following: Raw size of the capacity devices used in the hosts. The number of capacity devices per host. The number of disk groups per host. The use of the cluster-based Deduplication & Compression service. https://core.vmware.com/blog/understanding-reserved-capacity-concepts-vsan
A. Provides space for internal operations. The Operations Reserve is used to set aside a portion of the vSAN capacity to handle internal operations such as maintenance tasks, background activities, and other housekeeping operations. This reserved space ensures that there is enough capacity within the vSAN cluster for these activities without impacting the available storage capacity for virtual machines and other data objects.
Answer is A C is incorrect as this is host rebuild reserve (HRR)
A is the correct answer, do not confuse OR with host rebuild reservation HRR
A. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-monitoring.doc/GUID-CD510EAE-1A9F-45D2-BB66-E893C8AAF20A.html
C is correct https://core.vmware.com/blog/understanding-reserved-capacity-concepts-vsan