Recovering from Checkpoints

In order to load the checkpoints and recover a Fulfillment Provisioning instance from them, the provadmin plugin exposes a load operation.

When executed, this operation will iterate over the declared checkpoint kinds and for each of them (if needed) load it and pass it to the interface responsible for effective recovery implementation.

Checkpoints should always be loaded before starting the Fulfillment Provisioning application’s client adapters. Checkpoints are always re-injected after the following operations. 

        provadmin stop fp
        provadmin remove fp
        provadmin install fp
        provadmin start fp

The provadmin command triggering recovery is called load. This command will stop flow controllers, wait for them to be stopped, load the checkpoints and eventually automatically restart flow controllers. 

provadmin load checkpoints [option1] [option2]...

Parameters associated to the load command.

Parameter

Description

nodename

The path to the Fulfillment Provisioning node.

cpnodename

The checkpoint node name.

types

The checkpoint types (aka kinds) that should be loaded. An empty value (default case) means that every checkpoint kind should be loaded (except if the interface does not allow it). Each checkpoint kind owns a priority that will define the order in which checkpoint kinds will be loaded.

chunkSize

This parameter defines the maximum number of checkpoints that should be iterated before the low level transaction is committed and another one started to continue loading checkpoints. The default setting is 500.

autoStartFC

If set to true, flow controller instances will be automatically started when all checkpoints have been loaded so that orders are resumed immediately.