[BUG] inconsitent reporting and logging for backup and restore

[duncdrum]

What happens

While debugging the recent backup/restore options i noticed a couple of minor inconsistencies and bugs regarding how exist treats different backup options.

For server-side backups I used:

• the GUI that ships with the Dashboard
  clients side:
• java java org.exist.start.Main backup -ouri=xmldb… (via docker exec)
• xquery (system:export('/tmp', xs:boolean(0), xs:boolean(0)) )

The server-side backup writes to exist.log

INFO  (TriggerSystemTask.java [eval]:85) - Triggering SystemTask: org.exist.storage.ConsistencyCheckTask 

05 Oct 2021 13:14:39,220 [qtp260620222-28] INFO  (ConsistencyCheckTask.java [execute]:151) - Starting consistency check... 

05 Oct 2021 13:14:39,397 [qtp260620222-28] INFO  (ConsistencyCheckTask.java [execute]:174) - Finished consistency check 

05 Oct 2021 13:14:39,397 [qtp260620222-28] INFO  (ConsistencyCheckTask.java [execute]:178) - Starting backup... 

05 Oct 2021 13:14:40,721 [qtp260620222-28] INFO  (ConsistencyCheckTask.java [execute]:185) - Created backup to file: /exist/

etc/../data/export/full20211005-1314 

05 Oct 2021 13:14:40,722 [qtp260620222-28] INFO  (ConsistencyCheckTask.java [execute]:188) - Finished backup 

but the backup.log is empty

client-side

both exist.log and backup.log are empty. This is on successful backups, there is a detailed report returned from system:export()

What should happen

logging the start and finish of a backup or restore, including the filename as a system event makes sense. We have a backup.log so lets use it. From what i can see nothing seem to write into this log file which is a bug.

Backup is separate from consistency check, which seems responsible for server-side backups writing to exist.log on non-container instances i think we can put this info into the backup.log.

HOwever, on docker we should modify the applied log2j config file, so that backups evens appear in the exist.log as its the the log directly accessible by the docker daemon or other orchestrators.

see eXist-db/dashboard#210
see #4052

Context (please always complete the following information):

• OS: docker
• eXist-db version: 5.4.0-SNAPSHOT , Fusion-DB 1.0.0-SNAPSHOT

Additional context

• How is eXist-db installed? docker
• Any custom changes in e.g. conf.xml? No