Some database management systems such as Pervasive SQL and MongoDB pre-allocate large volumes of empty space to their database files so that the file sizes of these databases do not need to change whenever new records are added. The timestamps of these databases also do not change while the databases are in use, even if new data is written to them. With no changes to the file size or timestamps, however, the backup engine does not pick up file changes, which can lead to files not being backed up.
The ESE backup client solves this problem by sourcing extra file information directly from the operating system before the backup starts. A list of all open files and their respective access types (read-only or read-write) is retrieved. The backup client then compares the list of open files to the list of files selected for backup, checking for changes in those open files that are included in the backup selection.
To backup these file types successfully, you need to enable open file detection in the ESE backup client.
1. Change the ESE backup client service to run as an Administrator. (This avoids possible lockup during the scanning phase of the backup.)
2. Stop the ESE backup client service and edit the a5backup.properties file. This file's default location is C:\Program Files\Redstor Backup Pro\Backup Client ESE\.
3. Add the following setting:
If Archiving is enabled, also add the following setting:
4. Save the file and start the backup service.
5. Ensure all the relevant files are included in the backup selection.
Note: Open file detection is similar to mandatory patching in the Server Edition.