HP Data Protector Express Basic-Software - Manual (Page 69)

In the last incremental restore job, click the Advanced Options button and select the Finalize recovery
of MS SQL databases check box. If you do not select this check box, the database will be offline.
Restoring Microsoft SQL Server master databases
A damaged master database is evident by the failure of the SQL Server to start, by segmentation faults or
input/output errors or by a report from DBCC. An example of an error might be damage caused by
media failure in the area in which master database is stored.
The procedure used to recover a damaged master database is different from the procedure used to
recover user databases. If the master database becomes unusable, it must be restored from a previous
dump. All changes made to the master database after the last dump are lost when the dump is reloaded
and therefore must be reapplied.
It is strongly recommended that the master database be backed up each time it is changed. This is best
accomplished by prohibiting the creation of user-defined objects in the master database and by being
aware of the statements and system procedures, and the equivalent actions in SQL Server Management
Studio, that modify it.
Please refer to the documentation for Microsoft SQL Server for information on the proper way to restore
the master databases.
Protecting Microsoft Windows SharePoint Services
In this section
• Windows SharePoint Services protection concepts
• Protecting Windows SharePoint Services
• Restoring SharePoint Services
• Using Disaster Recovery with Windows SharePoint Services
Overview
This section contains information for the backup and restore of Windows SharePoint Services.
Windows SharePoint Services protection concepts
Microsoft Windows SharePoint Services is a free component of certain Windows Server operating
systems. Microsoft SharePoint Portal Server is a web-based collaboration application that runs on
Microsoft Windows and uses SharePoint Services. SharePoint Services uses a Microsoft SQL Server
database for storing data and metadata. The version of SQL Server depends upon the installation and
whether SharePoint Portal Server is installed. Windows SharePoint Services uses a special version of
MSDE, known as SQL Server 2000 Desktop Engine (Windows) or WMSDE. If SharePoint Portal Server is
installed, SQL Server 2000 Desktop Engine (MSDE) or SQL Server 2000 is used instead.
Data Protector Express will automatically discover all SharePoint Services databases and manage them for
backup and recovery as separate objects. Backing up an entire system will also include those databases.
If you are using Microsoft SharePoint Portal Server or Microsoft Office SharePoint Server, you need to use
the Data Protector Express Agent for Microsoft SQL Server to protect the SQL Server database.
Protecting Windows SharePoint Services
Data Protector Express is designed specifically to protect the databases of Windows SharePoint Services.
These databases will appear in the Data Protector Express Administrator GUI with the name of the
database instance. This name will depend on the version of SharePoint Services that is installed.
When using SharePoint 2.0 “SHAREPOINT” is the default name. When using SharePoint Services 3.0,
“Microsoft ##SSEE” is the default name. In addition to storing Web site content in a WMSDE/SSEE
SQL database, Windows SharePoint Services stores certain files including Windows SharePoint Services
User’s Guide 69