Data Recovery Service Editor

Data Recovery Settings

All but the first of these is a read-only status property, and include the following:

Service Enabled

Defaults to true, to enable SRAM support via this service. If a JACE with onboard SRAM (e.g. JACE-6E or JACE-3E), you can set this to false to disable SRAM support—in which case it relies on its installed backup battery and its PowerMonitorService to preserve station data upon loss of power. (If an SRAM option card-equipped JACE, you can simply remove the SRAM option card and uninstall the platDataRecovery software module).
Service Status

The current status of the DataRecoveryService, which is typically “Ready”. Other states include “Starting”, “Configuring”, “Replaying”, “Saving”, “Stopping”, “Stopped”, “Fault” and “Unknown”.
Last Station Save Time

Reflects the last time a station save occurred (config.bog written to flash memory). This save may (or may not) have occurred as a result of the DataRecoveryService.
Last Station Save Successful

Boolean that reflects if last station save attempt was successful, as either “true” or “false”. This save may (or may not) have occurred as a result of the DataRecoveryService.

Note in the case of a newly-created DataRecoveryService, this is “false” until the next save occurs.
Persistent Storage Size

Reflects the total size of all the “flushed to flash” data block files (“.drdb” files) that exist in the station’s !/dataRecovery folder, in KB. Initially, this will be 0, until the first SRAM block flushes to flash. It will then increment by that KB amount for each subsequent SRAM block flushed.

Note this value is continually compared to the “Persistent Capacity” property in the Blocks Configuration property section.

Blocks Configuration

These status properties include the following:

Total Size

Reflects, in bytes, the total amount of SRAM buffer memory available to the service. For example, this is “524288” for the 512 KB SRAM option card.
Number of Data Recovery Blocks

Reflects the number of data block partitions of SRAM used, for example, 3.
Active Directory

Reflects the directory used in SRAM for the active data block.
Persistent Directory

Reflects the full flash file directory path used to store flushed “.drdb” files, which equates to: !/dataRecovery
Full Policy

Reflects the current policy when an SRAM data block becomes full (currently “Flush”).
Persistent Capacity

Reflects the size limit, in KB, for the total of all “flushed to flash” data block files (“.drdb” files). If this limit is exceeded (see property “Persistent Storage Size”), the service automatically triggers a station save operation. For related details see Station save effects.

Data Recovery Blocks

This area provides expandable bar graphs for each of the SRAM buffer data blocks, to visually represent the current amount of used space, overhead space, and available free space, along with numerical values.

By default, the currently active SRAM block is expanded, showing a bar graph of current buffer usage.

Figure 2. Example SRAM data block, show both states “Active” and “Flushing”

Figure 2 shows an example active SRAM block first near full, then “flushing” momentarily to flash—an operation that lasts only a second or two. Another SRAM block becomes active when this happens, and it is used until it fills and needs to flush to flash.

Above the bar graph of each block, its Status is described, typically as either: “Active”, “Idle”, or sometimes “Flushing”, with other states “Purging”, “Awaiting Idle”, “Flush Queued”, “Defragmenting”, “Reserved”, “Fail”, and “Unknown”.

Below the bar graph of each block, numerical amounts display, in bytes, for its total Capacity, currently Used space, calculated Overhead Space, and available Free Space.