Berkeley DB Family

When I configure logs to write to memory and the database to be backed on disk, I get the following error when I safely shutdown the application and restart it.

file unknown has LSN 1/13017, past end of log at 1/28
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment

This seems logical, as the log files are no longer there as they were lost when user space memory was cleaned up on application shutdown. Is there a way to work around this? Resetting the LSNs on shutdown isn't an option as a 20 GB database can take a couple of hours to complete.

I do not require fatal recovery, I just want the performance of logging to memory while keeping a persistent store for when I reboot the system.