I need to restore a database from a backup that contains logs until 5pm. The problem is i need to stop the logs at 3pm because the user deleted the email after 3pm. We didn't have single item retention turned on and the user purged the message from deleted items.
I ran the following eseutils cmd and it says its missing logs. I deleted the logs after 3pm and the chk file because my understanding of the chk file is it knows that the logs should be ending at 5pm. We thought if you remove the chk file and rename the last log file to XXX.log (where xxx is the first three letters/numbers in our log files) that it would stop at that point.
eseutil /r XXX /l Z:Recovery-db\_restoredlogs /d Z:\Recovery-db /i /a
Database is in a dirty shutdown state after this point
If we don't delete any logs and the same command we still have a dirty shutdown state but no missing log error. If we run the /p on the database it comes up clean be we cant mount it. This happens to the database where we delete the logs as well. I forgot the error we get when we mount it. If we let TSM restore the database and mount it it works fine but we don't see a way in TSM to stop the logs at 3pm.
We also ran the command without the /a and had the same results.