Forums

We've updated our backup routines to ensure all journal files are copied. We record the current journal prior to the start of the backup and again at the end. We then look to backup all the journals to the backup disk. However the systems are configured to Move And Compress journals when they are closed by Jade. We've noticed that sometimes, our archival of the journal and the internal archiving is conflicting. e.g. the journal has been archived by Jade before we copy it to the backup or Jade is unable to archive the journal as we are archiving it.

I can't see any notifications that occur when Jade archives the journal or any way of pausing the Jade archival process.

Short of writing our own journal archival process to run as a server task, has anyone found a solution to this?

Hi Torrie,
I recommend taking a look at the backup functionality as provided by the CnDatabaseAdmin class in CardSchema. Our backup routines are a modified version of that, and it handles the problem you have mentioned. I've just had a quick look at the code and it seems the CnDatabaseAdmin::backupLogFiles method caters for that problem.

Regards,
Allistar.