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.

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

Before beginning an update, the content index is in the “initializing” state. If<br />

there are a large number of alerts or people profiles, the content index can stay in<br />

the “initializing” state for a period of time.<br />

Note If power to the server is interrupted during an update, the update<br />

continues after power is restored. For a full update, the crawl restores the<br />

previous checkpoint <strong>and</strong> then resumes. For an incremental update, the<br />

crawl restores the previous checkpoint <strong>and</strong> then redoes all work that<br />

occurred after the previous checkpoint. The content index is still available<br />

for queries during this time.<br />

Updates <strong>and</strong> Permissions<br />

All updates pick up permission changes. Access control lists are indexed as part of<br />

a document’s properties. However, only the full update picks up changes to membership<br />

in local groups. Because of this, you should not use local groups to secure<br />

content that SharePoint Portal Server crawls.<br />

The Gatherer Log<br />

Each time SharePoint Portal Server 2003 creates or updates a content index, it also<br />

creates a gatherer log. The gatherer log is located in a table in the component settings<br />

database for the portal site <strong>and</strong> can be viewed by selecting links on the Site<br />

Settings—Configure Search And Indexing page of a portal. This log contains data<br />

about URLs accessed by SharePoint Portal Server while it is creating an index. An<br />

administrator can also configure the log to record successful accesses, indexing<br />

warnings, access errors, <strong>and</strong> accesses disallowed by rules, which it does not log by<br />

default.<br />

Viewing Gatherer Logs<br />

The latest gatherer log can be viewed on the SharePoint Portal Server Central<br />

Administration page, but only if the administrator has enabled advanced search<br />

administration mode. This view of the gatherer log includes summary or detailed<br />

information as well as customized views of the log.<br />

By default, the gatherer log shows only the information from the last crawl.<br />

When a new crawl begins, the log entries from the new crawl can overwrite previously<br />

recorded entries. However, the gatherer log does not overwrite entries that are<br />

less than five days old. Log entries over five days old are considered to be obsolete.<br />

If no crawl is performed for more than five days, the log remains unchanged until a<br />

new crawl begins. Then all entries are deleted.

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

Saved successfully!

Ooh no, something went wrong!