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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

772 Part IX: Maintaining a Server in Windows SharePoint Services<br />

If a content index contains corrupted data, you can force a full index rebuild to<br />

overwrite the corrupted index. Rebuilding a content index is accomplished by<br />

indexing the locations specified by the content sources <strong>and</strong> storing the results in the<br />

content index on the index server. You can also reset a damaged content index from<br />

the SharePoint portal site Configure Search <strong>and</strong> Indexing page in the Administration<br />

console if Advanced Search Administration mode is enabled. You can enable<br />

Advanced Search Administration mode in the Administration console, although it is<br />

recommended that you enable it during installation.<br />

When you reset a content index, you are emptying the index <strong>and</strong> you must<br />

perform a full update of that index to rebuild it. This can be a time-consuming <strong>and</strong><br />

resource-intensive process in an environment in which there is a great deal of content.<br />

In addition, during a full content index reset, any user who has search alerts set<br />

will receive all the alerts. If an index becomes corrupted beyond recovery or if an<br />

index management server fails, you can restore the indexes from the latest backup.<br />

To recover an index management server<br />

With the loss of an index management server, the content indexes for the server<br />

farm, in addition to all content sources for the portal sites, are lost unless the content<br />

indexes have been backed up using the SharePoint Portal Server Data Backup <strong>and</strong><br />

Restore utility. To recover an index management server, perform the following steps:<br />

1. Remove the failed server from the server farm topology before restoring it.<br />

2. Restore the server by using your st<strong>and</strong>ard image, or install SharePoint Portal<br />

Server on a newly built server.<br />

3. Connect to the configuration database for the server farm, <strong>and</strong> add the server<br />

to the topology as an index <strong>and</strong> job server.<br />

4. Restore the content indexes from the latest SharePoint Portal Server Data<br />

Backup <strong>and</strong> Restore Utility backup set. If a backup of the indexes does not<br />

exist, manually re-create any indexes <strong>and</strong> divisional content sources.<br />

Backing Up Databases by Using SQL Server Backup Tools<br />

SQL Server 2000 is the data store for SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>. This<br />

means you can leverage all the knowledge you have about backing up SQL Server<br />

databases. You can use the SQL Server backup tools in addition to the native Share-<br />

Point <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> backup tools Stsadm.exe <strong>and</strong> the SharePoint Portal<br />

Server 2003 Data Backup <strong>and</strong> Restore utility. In some ways, these backup tools overlap<br />

each other, but they also complement each other. You should use Stsadm.exe<br />

if you need the finest granularity possible. Using Stsadm.exe, you can restore site<br />

collections <strong>and</strong> personal sites without having to restore the entire site database.<br />

The SharePoint Portal Server 2003 Data Backup <strong>and</strong> Restore utility offers the<br />

most complete solution: it backs up all relevant databases as well as content sources<br />

<strong>and</strong> indexes. This is very important in deployments where it takes a long time to<br />

build indexes for all content sources. If you underst<strong>and</strong> the types of databases used

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

Saved successfully!

Ooh no, something went wrong!