Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Infrastructure as Code 
    Implement infrastructure as code practices to manage and provision your deployment environments. This ensures consistency and allows you to reproduce environments easily, reducing the risk of configuration drift.

  2. Log Management 
    Keep detailed logs of your deployment processes and system activities. Logs are crucial for troubleshooting issues, monitoring system performance, and maintaining compliance with regulatory requirements.


Backups

...

  1. Data backup

...

  1. In order to keep the data safe, especially the most critical ones, it is a good practice to make them redundant and store them in multiple places, also leveraging the different storage solutions provided by EWC. As examples: data could be synced across multiple volumes attached to different VMs; data could be also saved on the object storage in S3 buckets; where needed it is also possible to replicate on multiple clouds within EWC (e.g. at both ECMWF and EUMETSAT clouds); finally a copy of the data could also be stored externally to EWC, e.g. in local premises or other infrastructure providers. 
  2. Applications backup
    When it is required to have a resilient and faults tolerant application, it is usually chosen a design and deployment that allows to run it in a high availability mode so that if an instance is down, the overall service is not impacted and the application remains available to the end users. In other cases, where it is not possible to implement an active high availability setup, it is at least advisable to take a regular backup of the application and relevant data in order to make it possible a quick service restoration in case of outage or redeployment.   
  3. Virtual Machines backup
    Beside the above mentioned backups, the users of the EWC has the possibility to take a backup of the deployed Virtual Machines by following the steps described in VM Backups in Morpheus .
    However the VM backup is just an additional complementary tool to create a backup, but it shall not be the primary and neither the only one to rely on. It is indeed meant to be used in conjunction with data/application backups and automated deployment.

...

Remove VMs

  • Remove unused VMs

...