How to prevent the built-in H2 database from growing excessively large
Posted by John Villanueva on 24 May 2018 06:40 PM
As pointed out in the article "Slow startup and other performance issues due to large database", if the built-in H2 database used by MFT Server to store server configuration data grows excessively large, it can cause performance issues and can even prevent MFT Server from starting. While that same article outlines the steps to compact an overgrown database, it would help to know how to prevent the database from growing too large in the first place. This article addresses that.
First of all, you need to be aware of the items that enable the database to grow. Here are some of them:
Now, here are the things you can do prevent these items from flooding the database:
For the Trigger execution history
For the administrative events log
Go to "Settings > Manager Service > Logs" and enable "Clear records older than" option and set it to 1 day.
For the AS2 messages
AS2 messages can be purged using the js-as2purge command line utility.
Other things you can do
Check if you have set any domain logging to database (Logging > Service). You can use Log to File instead (see http://files.jscape.com/secureftpserver/docs/index.html?settingloggingpreferences.htm)
Check if you have enabled verbose logging as well (Logging > Settings). Disable this if so.
Refer to this for details: