File backend

The file backend maps a checkpoint to its own file. Each file may, contain several records. For performance reasons, it is not recommended to use more than one record per checkpoint.

  • Performance of the file backend is directly related to the disk performance. Faster disks can improve this performance somewhat.

  • The file backend is not secured : in normal circumstances, whenever the Fulfillment Provisioning application crashes, all data should be flushed by the OS to checkpoint files. However, it would not withstand a hardware crash or a kernel panic. Data may be lost and/or corrupted in this case.

In the file backend a checkpoint is stored in a file located at: 

[checkpointDirectory]/[checkpointNodename]/[checkpointKind]/[checkpointKey].kcp

For instance if the file backend is configured to store checkpoints in the checkpoints directory, a checkpoint with key 1100084599944953805, kind chk (standard service order checkpoints) belonging to node DefaultNodeName is stored at this location: 

checkpoints/DefaultNodeName/chk/1100084599944953805.kcp
The file backend handles corrupted checkpoints by renaming the checkpoint with a specific "cor" extension. A checkpoint file which was initially called : 
checkpoints/DefaultNodeName/chk/1100084599944953805.kcp
is renamed (if found corrupted) to : 
checkpoints/DefaultNodeName/chk/1100084599944953805.cor