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.

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

in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>, the SQL Server backup tools provide an<br />

important advantage compared to the SharePoint Portal Server 2003 Data Backup<br />

<strong>and</strong> Restore utility.<br />

With the SQL Server backup tools, you can get a full-fidelity, complete backup<br />

of the databases used by SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>. You can restore<br />

any or all of these databases. In a scenario where portal databases are backed up<br />

using the SQL Server backup tools, you need to remember that the index is not<br />

restored. You can restore the portal site via the SharePoint Portal Server Central<br />

Administration page after you have restored the portal databases by using the SQL<br />

Server backup tools. For this scenario to work, the spsadmin service account must<br />

either be a member of the Administrator’s group on the Web front-end server or be a<br />

Windows SharePoint Services administrator. According to recommended security<br />

practices, you should not grant the spsadmin account administrator rights; on the<br />

server, the spsadmin account should be granted as few privileges as possible. By<br />

default, the content access account is granted Windows SharePoint Services administrator<br />

rights. You should create a new Windows security group, <strong>and</strong> add both the<br />

content access account <strong>and</strong> the spsadmin service account to this group. Then, using<br />

the Windows SharePoint Services administration Web pages, you should change the<br />

Windows SharePoint Services administrator account to be this Windows security<br />

group. From Windows SharePoint Services Central Administration, locate the Security<br />

Configuration section <strong>and</strong> click Set SharePoint administration group. You must<br />

have installed the SQL Server 2000 client tools to be able to use the SQL Server<br />

backup tools or use the OSQL comm<strong>and</strong>-line tools that are installed with the Windows<br />

<strong>Microsoft</strong> Data Engine. Both kinds of tools provide you with the possibility to<br />

perform differential backups of the relevant databases.<br />

A differential backup backs up the parts of the database that have changed<br />

since the last full database backup. It also backs up any activity that took place during<br />

the differential backup, as well as any uncommitted transactions in the transaction<br />

log. Performing a differential backup minimizes the time that is necessary for<br />

backing up a frequently modified database.<br />

Note Perform a differential backup only if you have performed a full database<br />

backup. Remember that you don’t back up the configuration database.<br />

Windows SharePoint Services uses two types of databases: content databases<br />

<strong>and</strong> configuration databases. Data in the lists <strong>and</strong> libraries on SharePoint sites go<br />

into the content database. The virtual server settings, such as the mapping of a site<br />

URL to the physical storage location, go into the configuration database. SharePoint<br />

Portal Server uses two additional types of databases: the profile database <strong>and</strong> the services<br />

database. User profiles are stored in the profile database. Services information,<br />

such as gatherer logs <strong>and</strong> subscription schedules, goes into the services database.

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

Saved successfully!

Ooh no, something went wrong!