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

An alternative method is to manually create the entire database itself. Thus, when Data Protector
Express attempts to restore the database, since the database already exists, it will use that
preexisting database. This allows you to restore a database in a new location, since Data
Protector Express does not check to see if it is the original device before restoring the database,
because the database already exists.
NOTE: An alternative method is to manually create the entire database itself. Thus, when
Data Protector Express attempts to restore the database, since the database already exists, it
will use that preexisting database. This allows you to restore a database in a new location,
since Data Protector Express does not check to see if it is the original device before restoring
the database, because the database already exists.
Using Data Protector Express, create a restore job and run the job to restore the database.
You must start with a full backup version of the database to restore which was created using
a Full backup job.
4. Create additional restore jobs to restore each transaction log backed up after the full database
you restored. You must create and run a separate restore job for each transaction log.
For example, if you ran a full backup on Friday and incremental jobs (that is, jobs that backed
up only the transaction logs) on the following Monday and Tuesday, you must first restore the
database using Friday’s version of the database. Next, create a run and restore job that
restores Monday’s version (Monday’s transaction log). Finally, create and run a job that
restores Tuesday’s version (Tuesday’s transaction log).
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.
HP recommends 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.
Restoring Microsoft SQL Server 2000 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.
HP recommends 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
54 Working with Third-Party Applications