You can automate the backing up of transaction journal files as they are closed, to ensure that this operation is not neglected. (The automating of the journal close action is ignored and unwanted journal files are removed when the
When archival recovery is enabled, use the
Copy, which uses the operating system to copy the file to the archive directory
CopyAndCompress, which programmatically creates a compressed copy of the file in the archive directory (using ZLIB compression mechanisms)
Move, which uses the operating system to move the file to the archive directory
MoveAndCompress, which programmatically creates a compressed copy of the file in the archive directory (using ZLIB compression mechanisms) and then removes it
None, which takes no action
The journal close actions operate in conjunction with the
When you set the
The number of the abort journal is not incremented. It changes based upon transaction activity, to reflect the oldest journal required for transaction abort or the restart recovery point established by the last checkpoint (whichever is farthest back in time). If there is no transaction activity, the abort journal number is not incremented.
This is a journal file backup mechanism, which is independent of the journal file shipping across a network connection used in conjunction with a hot standby server (documented in "Sample Usage Scenarios" in the Synchronized Database Service (SDS) white paper on the JADE Web site at https://www.jadeworld.com/developer-center/resource-library/white-papers).