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.

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

■ IIS metabase<br />

■ Root directories of Windows SharePoint Services–extended virtual servers<br />

■ Custom Web Part assemblies<br />

■ Custom templates<br />

■ Add-in software<br />

The following sections discuss these components in detail.<br />

IIS Metabase<br />

IIS automatically backs up the metabase on each front-end Web server to the<br />

%WinDir%System32\inetsrv\MetaBack directory. Back up the entire MetaBack<br />

directory for each individual front-end Web server to its own server subdirectory on<br />

the shared network location.<br />

Note You cannot just copy the metadata from one front-end Web server to<br />

another because the metadata is unique to each implementation of IIS 6.0.<br />

You can also use the iisback.vbs comm<strong>and</strong>-line utility to schedule <strong>and</strong> perform regular<br />

backups of the metabase on each front-end Web server remotely, beyond the<br />

normal automatic backup schedule. You should also manually create IIS 6.0 metabase<br />

backups before <strong>and</strong> after making any changes to virtual servers or application<br />

pools so that the configuration can be quickly restored if necessary.<br />

Root Directories<br />

The root directory of a Windows SharePoint Services–extended virtual server contains<br />

the Web.config files, which are text files that contain custom XML elements or<br />

options for Web Parts <strong>and</strong> Web Part pages for each virtual server on the front-end<br />

Web Servers. You should back up the complete root directory for each front-end Web<br />

server to the shared library on a regular basis. The tree must be restored to the same<br />

path from which it was copied, <strong>and</strong> it must correspond to the paths identified within<br />

the IIS 6.0 metadata.<br />

Custom Web Part Assemblies<br />

Custom Web Part assemblies should be kept in the shared directory <strong>and</strong> reinstalled<br />

on the front-end Web servers when new servers are added to the server farm or<br />

restored after a failure. Custom Web Part assemblies are located by default in either<br />

the bin folder under the virtual server root directory of the computer running Share-<br />

Point Portal Server or the Global Assembly Cache (GAC) folder %WinDir%assembly,<br />

depending on your software development best practices <strong>and</strong> st<strong>and</strong>ards.

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

Saved successfully!

Ooh no, something went wrong!