The following steps assume that there is a single transaction log file, which has existed since the database was created. They also assume that previous backups of the database file have been made and are available, for example on tape.
Make a copy of the database and log file.
Restore the database (.db) file, not the log file, from tape into a temporary directory.
Start the database using the existing transaction log and the -a option, to apply the transactions and bring the database file up to date.
Start the database in your normal way.
Any new activity is appended to the current transaction log.
This example illustrates recovery using a mirrored transaction log.
Suppose you have a consolidated database file named consol.db in a directory c:\dbdir, and a transaction log file c:\logdir\consol.log that is mirrored to d:\mirdir\consol.mlg.
Back up the mirrored transaction log d:\mirdir\consol.mlg.
Replace the failed hardware and re-install all affected software.
Create a temporary directory to perform the recovery in (for example, c:\recover).
Restore the most recent backup of the database file, consol.db, to c:\recover\consol.db.
Copy the mirror transaction log, d:\mirdir\consol.mlg, to the recovery directory with a .log extension, giving c:\recover\consol.log.
Start the database using the following command:
dbeng10 -a c:\recover\consol.log C:\recover\consol.db
Shut down the database server.
Back up the recovered database and transaction log from c:\recover.
Copy the files from c:\recover to the appropriate production directories:
Copy c:\recover\consol.db to c:\dbdir\consol.db.
Copy c:\recover\consol.log to c:\logdir\consol.log, and to d:\mirdir\consol.mlg.
Restart your system normally.