16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

618 Part VII: Information Management in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

mind that if you reset the index, you’ll be starting simultaneous, full-index updates<br />

on each content source that writes to that index file. If you have a high number of<br />

content sources writing to that index file, it is possible to overload your server with<br />

the execution of multiple full-update builds to rebuild the content in that index file.<br />

Fourth, if you’re running in a server farm environment where the indexes are<br />

created on an Index server <strong>and</strong> then propagated to a Search server, bear in mind that<br />

the larger the index file, the longer the copy operation will last between the Index<br />

server <strong>and</strong> the Search server. When the Index server is crawling a content source,<br />

that information is being written to the local copy of the index on the Index server.<br />

Only after the crawling operations are completed will the index file be copied from<br />

the Index server to the Search server. Because this is a normal file copy operation,<br />

the larger the file, the more time that will be required to copy this file from the Index<br />

server to the Search server. Depending on available b<strong>and</strong>width between servers, this<br />

could end up being an hour or more of copy time between servers for extremely<br />

large index files. For the portal site content incremental update that occurs every 10<br />

minutes, this could mean that your copy operations do not finish before the next<br />

incremental crawl commences. A best practice is to perform a test copy of the largest<br />

index file to discern the amount of time required to copy a file from the Index server<br />

to the Search server <strong>and</strong> then verify that the copy time is within acceptable limits.<br />

If you need to create a new index file, perform these steps:<br />

1. On the Configure Search And Indexing page, in the Content Indexes section,<br />

click Manage content indexes.<br />

2. On the Manage Content Indexes page, click New Content Index.<br />

3. On the Create Content Index page, in the Name <strong>and</strong> Information section,<br />

perform the following: type a unique name for this index in the Name box.<br />

The name must be unique for this portal site. The description is not required to<br />

be filled in <strong>and</strong> is there for your purposes.<br />

4. In the Source Group box, type the source group name. This name should be<br />

thought out in advance of creating the index file because source groups play a<br />

pivotal role in the creation of search scopes.<br />

5. In the Server list, select the server on which the index will reside.<br />

6. Click OK.<br />

Tip Universal Naming Convention (UNC) names are not accepted here.<br />

The address must be a valid file system path for the server on which the<br />

index is being created.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!