2.2.7.1. Restore from a backed-up snapshot

This chapter describes the procedure for restoring data on a mijin Catapult (v.2) node on AWS from a backup from a Snapshot obtained with AWS Backup.

Note

If you want to erase the blockchain data and restore it from another node instead of from Snaoshot, you can use mijin Catapult(v.2) node resynchronization.
creation-day:

Aug. 1, 2022

update date:

September 14, 2022

2.2.7.1.1. Stop the node completely

Blockchain data.
Here, we stop at PEER node 3 as an example.

Login to PEER node 3.

mijin Catapult(v.2) EC2 instance login how to and log in to the node.
Note the availability zone where the volume is located.
Make sure it is GP3
 ../../../_images/aws_restore1.en.png
mijin Catapult(v.2) and stop the EC2 instance.
sudo su - catapult
cd mijin-catapult-package/package/peer/catapult/
docker-compose down
docker-compose ps
exit
sudo shutdown -h now
../../../_images/aws_ebs8.png

2.2.7.1.2. Detach volume of stopped PEER node

Remove the volume attached to the node.
Select the volume from PEER node 3 again.
 ../../../_images/aws_ebs17.en.png
From Volume, click on ‘Detach volume’ and press OK on the screen that pops up.
 ../../../_images/aws_ebs18.en.png

2.2.7.1.3. Create a volume from an AWS Backup Snapshot

For AWS Backup, select a Snapshot of mijin data from AMI.
Skip this step if you want to select a manually acquired Snapshot.
 ../../../_images/aws_restore2.en.png
Click on ‘Create volume from snapshot’.
 ../../../_images/aws_restore3.en.png
Select volume type gp3
Select availability zone Stop the node completely.
 ../../../_images/aws_restore4.en.png

2.2.7.1.4. Attach the restored volume to the PEER node

Attach the encrypted volume to the node
Select the encrypted volume and click ‘Attach volume’.
 ../../../_images/aws_ebs19.en.png
Select instance PEER node 3 and specify the same path as the detached volume.
Click on ‘Attach volume.’
 ../../../_images/aws_ebs20.en.png
Verify that the restored volume is attached.
 ../../../_images/aws_ebs21.en.png

2.2.7.1.5. Start up a stopped PEER node

Start up the stopped node and start up mijin Catapult(v.2) as well.
From the list of instances, check PEER node 3 and click ‘Start Instance’.
 ../../../_images/aws_ebs22.en.png

Login to PEER node 3.

mijin Catapult(v.2) EC2 instance login how to and log in to the node.
Make sure the disk is mounted, and start up mijin Catapult(v.2).
df -h
sudo su - catapult
cd mijin-catapult-package/package/peer/catapult/
rm -rf /mnt/mijin/blocks/data/*.lock
docker-compose up -d
docker-compose ps
../../../_images/aws_ebs23.png