Manage Transaction Log Journal Files

AMPS provides the following modules for managing journal files and loads these modules by default:

Module Name	Does
amps-action-do-archive-journal	Archives journal files that are older than a specified age to the JournalArchiveDirectory specified for the transaction log. This action marks files to be archived and then returns.
amps-action-do-compress-journal	Compresses journal files that are older than a specified age. This action marks files to be compressed and then returns.
amps-action-do-remove-journal	Deletes journal files that are older than a specified age. This action marks files to be deleted and then returns. If a journal file is currently in use, it will be removed when it is no longer in use.

AMPS will only remove journal files that are no longer needed by the instance. AMPS ensures that all replays from a journal file are complete, all queue messages in that journal file have been delivered (and acknowledged, if required), and all messages from a journal file have been successfully replicated before removing the file.

Journal files that have been compressed or archived (or both) are still part of the transaction log. AMPS will compress and archive journal files that have undelivered queue messages, or that have not yet been fully replicated, and so on.

Each of these modules requires an Age parameter that specifies the age of the journal files to process.

Parameter

Description

Age (required)

Specifies the age of files to process. The module processes any file older than the specified Age. For example, when the Age is 5d, only files that have not been written to for longer than 5 days will be processed by the module. AMPS does not remove the current journal file or files that are being used for replay, files that are being used for replication or files that contain unacknowledged and unexpired messages in a queue; even if the file is older than the Age parameter. AMPS does not allow gaps in the journal files, so it will only remove a given file if all previous files have been removed. AMPS can compress and archive journal files that are still in use since compressed or archived journal files are part of the transaction log and AMPS will replay messages from these files. There is no default for this parameter.

These modules do not add any variables to the AMPS context.