DB/Data Management
RMS Journaling
Product Overview
RMS Journaling is a tool that helps to protect your data from being lost or becoming inconsistent.
Journaling is applied on a file-by-file basis, not on an application basis.
You can use RMS Journaling for any RMS (Record Management Services) file that is updated. You can use any of the journaling types with sequential, relative, or Prolog 3 indexed file organizations.
Features
RMS Journaling provides the following three types of journaling: after-image, before-image, and recovery journaling. These journaling products protect RMS file data from becoming lost or inconsistent. RMS Journaling for OpenVMS provides the following three methods of journaling:
- After-image (AI) journaling allows you to redo a series of modifications to a file. This type of journaling helps recover lost or corrupted files. After-image recovery restores the contents of the file from the point of the latest backup copy of that file.
- Before-image (BI) journaling allows you to undo a series of modifications to a file. This type of journaling returns the file to a previous known state. This is useful when a file is updated with erroneous data.
- Recovery unit (RU) journaling helps maintain transaction integrity, where a transaction consists of a group of related operations that must be atomic. That is, either all of the operations complete in their entirety, or none of the operations complete. This type of journaling helps prevent data from becoming inconsistent due to the incomplete execution of a transaction.
Journaling is applied on a file-by-file basis. A file can be marked for AI, BI, or RU journaling, or any combination of these methods. Within a given application, any combination of journaling methods can be used.
RMS Journaling for OpenVMS stores the information necessary for data recovery in files known as journals. Multiple files can use the same journal.
You cannot use RMS Journaling for:
-
File operations that do not use RMS services
-
RMS files that are rewritten with a new version number (such as text files that are modified by a text editor) rather than updated in place
Licensing
Integrity: HAOE, per active socket.Alpha: Alpha-LP
Documentation
Documents and manuals related to this product
Downloads
Useful files related to the product, such as tools or additional materials.
Get a license
Most non-Open Source products require a valid license to operate. If you need to get a license for a product or OpenVMS itself, please look at the page describing the possible options.
Migrate to x86
OpenVMS is now available for x86/64 architecture, offering a reliable and up-to-date option to run your software in the future.
We are ready to give you all the information needed to evaluate the migration project, move your solutions to x86, and start using them in a working environment.