{"id":570,"date":"2020-11-15T18:47:01","date_gmt":"2020-11-15T17:47:01","guid":{"rendered":"http:\/\/thomas-kopton.de\/vblog\/?p=570"},"modified":"2020-11-15T18:47:01","modified_gmt":"2020-11-15T17:47:01","slug":"capacity-management-for-n1-and-n2-clusters-using-vrealize-operations","status":"publish","type":"post","link":"https:\/\/thomas-kopton.de\/vblog\/?p=570","title":{"rendered":"Capacity Management for n+1 and n*2 Clusters using vRealize Operations"},"content":{"rendered":"\n

When it comes to capacity management in vSphere environments using vRealize Operations<\/span><\/strong> customers are frequently asking for guidelines how to setup vROps to properly manage n+1<\/span><\/strong> and n*2<\/span> <\/strong>ESXi clusters.<\/p>\n\n\n\n

Just as a short reminder, n+1 in context of a ESXi cluster means that we are tolerating (and are hopefully prepared for) the failure of exactly one host. If we need to cope with the failure of 50% of all hosts in a cluster, like two fault domains, we often use the n*2 term.<\/p>\n\n\n\n

In general we have two options to make vRealize Operations aware of the failure strategy for the ESXi clusters:<\/p>\n\n\n\n