Configuring EBS Snapshots for Amazon S3
- 31 May 2022
- 1 Minute to read
- Print
- DarkLight
- PDF
Configuring EBS Snapshots for Amazon S3
- Updated on 31 May 2022
- 1 Minute to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
The CTERA Portal includes a scheduled job that runs by default once every three hours. The job takes a snapshot of the CTERA EBS volume and sends it to Amazon S3. If desired, you can restore the CTERA database's EBS volume from a snapshot.
Restoring a CTERA Server EBS Volume from a Snapshot
Note
This procedure requires downtime.
To restore a CTERA server EBS volume from a snapshot:
- For each CTERA Portal instance you have installed on AWS, stop CTERA services, by doing the following:
- Open a SSH session to the CTERA Portal instance and log in as the admin user.
- Run the following command to stop the portal services:
portal stop
- Run the following command to access the linux shell:
elevate
- Restore the CTERA database EBS volume from a snapshot, by doing the following:
- Run the following command to list the available restore points (EBS snapshots):
portal-storage-util.sh display_snapshots
- To roll back to a snapshot, run the following command:
portal-storage-util.sh rollback_snapshot snapshot-id
Where snapshot-id is the ID of the snapshot you want to roll back.
EBS snapshot rollback begins.
- Run the following command to list the available restore points (EBS snapshots):
- For each CTERA Portal instance you installed on AWS, starting from the CTERA Portal database servers (that is, start from the main database and then proceed to the application servers), start the CTERA Portal services, by doing the following:
- Open an SSH session to the CTERA Portal instance and log in as the admin user.
- Run the following command to start the portal services:
portal start
Was this article helpful?