VMware Blockchain data archiving is an optional feature that can be enabled during the deployment configuration.

Data archiving is performed using a Full Copy Client node. The Full Copy Client node’s role is to receive data stored on the blockchain deployment and save it in the ObjectStore. Full Copy Client nodes do not participate in the BFT consensus process.

The data archiving is done in a trusted manner. Each Full Copy Client node has its own set of private and public TLS Keys. The public key of each Full Copy Client node is known to the ReplicaNetwork. When a command is executed on the Replica Network, a key-value pair is generated. This key-value pair is sent to the Full Copy Client node over a TLS connection and written into the ObjectStore.

The Full Copy Client node interacts with the ObjectStore using the standard S3 APIs.

The Full Copy Client node is stateless, which means it does not contain data, and the data is stored in the connected ObjectStore. If the Full Copy Client node goes offline temporarily, there is no data loss in the case of a hardware or networking failure. A System Administrator must set up a new Full Copy Client node and connect it to the ObjectStore. When the connection to the new Full Copy Client node is established, the ObjectStore starts to receive data from the Replica Network until all the data is synchronized with the Replica Network.

For implementation steps, see the Understanding the Deployment Schema Parameters topic and the Full Copy Client Node Parameters section in the Using and Managing VMware Blockchain guide.