...
Steps in order to take a new snapshot.
Navigate into RDS → DB instances.
Select the database we want to take a snapshot from
Actions → Take Snapshot
We give a name of the snapshot and hit create.
Snapshot it will take approximately 15 minutes to finish.
Restore from a snapshot (Manual or Automated).
Navigate into RDS → Snapshots
Select the snapshot we want to restore
Actions → Restore Snapshot
We navigate into a new window where we must select the appropriate Security Groups and availability zones.
Restore DB instance.
Restore EFS
Take an EFS backup right away
In order to make an EFS backup right away we need to navigate into AWS Backup service.
We select the Create on-demand backup.
Resource type we select EFS
Select the File system ID
Backup window set to “Create backup now“
Transition to cold storage Never
Retention period Always
Backup vault set to Default
IAM role set to Default role
Set tags
Create on-demand backup.
Creating the backup will take approximately 2 hours for 1.4TB
...
In order to restore EFS we need to go into AWS Backup services and then into Backup vaults
Select the EFS we want to restore
Actions → Restore
We can select Full restore if we want the whole EFS or item-level restore if we want a specific directory from the EFS.
Restore to a new file system.
Restore role → Default role
Restore backup
This action will take approximately 15 minutes.
...
The steps to mount the EFS are:
In EFS dashboard we select the EFS that we have restored and we navigate into another page
we select Attach we chose the option Mount via DNS
Using the NFS client we select the appropriate command on which we paste into our EC2 console.
example of command
| Code Block | ||
|---|---|---|
| ||
sudo mount -t nfs4 -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport fs-.....:/ efs |
...
We edit config.php and we make the relevant changes:
we need to make sure the dbtype is the correct one in our case we have 'mariadb'
dbhost,dbname,dbuser,dbpass need to be of the newly restored DB instance.
wwwroot needs to change into the new URL eg https://dev.courses…
dataroot need to point to newly restored EFS with a path to moodledata
session_redis_host need to have the name of the redis for our application
Make sure Redis cache is correct in Moodle application
...
in Configured store instances table we edit redis_all and on the server input we put the one we have for our cloned website. eg dev-courses[…]amazonaws.com
In this area we need to put the Primary endpoint which we can found in our Amazon ElasticCache service
This is an important step as if it’s not configured then changes that are suppose to happen in cloned website will be done into the previous website because of redis caching.
...