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.

Propagating Content Indexes<br />

Chapter 8: Planning Your Information Structure 167<br />

Index propagation occurs only when the Search application <strong>and</strong> the Index application<br />

are run on two different servers in a medium or large server farm. Propagation<br />

happens automatically at the end of every successful update (or crawl). Before<br />

propagation can be successful, the following conditions must be met:<br />

■ You have configured a search service account for the server farm. This account<br />

must have local administrator permissions on the search (destination) server.<br />

■ The destination server is on a trusted domain.<br />

■ There is sufficient disk space available on the destination server. For each<br />

propagated index, allow for more than twice its size in disk space to accommodate<br />

both the current index <strong>and</strong> the propagating index.<br />

■ SMB (Server Message Block) traffic must be enabled between the two servers,<br />

<strong>and</strong> if there is a firewall between them, the appropriate ports must be opened<br />

too. These ports include the common Netbios <strong>and</strong> RPC (Remote Procedure<br />

Call) ports.<br />

Propagation is considered successful if the index is successfully copied to any<br />

one search server. If you have a scenario where propagation is successful to one or<br />

more, but not all, search servers, the search servers to which propagation failed is<br />

taken off line, an error is logged in the event log, <strong>and</strong> the error appears on the propagation<br />

status page.<br />

Note If propagation fails because of lack of disk space on the destination<br />

server, SharePoint Portal Server 2003 logs an error in the Application Log of<br />

the Windows Server 2003 Event Viewer (event log) of both the destination<br />

search server <strong>and</strong> the index management server.<br />

The contents of a new index are not accessible on the search server<br />

until propagation has been completed. The index is not accessible if propagation<br />

fails, even if a previous propagation was successful.<br />

Updating Content Indexes<br />

The four methods for updating content indexes are as follows:<br />

■ Full<br />

■ Incremental<br />

■ Incremental (inclusive)<br />

■ Adaptive

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

Saved successfully!

Ooh no, something went wrong!