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.

Chapter 28: Disaster Recovery in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> 769<br />

Assemblies are unique, <strong>and</strong> each one can have different installation instructions.<br />

Some assemblies require that you edit the registry. Keep the directions for<br />

installing each assembly along with each assembly in the shared directory.<br />

Custom Templates<br />

If you have customized any site templates, these should be included in your regular<br />

script or backup process for each front-end Web server <strong>and</strong> copied to the network<br />

shared library. Copy the following directories:<br />

■ systemroot\Program Files\Common Files\<strong>Microsoft</strong> Shared\Web Server Extensions<br />

\60\config\<br />

■ systemroot\Program Files\Common Files\<strong>Microsoft</strong> Shared\Web Server Extensions<br />

\60\template\<br />

Add-in Software<br />

Add-in software includes the following:<br />

■ Language template packs for Windows SharePoint Services<br />

■ Web Part page solutions (third-party-developed aspx pages that include Web<br />

Parts)<br />

■ Templates that work with <strong>Microsoft</strong> Office<br />

■ <strong>Microsoft</strong> Office Web Parts <strong>and</strong> Components, which is a collection of Web Parts<br />

If you are using any add-in software packages, they must be reinstalled after<br />

restoring a front-end Web server. The backups should be located in the shared directory<br />

so that they can be reinstalled after a front-end Web server has been restored or<br />

when a new front-end Web server is added to the server farm.<br />

Optional Backups<br />

There is other data that is not intended to be restored to the front-end Web server<br />

but that is interesting enough to archive for analysis <strong>and</strong> long-term off-line reference.<br />

You might consider backing up the following log files:<br />

■ Internet Information Services (IIS) logs. %WinDir%System32\Logfiles<br />

\W3svc\*.log.<br />

■ Usage analysis log. %WinDir%System32\LogFiles\STS\ (available only if usage<br />

analysis is enabled).<br />

■ Other Windows SharePoint Services logs. STSAdm.log <strong>and</strong> OWSTimer.log<br />

from the %PersonalFolder%Local Settings\Temp directory. For STSAdm.exe,<br />

%PersonalFolder% is the personal folder of the person who installed Windows<br />

SharePoint Services on the front-end Web server. The STSAdm.log contains

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

Saved successfully!

Ooh no, something went wrong!