The VMware Blockchain cloning process is a two-step process. The first step requires creating a backup of an existing blockchain deployment, and the second step requires creating a clone from the newly saved backup.


A System Administrator must perform both of the cloning configuration steps.

The System Administrator must consider and plan for additional hardware and memory resources before backing up and cloning a blockchain deployment.

Backing Up a Blockchain State

You must start by identifying the blockchain deployment to clone. Select a Replica and Client node representing the blockchain state, back up the selected Replica nodes within the Replica Network and Client nodes within the Client node group.

Issue the WEDGE command to all the Replica nodes in the Replica Network. This operation stops all the Replica nodes from processing new commands at the same checkpoint based on the consensus protocol. After the command is executed, all the Replica nodes have the same state.

Cloning the Blockchain Deployment Backup

After a successful backup of the blockchain state, create a clone of the deployment environment. You must have all the licensing entitlements for the Replica and Client nodes in the cloned deployment.

Issue the restore command to clone a blockchain from the existing backup. The new blockchain starts from the same state as the original one. For security purposes, the cloned deployment environment does not share any private keys or certificates with the original blockchain. New private keys are created during the cloning of the blockchain deployment environment.

See the Understanding the Deployment Schema Parameters for Cloning topic in the Using and Managing VMware Blockchain guide for implementation steps.