Dear silverspr and jllort , thank you for your quick answer.
@jllort, while examining the script mentioned by silverspr to execute as a cron job the export task (see link on his post), I noted the following lines:
// Configuration parameters
String token = DbSessionManager.getInstance().getSystemToken();
String LOG_FILE_NAME = "CrontabRepositoryExporter";
so I thought that such script, once uploaded as a cronjob for openkm, could produce a log report at each execution.
Now, to answer your question and describe the scenario I have in mind, I want to understand if it is possible to create a backup of all documents in a readable format, automatically.
If the export function, either manually or cron-job activated, every time rewrites the entire tree of docs, this may not be a viable option, at least when managing thousands or hundred of thousand documents (not mentioning the fact that right now the repository on my system is on a zfs file system with automated snapshots running hourly, daily, weekly, monthly and yearly).
Ideally if the export was executed onto a previously used directory, it would be great if existing files were just skipped.
As for the log management, is the log mentioned in the above script the same log that you are pointing me out to in $TOMCAT_HOME/logs named RepositoryExportXXXXX.log ?
I would guess no, since the log mentioned in the script should be the log of the cron job, while the log that you are referring to is the log of the export function.
In both cases, is there a rotation policy implemented for all the logs produced?
So, to summarize, the scenario is to understand how to automate a backup function of all the documents stored in openkm, in a readable format (if we include metadata and history, that is great).
I wish that export function could fit the purpose, but it has to be found out if an "incremental" export is possible or not.
Thank you in advance for your support.
Rosario