IT tutorials
 
Technology
 

SharePoint 2010 : Planning Your Search Deployment - Environment Planning and Metrics (part 2) - Initial Deployment Guidelines

9/13/2013 9:37:49 PM
- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019

3. Initial Deployment Guidelines

It can be a difficult process to decide how large of a deployment and how many resources to dedicate to an initial search deployment. Generally speaking, if SharePoint 2010 is being installed as the first document management and collaboration tool, the search components can start out in their simplest form and scale out as documents are added and the adoption of SharePoint 2010 grows. However, this scenario is becoming rare, and most organizations will find themselves either upgrading to SharePoint 2010 from a previous version or migrating content from another system or from an ad hoc system, such as a file share. In these cases, initial deployment architectures and best practices can be useful.

Luckily, Microsoft gives some guidelines for what kinds of architectures can support different scenarios. These guidelines are based on the number of items that are indexed and searchable regardless of whether they come from inside or outside SharePoint 2010. The entirety of these documents is known as the corpus.

  • 1 million documents or less: All roles on a single server or one application server and one database server
  • 1 to 10 million documents: Web server and query server roles combined on one to two servers, one dedicated crawl server, and a dedicated database server
  • 10–20 million documents: Same architecture as 1 to 10 million documents model but with an additional crawl server and redundancy on the query servers—that is, use two query servers, each with two index partitions broken into half of the index partition on each and a mirror of the other server's half on each.
  • 20–40 million documents: For more than 20 million documents, a dedicated search farm is recommended. On a dedicated search farm, servers with the web server role are not necessary as long as the farm where searches are initiated has servers with this role and those servers are configured to direct queries to the dedicated farm. The farm should have a minimum of four query servers, each with a quarter of the index in an index partition. Each query server should also host a mirror of another server's partition for redundancy. In addition, two crawl servers, each with two crawlers, and two crawl databases, each with two crawlers associated with it, are recommended. In addition, it is recommended that two additional database servers be utilized to hold property databases and the Search Admin database.
  • 40–100 million documents: Any organization with more than 40 million documents will require a completely dedicated search farm with a high level of redundancy. The web server role should probably be handled by the content farm except if a dedicated web server is allocated for indexing (recommended). The farm should have six to ten query servers, each holding an equal portion of the index in an index partition, as well as a mirror of one of the other index partitions from another server. There should also be four crawl servers and four database clusters where the four crawl servers write to two crawl databases.

Use the following flowco easily see how many servers will be required for a deployment.

Image

Figure 2. Deployment sizing decision flowchart

 
Others
 
- SharePoint 2010 : Planning Your Search Deployment - Environment Planning and Metrics (part 1)
- SharePoint 2010 Components : Web Server Role, Query Server Role, Database Server Role
- Windows 8 : Troubleshooting Common Disk Problems (part 3) - Defragmenting Disks
- Windows 8 : Troubleshooting Common Disk Problems (part 2) - Checking for Disk Errors
- Windows 8 : Troubleshooting Common Disk Problems (part 1) - Repairing Disk Errors and Inconsistencies
- Windows Small Business Server 2011 : Working with Shares (part 3) - Managing Shares
- Windows Small Business Server 2011 : Working with Shares (part 2) - Creating a New Share Using Windows Explorer
- Windows Small Business Server 2011 : Working with Shares (part 1) - Creating a New Share Using Windows SBS Console
- Understanding the Default Windows Small Business Server 2011 Storage Configuration
- Windows 7 : Managing Hard Disks - Hard Disk Troubleshooting
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
Technology FAQ
- Is possible to just to use a wireless router to extend wireless access to wireless access points?
- Ruby - Insert Struct to MySql
- how to find my Symantec pcAnywhere serial number
- About direct X / Open GL issue
- How to determine eclipse version?
- What SAN cert Exchange 2010 for UM, OA?
- How do I populate a SQL Express table from Excel file?
- code for express check out with Paypal.
- Problem with Templated User Control
- ShellExecute SW_HIDE
programming4us programming4us