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

For example, you can use the DUMP command to dump transaction logs to the dump device (preferably, a
separate disk drive). You can set this up to occur at regular intervals, such as every 15 minutes or every hour.
Next, you can create a backup job that backs up these transaction logs onto archival media every day.
In general, when you implement Data Protector Express to back up your SQL Server databases, continue
to use SQL Server’s internal commands to duplicate and back up transaction logs. Set up a separate
Data Protector Express backup job to write these duplicated transaction logs to archival media.
Restoring Microsoft SQL Server
When restoring SQL Server databases, you must:
1. Restore a full backup of the SQL Server database.
2. Restore the logs in the order created.
3. Follow special procedures when renaming databases (if you rename databases).
NOTE:
Any time Data Protector Express returns an error message that is greater than 10000, a
Microsoft SQL or Exchange error has occurred. Refer to your Microsoft documentation for more
information as this is a Microsoft error code.
Restoring Microsoft SQL Server databases and transaction logs 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.)
Restoring Microsoft SQL Server 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.
User’s Guide 67