Dynamic Transaction Point Settings

Datalight Reliance™ Nitro is a two state file system, comprised of the working state and the committed state. Original data (the committed state) is preserved until the new data (the working state) is written and a transaction point is performed. During operation on the working state, all file system modifications - including changes to directories, files and metadata - are stored on an area of the media that is currently unused and does not contain committed state data. The possibility of corruption is eliminated because the data of the new transaction is written to an unused portion of the media. Writing to an unused portion of the media allows the previous state of the file system to be untouched. Valid data from the previous transaction is always available. Transaction points are run-time configurable using Dynamic Transaction Point Settings. Setting options include automatic, timed or application controlled options see use case examples in table below.



  Use Cases Requirement Solution
Automatic Handheld Scanner Transact each time
an item is scanned

Transact on fileclose 
“timed” will not work; rate of
scans is unpredictable 

Timed Crash Recorder
"Black Box"
Government req. that
only 16 sec. of data
can be at risk

Transact every 16 seconds 
“automatic” would not
guarantee req; “timed” at
smaller intervals may affect

Boot Image 
Several files are
dependent on each
other and must be
updated at the same
Ensure application will
instruct Reliance to transact
when all conditions are met