在 SharePoint 2016 中重新設計其他內容和使用者的企業搜尋拓撲Redesign enterprise search topology for more content and users in SharePoint 2016

摘要:了解如何重新設計企業搜尋架構內容成長、 成長的使用者數量,或兩者的拓撲。Summary: Learn how to redesign the topology of your enterprise search architecture for growth in content, growth in number of users, or both.

經過一段時間之後,大部分搜尋環境的內容量和使用者數目都會成長。在某個時間點,搜尋環境會無法符合您搜尋架構的容量和效能。解決方案是擴充搜尋架構的拓撲:Over time most search environments grow, both in amount of content and number of users. At some point the search environment outgrows the capacity and performance of your search architecture. The solution is to scale the topology of your search architecture:

  1. 重新設計拓撲 (本文)Redesign your topology (this article)

  2. 實作重新設計的拓撲 (在 SharePoint Server 中管理搜尋拓撲)Implement the redesigned topology (Manage the search topology in SharePoint Server)

所熟悉的 SharePoint Server 與互動的方式中的搜尋系統的元件閱讀Overview of SharePoint Server 中的搜尋架構SharePoint Server 2016 的搜尋架構(或SharePoint Server 2013 搜尋架構) 取得升級之前,您將熟悉搜尋架構、 搜尋元件、 搜尋資料庫和搜尋拓撲。Are you familiar with the components of the search system in SharePoint Server, and how they interact? By reading Overview of search architecture in SharePoint Server and Search architectures for SharePoint Server 2016 (or Search architectures for SharePoint Server 2013) before you get going, you'll become familiar with search architecture, search components, search databases, and the search topology.

在本文中,我們將顯示逐步說明如何重新設計搜尋拓撲。In this article, we'll show you step-by-step how to redesign your search topology.

遵循這些步驟之後,您會知道:After you've followed these steps you'll know:

  • 您拓撲所需之每種類型的搜尋元件和搜尋資料庫數目。How many of each type of search component and search database your topology needs.

  • 在其上部署每個搜尋元件的應用程式伺服器和資料庫伺服器。Which application servers and database servers to deploy each search component on.

  • 每部應用程式伺服器和資料庫伺服器所需的硬體資源。What hardware resources each application server and database server needs.

步驟 1:我有多少內容?Step 1: How much content do I have?

您必須在搜尋索引的內容數量會影響為何您以架設在伺服器陣列所需的資源。檢查現有的搜尋環境中可搜尋的項目數。您可以在 [搜尋管理] 頁面上找到此號碼在 SharePoint 管理中心網站。若要開啟 [搜尋管理] 頁面上按一下 [管理服務應用程式在管理中心,然後按一下 [Search service 應用程式的名稱。The volume of content that you have in your search index affects what resources you need to host the farm. Check how many items that are searchable in your existing search environment. You find this number on the Search administration page in the SharePoint Central Administration website. To open the search administration page click Manage service applications in Central Administration and then click the name of the Search service application.

評估預期在接下來的 12 個月會成長的可搜尋項目數,以及設計該數量的搜尋拓撲。例如,如果您有 8,000,000 個索引項目,而且預期該內容的數量會在接下來的 12 個月成長 50%。您應該針對 12,000,000 個可搜尋項目進行設計。Estimate how much you expect the number of searchable items to grow over the next 12 months and design the search topology for that amount. For example, if you have 8,000,000 indexed items, and you expect the volume of that content to grow 50% over the next 12 months. You should design for 12,000,000 searchable items.

步驟 2:應該擴充為的大小搜尋架構為何?Step 2: What size search architecture should I scale to?

它不一定容易評估方式大或小,讓您的搜尋架構。搜尋架構的大小取決於您的內容、 編目率、 的查詢輸出量及您需要的高可用性的層級的量。有我們建議您自己的伺服器陣列使用做為基礎的 microsoft 測試的範例搜尋架構。比較您目前的搜尋架構與範例搜尋架構並決定最佳的範例代表您目前的搜尋架構。然後考慮可適應哪些範例搜尋架構。您選擇範例搜尋架構取決於有多少內容可供搜尋:It's not always easy to assess how big or small to make your search architecture. The size of your search architecture depends on the volume of your content, the crawl rate, the query throughput, and the level of high availability that you require. There are sample search architectures that were tested by Microsoft that we advise using as a basis for your own farm. Compare your current search architecture with the sample search architectures and determine which sample best represents your current search architecture. Then consider which sample search architecture to scale to. The sample search architecture that you choose depends on how much content has to be searchable:

磁碟區的內容 (SharePoint 2016)Volume of content (SharePoint 2016) 範例搜尋架構Sample search architecture 磁碟區的內容 (SharePoint 2013)Volume of content (SharePoint 2013)
0 至 2,000 萬個項目0-20 million items 小型搜尋伺服器陣列Small search farm 0 至 1,000 萬個項目0-10 million items
0 至 8,000 萬個項目0-80 million items 中型搜尋伺服器陣列Medium search farm 0 至 4,000 萬個項目0-40 million items
0 至 2 億個項目0-200 million items 大型搜尋伺服器陣列Large search farm 0 至 1 億個項目0-100 million items
0 至 5 億個項目0-500 million items 特大型搜尋伺服器陣列Extra large search farm 不支援Not supported

雖然這些範例搜尋架構使用虛擬機器,您可以使用實體伺服器與虛擬機器根據您的搜尋架構整體 SharePoint Server solution 策略。Although these sample search architectures use virtual machines, you can use both physical servers and virtual machines according to the strategy of the overall SharePoint Server solution of your search architecture.

小型搜尋伺服器陣列Small search farm

我們已估計此搜尋架構可編目 50 每秒文件,並以每秒 10 個查詢順序做。如果您在 SharePoint Server 2016 伺服器陣列中有最多 20 個萬個項目,小型搜尋伺服器陣列可能會讓您最合適的伺服器陣列。每秒 50 文件的編目率、 延長搜尋 110 小時中第一次的完整編目的編目 20 萬個項目。We've estimated that this search architecture can crawl 50 documents per second, and serve in the order of 10 queries per second. If you have up to 20 million items in a SharePoint Server 2016 farm, the small search farm will probably be the most suitable farm for you. With a crawl rate of 50 documents per second, it takes search 110 hours to crawl 20 million items in the first full crawl.

小型企業搜尋架構範例中伺服器和搜尋元件的圖表

中型搜尋伺服器陣列Medium search farm

我們已估計此搜尋架構可編目 100 每秒文件,並以每秒 10 個查詢順序做。如果您在 SharePoint Server 2016 伺服器陣列中的 20%和 80 萬個項目之間,中型搜尋伺服器陣列可能會讓您最合適的伺服器陣列。每秒 200 文件的編目率、 延長搜尋 280 小時中第一次的完整編目的編目 80 萬個項目。We've estimated that this search architecture can crawl 100 documents per second, and serve in the order of 10 queries per second. If you have between 20 and 80 million items in a SharePoint Server 2016 farm, the medium search farm will probably be the most suitable farm for you. With a crawl rate of 200 documents per second, it takes search 280 hours to crawl 80 million items in the first full crawl.

中型企業搜尋架構範例中伺服器和搜尋元件的圖表

大型搜尋伺服器陣列Large search farm

我們已估計此搜尋架構可編目 200 每秒文件,並以每秒 10 個查詢順序做。如果您在 SharePoint Server 2016 伺服器陣列中 80 和 200 萬個項目之間,大型搜尋伺服器陣列可能會讓您最合適的伺服器陣列。每秒 200 文件的編目率、 延長搜尋 280 小時中第一次的完整編目的編目 200 萬個項目。We've estimated that this search architecture can crawl 200 documents per second, and serve in the order of 10 queries per second. If you have between 80 and 200 million items in a SharePoint Server 2016 farm, the large search farm will probably be the most suitable farm for you. With a crawl rate of 200 documents per second, it takes search 280 hours to crawl 200 million items in the first full crawl.

在大型企業搜尋架構範例中伺服器和搜尋元件的圖表

特大型搜尋伺服器陣列Extra-large search farm

Microsoft 測試此搜尋架構與可以編目 300-500 位每秒文件,並以每秒 10 個查詢順序做為單位。SharePoint Server 2016 支援此大小搜尋架構。如果您有最多 500 萬個項目,類似於非常大的搜尋伺服器陣列的伺服器陣列會是很好的起點。每秒的文件 500 編目率、 延長搜尋大約 300 小時中第一次的完整編目的編目 500 萬個項目。Microsoft tested this search architecture and measured that it can crawl 300-500 documents per second, and serve in the order of 10 queries per second. Only SharePoint Server 2016 supports this size search architecture. If you have up to 500 million items, a farm similar to the extra large search farm is a good starting point. With a crawl rate of 500 documents per second, it takes search about 300 hours to crawl 500 million items in the first full crawl.

建立此大小的搜尋伺服器陣列需要謹慎規劃及調整伺服器陣列,以取得您想要的效能。您可能會發現有用 seek 專家指導。它也務必規劃如何備份及還原的這個大小、 搜尋伺服器陣列及如何如果您的資料中心有主要中斷復原伺服器陣列。我們建議您練習備份、 還原及復原。Creating a search farm of this size requires you to carefully plan and tune the farm to get the performance you want. You might find it advantageous to seek expert guidance. It's also important to plan how to back up and restore a search farm of this size, and how to recover the farm if your data center has a major outage. We recommend that you practice backup, restore and recovery.

在超大型企業搜尋範例中伺服器和搜尋元件的圖表。

步驟 3:我應該要知道哪些硬體需求?Step 3: Which hardware requirements should I be aware of?

既然您已經決定內容數量並選擇將移至新的拓撲下, 一步是規劃硬體您需要,如本節所述:Now that you've determined the volume of your content and chosen a new topology to move to, the next step is to plan the hardware you'll need, as described in this section:

選擇以實體或虛擬的方式執行伺服器Choose to run the servers physically or virtually

當您原本規劃您的搜尋架構時,您決定要使用實體伺服器或虛擬機器或混合。請考慮是否該決策仍會有效。例如,如果您移動從 medium 降低大型範例搜尋架構時,您可能會發現,更輕鬆地管理伺服器數目增加時使用虛擬機器。請注意且更輕鬆地管理虛擬環境,雖然其效能層級有時可稍微低於之實體的環境。實體伺服器可裝載多個搜尋元件的同一部伺服器與虛擬伺服器。您可在伺服器陣列虛擬化及 SharePoint 2013 的架構概觀找到實用的指導。When you originally planned your search architecture, you decided to use physical servers or virtual machines, or a mix. Consider whether that decision still is valid. For example, if you move from the medium to the large sample search architecture, you might find it easier to manage the increased number of servers when you use virtual machines. Note also that although a virtual environment is easier to manage, its performance level can sometimes be slightly lower than that of a physical environment. A physical server can host more search components on the same server than a virtual server. You'll find useful guidance in Overview of farm virtualization and architectures for SharePoint 2013.

小型、 中型、 大型或非常大的搜尋架構範例 (英文) 虛擬機器上執行,但也可以在實體伺服器上執行。範例伺服器陣列架構、 中只從虛擬機器移動搜尋元件的主機伺服器,並採取離開虛擬機器。每個實體伺服器可主控最多四個索引元件,但僅有一個搜尋元件的每個類型。如果您例如變更使用實體伺服器的中型範例搜尋架構時,您可以找到主機 E.上有兩個內容處理元件解決方案是需要離開一種內容處理元件。這項措施因為編目、 內容處理及分析處理取決於可用資源,而非數內容處理元件的數量。The small, medium, large, or extra large search architecture samples run on virtual machines, but they can also run on physical servers. In the sample farm architectures, just move the search components from the virtual machines to the host server and take away the virtual machines. Each physical server can host up to four index components, but only one of each type of the other search components. If you for example change the medium sample search architecture to use physical servers, you'll find that you have two content processing components on Host E. The solution is to take away one of the content processing components. This works because crawling, processing of content, and processing of analytics depend on the amount of resources that are available, not the number of content processing components.

選擇以實體或虛擬的方式執行伺服器

選擇主機伺服器的硬體資源Choose hardware resources for the host servers

每個搜尋元件和搜尋資料庫都需要主機伺服器的最少硬體資源數量,才能執行良好。但是,您擁有的硬體資源越多,搜尋架構的效能就越好。因此,數量最好高於最少硬體資源數量。每個搜尋元件所需的資源取決於工作量,大部分會視編目率、查詢率和索引項目數目而定。Each search component and search database requires a minimum amount of hardware resources from the host server to perform well. But, the more hardware resources you have, the better the performance of your search architecture will be. So it's a good idea to have more than the minimum amount of hardware resources. The resources each search component requires depends on the workload, mostly determined by the crawl rate, the query rate, and the number of indexed items.

例如,在 Windows Server 2008 R2 Service Pack 1 (SP1) 上裝載虛擬機器時,每部虛擬機器無法使用四個以上的 CPU 核心。使用 Windows Server 2012 或更新版本,您可以每部虛擬機器使用八個以上的 CPU 核心。然後,您可以每部虛擬機器擴充更多 CPU 核心,而非垂直擴充更多虛擬機器。請設定裝載相同搜尋元件的伺服器或虛擬機器,且硬體資源相同。我們將使用索引元件做為範例。在虛擬機器上裝載索引分割區時,效能最弱的虛擬機器會決定整體搜尋架構的效能。For example, when hosting virtual machines on Windows Server 2008 R2 Service Pack 1 (SP1), you can't use more than four CPU cores per virtual machine. With Windows Server 2012 or newer, you use eight or more CPU cores per virtual machine. Then you can scale out with more CPU cores for each virtual machine instead of scaling up with more virtual machines. Set up servers or virtual machines that host the same search components, with the same hardware resources. Let's use the index component as an example. When you host index partitions on virtual machines, the virtual machine with the weakest performance determines the performance of the overall search architecture.

一般儲存體資源General storage resources

請確定每個主機伺服器具有足夠的磁碟空間的基本安裝的 Windows Server 作業系統和 SharePoint Server 程式檔。診斷記錄、 偵錯時,例如主機伺服器也需要的可用硬碟空間和建立記憶體傾印,日常作業,以及分頁檔案。一般而言,80 GB 的磁碟空間是足夠的 Windows Server 作業系統和 SharePoint Server 程式檔。Make sure that each host server has enough disk space for the base installation of the Windows Server operating system and for the SharePoint Server program files. The host server also needs free hard disk space for diagnostics such as logging, debugging, and creating memory dumps, for daily operations, and for the page file. Normally, 80 GB of disk space is enough for the Windows Server operating system and for the SharePoint Server program files.

請新增儲存體,供每部資料庫伺服器的 SQL 記錄空間使用。如果您未設定資料庫伺服器經常備份資料庫,則 SQL 記錄空間會使用許多儲存體。如需如何規劃 SQL 資料庫的詳細資訊,請參閱規劃及設定儲存設備與 SQL Server 容量 (SharePoint Server)Add storage for the SQL log space for each database server. If you don't set the database server to back up the databases often, the SQL log space uses lots of storage. For more information about how to plan SQL databases, see Storage and SQL Server capacity planning and configuration (SharePoint Server).

分析報表資料庫需要最低儲存空間可能會有所不同。這是因為的儲存量取決於在使用者與 SharePoint Server 的互動方式。當使用者經常互動時,通常有個以上的事件存放區。檢查您目前的搜尋架構使用分析資料庫儲存空間量並至少指派此經過重新設計拓撲。The minimum storage that the analytics reporting database requires can vary. This is because the amount of storage depends on how users interact with SharePoint Server. When users interact frequently, there usually are more events to store. Check the amount of storage your current search architecture uses for the analytics database, and assign at least this amount for your redesigned topology.

小型搜尋伺服器陣列的最低硬體資源Minimum hardware resources for the small search farm

此表格顯示每部應用程式伺服器或資料庫伺服器所需的最少硬體資源數量。This table shows the minimum amount of hardware resources that each application server or database server needs.

伺服器Server 在主機上On host 儲存Storage RAMRAM 處理器1Processor1 網路頻寬Network bandwidth
具有查詢處理和索引元件的應用程式伺服器。Application server that has query processing and index components. A、BA, B 500 GB2 3500 GB2,3 32 GB2 332 GB2,3 1.8 GHz CPU 核心2,3 x 81.8 GHz 8x CPU cores2,3 1 Gbps1 Gbps
具有編目、搜尋管理、分析及內容處理元件的應用程式伺服器。Application server that has crawl, search administration, analytics and content processing components. A、BA, B 200 GB200 GB 8 GB8 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps
具有所有搜尋資料庫的資料庫伺服器。Database server that has all search databases. C、DC, D 100 GB100 GB 16 GB16 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps

1CPU 核心數這裡,而非 CPU 執行緒數。1The number of CPU cores is specified here, not the number of CPU threads.

2與 SharePoint Server 2013 所需的資源的最少數量是 500 GB RAM、 16 GB RAM、 以及四個 CPU 核心。2With SharePoint Server 2013 the minimum amount of resources needed are 500 GB RAM, 16 GB RAM, and four CPU cores.

3您也可以使用 SharePoint Server 2016 與 500 GB 儲存空間、 16 GB RAM、 及四核心 CPU、 但然後每個索引元件只可以保留 10 萬個項目及搜尋伺服器陣列僅支援相同的內容量為 SharePoint Server 2013 搜尋伺服器陣列。3With SharePoint Server 2016 you can also use 500 GB storage, 16 GB RAM, and four CPU cores, but then each index component can only hold 10 million items and the search farm only supports the same volume of content as a SharePoint Server 2013 search farm.

中型搜尋伺服器陣列的最低硬體資源Minimum hardware resources for the medium search farm

此表格顯示每部應用程式伺服器或資料庫伺服器所需的最少硬體資源數量。This table shows the minimum amount of hardware resources that each application server or database server needs.

伺服器Server 在主機上On host 儲存Storage RAMRAM 處理器1Processor1 網路頻寬Network bandwidth
具有查詢處理和索引元件的應用程式伺服器。Application server that has query processing and index components. A、B、C、DA, B, C, D 500 GB2 3500 GB2,3 32 GB2 332 GB2,3 1.8 GHz CPU 核心2,3 x 81.8 GHz 8x CPU cores2,3 1 Gbps1 Gbps
具有索引元件的應用程式伺服器。Application server that has an index component. A、B、C、DA, B, C, D 500 GB2 3500 GB2,3 32 GB2 332 GB2,3 1.8 GHz CPU 核心2,3 x 81.8 GHz 8x CPU cores2,3 1 Gbps1 Gbps
具有分析和內容處理元件的應用程式伺服器。Application server that has analytics and content processing components. E、FE, F 300 GB300 GB 8 GB8 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps
具有編目、搜尋管理及內容處理元件的應用程式伺服器。Application server that has crawl, search administration, and content processing components. E、FE, F 100 GB100 GB 8 GB8 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps
具有所有搜尋資料庫的資料庫伺服器。Database server that has all search databases. G、HG, H 400 GB400 GB 16 GB16 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps

1CPU 核心數這裡,而非 CPU 執行緒數。1The number of CPU cores is specified here, not the number of CPU threads.

2與 SharePoint Server 2013 所需的資源的最少數量是 500 GB RAM、 16 GB RAM、 以及四個 CPU 核心。2With SharePoint Server 2013 the minimum amount of resources needed are 500 GB RAM, 16 GB RAM, and four CPU cores.

3您也可以使用 SharePoint Server 2016 與 500 GB 儲存空間、 16 GB RAM、 及四核心 CPU、 但然後每個索引元件只可以保留 10 萬個項目及搜尋伺服器陣列僅支援相同的內容量為 SharePoint Server 2013 搜尋伺服器陣列。3With SharePoint Server 2016 you can also use 500 GB storage, 16 GB RAM, and four CPU cores, but then each index component can only hold 10 million items and the search farm only supports the same volume of content as a SharePoint Server 2013 search farm.

大型搜尋伺服器陣列的最低硬體資源Minimum hardware resources for the large search farm

此表格顯示每部應用程式伺服器或資料庫伺服器所需的最少硬體資源數量。This table shows the minimum amount of hardware resources that each application server or database server needs.

伺服器Server 在主機上On host 儲存Storage RAMRAM 處理器1Processor1 網路頻寬Network bandwidth
具有查詢處理和索引元件的應用程式伺服器。Application server that has query processing and index components. A、B、C、D、E、G、HA, B, C, D, E, G, H 500 GB2 3500 GB2,3 32 GB2 332 GB2,3 1.8 GHz CPU 核心2,3 x 81.8 GHz 8x CPU cores2,3 1 Gbps1 Gbps
具有索引元件的應用程式伺服器。Application server that has an index component. A、B、C、D、E、F、G、H、I、JA, B, C, D, E, F, G, H, I, J 500 GB2 3500 GB2,3 32 GB2 332 GB2,3 1.8 GHz CPU 核心2,3 x 81.8 GHz 8x CPU cores2,3 1 Gbps1 Gbps
具有分析和內容處理元件的應用程式伺服器。Application servers that have analytics and content processing components K、L、M、NK, L, M, N 300 GB300 GB 8 GB8 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps
具有編目和搜尋管理元件的應用程式伺服器Application servers that have crawl and search administration components K、LK, L 100 GB100 GB 8 GB8 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps
具有搜尋資料庫的資料庫伺服器Database server that have search databases O、P、Q、RO, P, Q, R 500 GB500 GB 16 GB16 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps

2與 SharePoint Server 2013 所需的資源的最少數量是 500 GB RAM、 16 GB RAM、 以及四個 CPU 核心。2With SharePoint Server 2013 the minimum amount of resources needed are 500 GB RAM, 16 GB RAM, and four CPU cores.

3您也可以使用 SharePoint Server 2016 與 500 GB 儲存空間、 16 GB RAM、 及四核心 CPU、 但然後每個索引元件只可以保留 10 萬個項目及搜尋伺服器陣列僅支援相同的內容量為 SharePoint Server 2013 搜尋伺服器陣列。3With SharePoint Server 2016 you can also use 500 GB storage, 16 GB RAM, and four CPU cores, but then each index component can only hold 10 million items and the search farm only supports the same volume of content as a SharePoint Server 2013 search farm.

特大型搜尋伺服器陣列的最低硬體資源Minimum hardware resources for the extra large search farm

此表說明每個應用程式伺服器或資料庫伺服器所需的硬體資源的最少數量。您只可以建立與 SharePoint Server 2016 此範例伺服器陣列。This table shows the minimum amount of hardware resources that each application server or database server needs. You can only build this sample farm with SharePoint Server 2016.

伺服器Server 在主機上On host 儲存Storage RAMRAM 處理器1Processor1 網路頻寬Network bandwidth
具有索引元件的應用程式伺服器。Application server that has index components. A-XA-X 500 GB500 GB 32 GB32 GB 1.8 GHz 8x CPU 核心1.8 GHz 8x CPU cores 1 Gbps1 Gbps
具有查詢處理和索引元件的應用程式伺服器。Application server that has query processing and index components. Y、ZY, Z 500 GB500 GB 32 GB32 GB 1.8 GHz 8x CPU 核心1.8 GHz 8x CPU cores 1 Gbps1 Gbps
具有編目、搜尋管理或內容處理元件的應用程式伺服器Application servers that have crawl, search administration, or content processing components AA-AFAA-AF 100 GB100 GB 8 GB8 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps
具有分析處理元件的應用程式伺服器Application servers that have analytics processing components AG、AHAG, AH 800 GB800 GB 8 GB8 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps
具有搜尋資料庫的資料庫伺服器Database servers that have search databases AI-ALAI-AL 500 GB500 GB 16 GB16 GB 1.8 GHz 4x CPU 核心1.8 GHz 4x CPU cores 1 Gbps1 Gbps

1CPU 核心數這裡,而非 CPU 執行緒數。1The number of CPU cores is specified here, not the number of CPU threads.

規劃儲存效能Plan storage performance

儲存空間的速度會影響搜尋效能。請確定您的儲存空間速度足以處理來自搜尋元件和資料庫的流量。磁碟速度是以每秒 I/O 作業數 (IOPS) 來測量。The speed of the storage affects the search performance. Make sure that the storage you have is fast enough to handle the traffic from the search components and databases. Disk speed is measured in I/O operations per second (IOPS).

您決定將搜尋元件資料與作業系統資料分散在儲存體中的方式,會影響搜尋效能。您不妨:The way that you decide to distribute data from the search components and from the operating system across your storage, affects search performance. It's a good idea to:

  • Windows Server 作業系統檔案、 SharePoint Server 程式檔案和診斷記錄分割三個不同的儲存磁碟區或分割區的一般效能。Split the Windows Server operating system files, the SharePoint Server program files, and diagnostic logs across three separate storage volumes or partitions with normal performance.

  • 將搜尋元件資料另外儲存在一個高效能的儲存磁碟區或分割區。針對索引元件,此儲存體也必須要有高效能。Store the search component data on a separate storage volume or partition. For index components, this storage must also have high performance.

    注意

    您可以在主機上安裝 SharePoint Server 時設定自訂搜尋元件資料的位置。儲存資料,需要在主機上的任何搜尋元件會將它儲存在此位置。若要變更此位置之後,必須重新安裝 SharePoint Server。You can set a custom location for search component data when you install SharePoint Server on a host. Any search component on the host that needs to store data, stores it in this location. To change this location later, you have to reinstall SharePoint Server.

選擇儲存體類型Choose type of storage

如需儲存架構和磁碟類型的概觀,請參閱<規劃及設定儲存設備與 SQL Server 容量 (SharePoint Server 2013)>。裝載索引、分析處理與搜尋管理元件 (或搜尋資料庫) 的伺服器所需要的儲存空間,必須可以維持低延遲,同時提供足夠的每秒 I/O 作業數 (IOPS)。下列各表顯示這些搜尋元件和資料庫各需要多少 IOPS。For an overview of storage architectures and disk types, see Storage and SQL Server capacity planning and configuration (SharePoint Server 2013). The servers that host the index, analytics processing, and the search administration components, or search databases, require storage that can maintain low latency, while providing sufficient I/O operations per second (IOPS). The following tables show how many IOPS each of these search components and databases require.

如果您部署共用儲存設備 (例如 SAN/NAS),一個搜尋元件的尖峰磁碟負載通常會跟其他搜尋元件的尖峰磁碟負載同時發生。若要得到搜尋作業需要從共用儲存設備得到的 IOPS 數,您需要將這每個元件的 IOPS 相加。If you deploy shared storage like SAN/NAS, the peak disk load of one search component typically coincides with the peak disk load of another search component. To get the number of IOPS search requires from the shared storage, you need to add up the IOPS requirement of each of these components.

搜尋元件 IOPS 需求Search component IOPS requirements

元件名稱Component name 元件詳細資料Component details IOPS 需求IOPS requirements 使用個別儲存磁碟區/磁碟分割Use of separate storage volume/partition
索引元件Index component 合併索引及處理和回應查詢時使用儲存設備。Uses storage when merging the index and when handling and responding to queries. 300 IOPS 用於 64 KB 隨機讀取。300 IOPS for 64 KB random reads.
100 IOPS 用於 256 KB 隨機寫入。100 IOPS for 256 KB random writes.
200 MB/s 用於循序讀取。200 MB/s for sequential reads.
200 MB/s 用於循序寫入。200 MB/s for sequential writes.
Yes
分析元件Analytics component 在本機以大量處理方式分析資料。Analyzes data locally, in bulk processing. No Yes
編目元件Crawl component 在將下載的內容傳送至內容處理元件之前,先將該內容儲存到本機。儲存空間受限於網路頻寬。Stores downloaded content locally, before it sends it to a content processing component. Storage is limited by network bandwidth. No Yes

搜尋資料庫 IOPS 需求Search database IOPS requirements

資料庫名稱Database name IOPS 需求IOPS requirements I/O 子系統的一般負載。Typical load on I/O subsystem.
編目資料庫Crawl database 中至高 IOPSMedium to high IOPS 每秒每文件10 IOPS (DPS) 編目率。10 IOPS per 1 document per second (DPS) crawl rate.
連結資料庫Link database 中 IOPSMedium IOPS 搜尋索引中每 100 萬個項目 10 IOPS。10 IOPS per 1 million items in the search index.
搜尋管理資料庫Search administration database 低 IOPSLow IOPS 不適用。Not applicable.
分析報表資料庫Analytics reporting database 中 IOPSMedium IOPS 不適用。Not applicable.

選擇您的搜尋架構如何支援高可用性Choose how your search architecture supports high availability

如果您不熟悉高可用性策略時,以下是可讓您從著手文章:為 SharePoint Server 打造高可用性架構和策略。當您主機備援搜尋元件和個別的容錯網域上的資料庫時,在一組件中的伺服器陣列中斷不需要停機完成服務。但是,搜尋效能會降低因為搜尋元件無法再共用負載。若要減少遺失的單一伺服器的可能性是不錯的選項以改善本機備援。對於搜尋架構中每個主機伺服器:If you aren't familiar with high availability strategies, here's an article that will get you started: Create a high availability architecture and strategy for SharePoint Server. When you host redundant search components and databases on separate fault domains, an outage in one part of the farm doesn't take down the complete service. But, search performance will degrade because the search components can't share the load any longer. To reduce the possibility of losing a single server it's a good idea to improve local redundancy. For each host server in your search architecture:

  • 在每部伺服器上使用 RAID 儲存體。Use RAID storage on each server.

  • 在每部伺服器上安裝多個備援網路連線。Install multiple redundant network connections on each server.

  • 針對每部伺服器,安裝多個配有獨立電線或不斷電供應系統 (UPS) 的備援電源供應器。Install multiple redundant power supplies with independent wiring or an uninterruptible power supply (UPS) for each server.

所有範例搜尋架構都會在獨立伺服器上裝載備援搜尋元件。在範例搜尋架構中,每個主機配對中最右邊的主機都是備援。以下是具有所述備援主機的大型搜尋架構:All of the sample search architectures host redundant search components on independent servers. In the sample search architectures, the rightmost host in each host pair is redundant. Here's the large search architecture with outlined redundant hosts:

Diagram of large enterprise search farm indicating which servers host redundant search components.