2.2.6.3. mijin Catapult(v.2) periodic backup of nodes

This chapter describes the procedure for backing up data on a node of mijin Catapult(v.2) on AWS.
By backing up your nodes, you can recover from the blockchain data in the event of a region failure, for example.
creation-day:

Aug. 1, 2022

update date:

September 13, 2022

2.2.6.3.1. About AWS Backup Service

Easily back up the mijin Catapult(v.2) running on your EC2 instance Use ‘AWS Backup’ to perform backups on a regular basis.
To learn more about AWS Backup, please refer to the following
https://docs.aws.amazon.com/ja_jp/aws-backup/latest/devguide/whatisbackup.html

2.2.6.3.2. Creating a Backup Plan

Click on Services on the top tab.
Click Storage.
Click on the ‘AWS Backup’ service.
 ../../_images/aws_backup1.en.png
Click Create Backup plan
 ../../_images/aws_backup2.en.png
[Startup Options]
Check Build a new plan.
Describe the Backup plan name.
[Backup Rule Settings]
Describe the Backup rule name.
Check Customize backup window.
Sets the start time of the backup. (Note that this should be set in UTC time.)
Specify any region in the copy for the copy destination. *1
Click on ‘Create plan’
 ../../_images/aws_backup3.en.png
[General]
Enter any name for the Resource assignment name.
[Resource Selection]
Check Include specific resource types.
Select Resource type EC2
Instance IDs Here we select the PEER3 node.
Click on ‘Assign resources’
 ../../_images/aws_backup4.en.png

Note

Although you can specify multiple nodes (EC2 instances) to be backed up
mijin Catapult(v.2) can recover everything from blockchain data on a single node, so regular backups are no problem if only one node is backed up, thus reducing costs.
*1 If the destination region is the same region, it can be recovered at Restore from a backed-up snapshot.
Separate regions can also be used for disaster recovery and other anti-disaster measures.