Implementing cluster backup solution to build resilient cloud architecture
Bui, Minh (2020)
Bui, Minh
2020
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2020060417179
https://urn.fi/URN:NBN:fi:amk-2020060417179
Tiivistelmä
This thesis project aimed to implement a backup solution in the cloud architecture of the client company - Solibri. The company provides out-of-the-box tools for model validation, compliance control, design process coordination, design review, analysis and rules checking. With Solibri products, every party involve in a construction project can build, view and check errors of the building models blueprint.
The company is in the progress of migrating their desktop application to become completely cloud native, and in the long-term to a Software-as-a-Service product. To build a stable infrastructure that is resilient against disaster scenarios, the author of this report oversaw the implementation of a back-up solution called Velero into the running cluster. The criteria to implement Velero was found by careful studying documentation from Velero website along with learning about the company’s current cloud infrastructure. One criteria was a persistent storage location is needed for backups to reside. Such a resource was partitioned from the cloud provider Amazon Web Service. Afterwards, the backup solution was configured to connected to a partitioned storage location, deployed into the cluster, and created schedule backups for several resources.
Using Kubernetes as a cluster orchestrator, the information about the deployed Velero solution can be viewed from the command line. Next, the author checked to see if the backups are in place. The scheduled backups can be viewed from AWS console along with retrieved from the command line. The results from these tests showed that the backup solution was integrated into the cluster and creating schedule backups as needed. Since this project is limited to only integrating a backup solution, further steps are still needed to complete the disaster recovery pipeline which should be addressed in future projects. This report can act as documentation on the procedure and knowledge needed to implement this backup tool.
The company is in the progress of migrating their desktop application to become completely cloud native, and in the long-term to a Software-as-a-Service product. To build a stable infrastructure that is resilient against disaster scenarios, the author of this report oversaw the implementation of a back-up solution called Velero into the running cluster. The criteria to implement Velero was found by careful studying documentation from Velero website along with learning about the company’s current cloud infrastructure. One criteria was a persistent storage location is needed for backups to reside. Such a resource was partitioned from the cloud provider Amazon Web Service. Afterwards, the backup solution was configured to connected to a partitioned storage location, deployed into the cluster, and created schedule backups for several resources.
Using Kubernetes as a cluster orchestrator, the information about the deployed Velero solution can be viewed from the command line. Next, the author checked to see if the backups are in place. The scheduled backups can be viewed from AWS console along with retrieved from the command line. The results from these tests showed that the backup solution was integrated into the cluster and creating schedule backups as needed. Since this project is limited to only integrating a backup solution, further steps are still needed to complete the disaster recovery pipeline which should be addressed in future projects. This report can act as documentation on the procedure and knowledge needed to implement this backup tool.