If the OS is restored with the snapshot function of AWS, perform the following procedure.
Set the value of the tag "fujitsu.pclswr.is_recovery_target" of the instance of the cluster node to false.
Restore a snapshot of a volume (EBS) attached to an instance.
For information about restoring snapshots and attaching EBS volumes, see the official AWS documentation.
Stop the instance of the cluster node. Note the integer value and instance ID that identifies the cluster node, which is the value of the cluster node instance tag "fujitsu.pclswr.id".
Create an AMI for the instance of the cluster node.
Terminate the instance that you stopped in step 3.
Create an instance according to "A.2.3.1 Creating Cluster Node Instance" from the AMI created in step 4. At this time, set the value of the cluster node instance tag "fujitsu.pclswr.id" to an integer value that identifies the cluster node in step 3. Also note the instance ID of the instance you created.
Add the instance you created to the ELB's target group.
Change the instance ID of the CloudWatch alarm from the instance ID in Step 3 to the instance ID in Step 6.Determine what to change by the integer value that identifies the cluster node at the end of the alarm name. For more information about alarm names, see "A.2.4.3 Configuring CloudWatch Alarm".
Modifies the items of a eligible instance registered to the table "Fujitsu-Pclswr-DB-Switcher" in Amazon DynamoDB. The items to be modified are checked from the items "SystemID" and "InstanceID". Change the value of the item "InstanceID" from the instance ID in step 3 to the instance ID in step 6. For more information about the items, see "A.2.4.4 Configuring Amazon DynamoDB".
Verify that the tag "fujitsu.pclswr.is_recovery_target" value of the instance you created in step 6 is true.
See
For instructions about using the AWS Management Console, see the official AWS documentation.
Note
In a cluster system that uses the smart workload recovery feature of PRIMECLUSTER, you cannot restore using the snapshot function while the business is still in operation.
Synchronize with EFS if restoring with snapshot.
