Data Protector Express User's Guide (TC330-96002, October 2010)

During the restore processes, Data Protector Express will recreate the database and all seg m ents
exactly as they existed when the backup was per formed.
To do this, Data Protector Express first determines if the database exists. If the database does exist,
Data Protector Express will use the database as is without any further processing or changes.
3. If the database does not exist, Data Protector Express next identifies the database devices on which
the da tabase was originally located. If the appropriate database device already exists, Data
ProtectorExpresswillusethatdeviceasiswithoutfurtherprocessing.
If the database device does not exist, Data Protector Express recreates the database device at its
original location and with its original size. After all the database devices are created, Data Protector
Express then creates the database with all the original options at the original locations.
TIP:
Thismethodmakesdisasterrecoverysimple. TheusersimplycreatearestorejobandallowsData
Protector Express to recreate whatever is needed in order to successfully restore the database.
NOTE:
If a disk drive fails and is not replaced, Data Protector Express will be unable to restore your
database because it will be unable to recreate a database device.
For example, if a segment of your database resides on a database named ‘DATA’ at
D:\MSSQL\DATA\DATA.DAT,ifD: is lost and not replaced, when Data Protector Express attempts
to recreate the database device, it will fail, since D: no longer exists.
Toavoidthisproblem,manuallyrecreatethedatabasedeviceatsomeothervalidlocation.Itmustbe
at least as lar
ge as the original database device since Data Protector Express will attempt to create a
database segment on it the same size as the original database.
An alternative method is to ma nually 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. Th
is allows you to restore a database in a new location, since D ata 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
pr eexistin
g database. This allows you to restore a database in a new location, since Data
Protector E
xpress 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 ).
68
Working with Third-Party Applications