Berkeley DB Family

Hi there,

I am currently testing my JE implementation for reliability of backup. Although I haven't encountered any problems with the method I am employing (hot backup as per the getting started guide; e.g. copying .jdb files to an archival location) there is one aspect of the process that I am unsure of.

My implementation is a little different to most I would say as I am using JE as the back end for a JSP implementation. Consequently in order to avoid the overhead of opening the environment and entity store for each read/write, I am storing these objects at the application context level which is created whenever the weblogic web app is started or stopped. Therefore these objects are remaining open for long periods of time. FYI I am using DPL.

The aspect that I am unsure of is that initially no .jdb file is created in the directory that I have specified. After some period of time, roughly a day or two the .jdb file appears. It is only then that I can perform hot backup of the database.

I have searched the API's for methods that may help to write this file sooner. So far I have played with the StoreConfig.setDefferredWrite() method to no avail. In addition I have tried both the Environment and EntityStore sync() methods, also to no avail. The former actually throws a null pointer exception for reasons unknown.

I would greatly appreciate any suggestions as to where I might look in order to better understand this behavior.

Many thanks,
Reece.