You can restore a failed Client node from a full backup data. The Client node backup should be within the Client node group.

Prerequisites

  • Verify that the backup was created from a healthy Client node. See Back-Up Client Node on vSphere.

  • Verify that you have captured the IP addresses of all the Client node VMs and have access to them. You can find the information in the VMware Blockchain Orchestrator descriptor file.

Procedure

  1. SSH into the VMware Blockchain Orchestrator appliance.
  2. Enter the login credentials for the blockchain user account.
  3. Navigate to the /home/blockchain directory.
  4. Stop all the applications that invoke connection requests from the Daml Ledger.
  5. Stop the Client node components. 
    curl -X POST 127.0.0.1:8546/api/node/management?action=stop
  6. Change the owner of the /mnt/data/db to VMware Blockchain user in the new Client node. 
    sudo chown vmbc:users /mnt/data
  7. Remove any contents of the database directory. 
    sudo rm -rf /mnt/data/db/*
  8. For small database, copy the backup data from the old Client node to the new Client node.
    Name of the backup should end with .tar.gz.
    1. Run the rysync command on the old Client node. 
      rsync -avh <BackupDir> <destination>
    2. Run the rysync command on the new Client node directory. 
      # Run this rsync command on the OLD CLIENT. For this example, it is assumed that when the old client's backup was taken,
# it was tar-gzipped to /mnt/data/db-backup.tar.gz.
 
rsync -avh /mnt/data/db-backup.tar.gz [email protected]:/mnt/data
  9. For large database, create a password.txt file with the VMware Blockchain user password.
    The user password is available in the output files generated by the initial deployment operation.
    1. Run the command on the old Client node to copy the backup tar to the new Client node. 
      sudo nohup sshpass -f ./password.txt scp -v -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -r /mnt/data/db-backup.tar.gz [email protected]:/mnt/data &
    2. Remove the password file after the copying operation is done.
  10. Untar the backup data in the new Client node. 
    #For small data
sudo tar xvzpf <BackupName> --directory /
#For large data
cd /mnt/data
sudo nohup tar xvzpf db-backup.tar.gz --directory . &
sudo tail -f nohup.out

    The large data untar process command might take some time.

  11. Start all the Client node components. 
    curl -X POST 127.0.0.1:8546/api/node/management?action=start

What to do next

You can also restore the Client node from the point-in-time backup data. See Restore Client Node from Point-In-Time Backup on vSphere.

After the restore, you can manage your backup configuration. See Manage Client Node Backup on vSphere.