Hi @jpillai , two main things: 4/8 CPUs are very few for Indexers that should have at least 12 CPUs each one (if you don't have ES or ITSI). You should analyze your requirements, with special atte...
See more...
Hi @jpillai , two main things: 4/8 CPUs are very few for Indexers that should have at least 12 CPUs each one (if you don't have ES or ITSI). You should analyze your requirements, with special attention to especially input next growth and the number of scheduled searches and concurrent users, because usually it's used one IDX every 200 GB indexed (less if you have ES or ITSI), so you have too many IDXs. In addition you should analyze the performances of your disks (storage and system disks) to find the correct number of IDXs, because you need at least 800 IOPS better if more! About configurations, SHs usually require more CPUs than IDXs, So I'd use (if you don't have ES or ITSI): SH and IDX: 24/48 CPUs 64 GB RAM, HF, CM, SHC-D, MC and DS: 12/24 CPUs 64 GB RAM. About the secondary site, as also @dural_yyz said, the secondary site, in the normal activity) is mainly used for the data replication, but you should analyze also the worst case, so I'd use the same configuration of the main site. Then, the Cluster Manager isn't required so performant and it must be only one in the cluster. In other words, you can have only one CM because the cluster continue to run also if the CM is down, eventually having a silent copy to turn on if the Primary Site down is longer that predicted. At least, I don't see in your infrastructure SHC-Deployer, Monitoring Console and Deployment Server for which you can apply the same considerations of the Cluster Manager. Ciao. Giuseppe