SharePoint 2013搜索服务拓扑更改 [英] SharePoint 2013 Search service topology change

问题描述

您好，

我们支持SharePoint 2013 onpremises 托管文档内容管理的VM服务器。

我们有两个专用搜索服务器（Server1，Server2），索引项目为15百万，索引数据随着内容数据库中内容的增加而增长

Server1托管主索引组件，server2管理索引副本只有一个索引分区及以下是搜索拓扑。

两台服务器的磁盘空间不足，由于VM管理容量限制，我们的infra团队无法提供额外空间。 

我们的计划是从SP服务器场中删除server2，以便搜索索引副本不可用，并将服务器2磁盘空间用于server1（通过infra管理）。

我们在降低搜索服务对企业的高可用性方面做出妥协。 

是否建议修改此方法搜索拓扑到只有server1和decommission server2？

解决方案

嗨AK SPAdmin。

I建议您创建一个新索引，将索引拆分为2个分区：您将节省磁盘空间并保持高可用性。

这个选项可行吗？

再见。

Hi there,

We are supporting SharePoint 2013 onpremises  VM servers hosted for document content management.

We have two dedicated search servers (Server1, Server2) with indexing items 15 Million and indexing data growing with increasing content in content database

Server1 is hosting primary index component and server2 is managing index replica with only one index partition and below is search topology.

Both servers are running out of disk space and our infra team is unable to provide the additional space due to VM administration capacity limits. 

Our plan is to remove server2 from the SP farm so that search index replica will not be available and use the server 2 disk space for server1 (through infra management) .

We compromise with the reducing the high availability of search service to business. 

Is  this approach recommended with modifying the search topology to only server1 and decommission server2?

解决方案

Hi AK SPAdmin.

I'd rather suggest you to create a new topology having the index split in 2 partitions: you'll save disk space and preserve high availability.
Is this option feasible?

Bye.

这篇关于SharePoint 2013搜索服务拓扑更改的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！