The following example describes how transaction logs are recovered.
The circumstances are as follows:
Will you lose two days of production data? The answer is no. Because the transaction logs are complete, they contain all transactions from the point of the last full backup.
After you have restored the hardware, you need to perform a full restore. Do not select Erase All Existing Data. Not selecting this option will instruct the backup program to keep any existing log files. The full restore writes the database files and the log files that were backed up with the last full backup.
The restored log files are any log file saved up to the first log file on the current transaction log drive. For example, suppose that the full backup copied Edb00012.log through Edb00014.log. The log files on the transaction log drive would be Edb00015.log and up. The full restore will copy Edb00012.log through Edb00014.log and the information store database files that are part of the backup set.
When the information store service is started, it restores transactions from Edb00012.log through the last log file (such as Edb00019.log) and Edb.log, the most recent log file. When the process is complete, the database will be up-to-date. The log files contain signatures, which ensure that they are included in the sequence to be restored.