The RepliGo Server document cache database is growing too large, what can I do?

RepliGo Server caches a copy of documents and converted pages in an internal database for efficient access.  This cache is periodically pruned to delete entries older than seven days, by default.

On RepliGo Server versions before 1.3, it is possible for reclaimed space in the cache database to become fragmented, causing it to grow in size, reaching a peak size equal to the maximum it has grown to during the pruning period (every twelve hours).  If email attachment throughput becomes high enough, it can cause problems on a RepliGo Server computer that is running low on disk space.

One way to keep the size of this cache down is to lower the aging period of the cache to some value smaller than the default seven days.  Once cleared from the cache, these documents become unavailable to your BlackBerry users if they have kept email attachments in their device Inbox longer than the aging period.

To change the aging period, edit the “auto_age” entry in the following file in your RepliGo Server installation directory with your favorite text editor:

  webapps\docsrv\WEB-INF\config.properties

Once saved, restart RepliGo Server for the new value to take effect.

For example, if your users don’t need to have attachments available in their BlackBerry Inboxes for longer than a few days, you might change “auto_age = 7” to “auto_age = 3” which should more than halve the current size of your RepliGo Server cache.

Once you have decided on an appropriate aging period, you may want (but aren’t required) to start over with a “clean” cache database.  Be forewarned that this operation causes all cached documents to be deleted and no longer be available to your BlackBerry users.  This can be accomplished by pointing a web browser on RepliGo Server to the following address:

  http://repligo-server:4080/srvcore/janitor.m?op=clear

Where repligo-server is the hostname for your server, and any port number change that is appropriate if you did not take the default port number during installation.  The result should be a simple page that simply says “status: ok” if the operation was successful.  If your BlackBerry users still need access to those attachments still in their Inboxes, they can re-send the Email them to themselves to have RepliGo Server process them again.

Another solution, of course, is to install RepliGo Server on a volume with enough disk space.  One heuristic to determine how much space should be available is to estimate one to two times the total attachment throughput of your BES computer for the aging period, for document types supported by RepliGo Server.  If you are running RepliGo Server version 2.1 on Microsoft Exchange, the space taken will be lower, and the above estimate may be modified by the actual viewed attachment throughput rather than the total attachment throughput.

RepliGo Server version 2.0 and later have an administrative setting allowing the aging value to be easily set.