Restoring Microsoft Sql Server Databases And Transaction Logs; Restoring Microsoft Sql Server Databases With A New Name; Restoring Microsoft Sql Server 2000 And Sql Server 7 User Databases - HP BB118BV - StorageWorks Data Protector Express Package User Manual

When recreating a database, you must first restore the whole database (created by a backup job running in
full backup mode).
Next, you must restore the transaction logs in the order created and in separate jobs. No log can be
skipped when restoring.
For example, if you did a full backup on Monday and incremental backups each day Tuesday through
Friday, you must run five separate jobs: one restoring the database from Monday's full backup job and
then four additional separate jobs restoring each transaction log in sequential order, beginning Tuesday
and continuing with each log sequentially until Friday.
You do not have to follow these procedures when restoring databases backed up with full backup jobs.
(Full backup jobs back up the entire database, while Incremental and Differential jobs only back up the
database logs.)
You can rename a database while restoring using the normal procedures for renaming files outlined in
Restoring a file with a new name on page 78. This method involves changing the name on the Selection
tab of the restore job. However, you cannot rename the master database. When you restore a master
database, you must follow the procedures specified in the section below, Restoring Microsoft SQL Server
master databases.
Restoring Microsoft SQL Server 2000 and SQL Server 7 user
databases
To restore a database, begin by restoring the most recent full backup of the database, followed by all the
database logs, that is, backups made with the Backup mode set to either incremental or differential.
When a database is restored, if the database does not yet exist, Data Protector Express will create the
database where the database was originally located.
To restore a lost or damaged database
1. If the transaction log of the damaged or inaccessible user database is on an undamaged device, make
a backup of the transactions before proceeding. (This lets you preserve up to the minute transactions
that are not included on the backup tape.)
You may use either a DUMP TRANSACTION statement on the SQL server or use a Data Protector
Express Incremental backup job to back up only the transactions logs.
2. If you are restoring the database because the data in the database is no longer needed or is incorrect,
skip to step 3. The following instructions are for recreating database devices and the database which
had existed previously.
During the restore processes, Data Protector Express will recreate the database and all segments
exactly as they existed when the backup was performed.
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.