Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Backup Component | Backup Method | Backup Performed By | Recovery Region | Backup/Retention Frequency | Retention Period |
Database | Azure Database | Azure | Geo Redundant | Point In Time | 7 Days |
Adeptia Connect Namespace | Using Velero backup, recover the entire namespace that includes components and objects of the application deployment such as PVC, ConfigMap, and Certificates. | Adeptia (Velero Scheduled Job) | Depend on Cluster | Every 8 hours | 14 Days |
Ingress | Using Velero backup, recover the entire namespace that includes components and objects of the application deployment (such as PVC, ConfigMap, Certificate, etc.). | Adeptia (Velero Scheduled Job) | Depend on Cluster | Every 8 hours | 14 Days |
Logs (EFK) Namespace | Using Velero backup, recover the entire namespace that includes components and objects of the application deployment (such as PVC, ConfigMap, Certificate, etc.). | Adeptia (Velero Scheduled Job) | Depend on Cluster | Every 8 hours | 14 Days |
Monitoring (Grafana) Namespace | Using Velero backup, recover the entire namespace that includes components and objects of the application deployment (such as PVC, ConfigMap, Certificate, etc.). | Adeptia (Velero Scheduled Job) | Depend on Cluster | Every 8 hours | 14 Days |
Restore\Recovery Points
Recovery Use Case | Recovery Method | Performed By | Recovery Region | Restore Duration |
Namespace is accidentally lost | Using Velero backup, recover the entire namespace that includes components and objects of the application deployment (such as PVC, ConfigMap, Certificate, etc.). | Adeptia | The recovery region will remain the same if the existing cluster is running smoothly. If a new cluster needs to be set up in a different region, the recovery process will be carried out in that new region. | 2-4 hours |
PVC Failed | Using Velero backup PVC object will be resorted | Adeptia | Recovery will remain in the same region if the existing cluster is operational. If a new cluster needs to be set up in a different region, recovery operations will be conducted in that new region. | 2-4 hours |
Kubernetes Failed | Connectria/Azure | 1-2 days(As per Connectria) | ||
Database/Server Failed or accidentally lost | Restore the database from the database backup and verify the connectivity of the application. | Adeptia/Connectria | 2-4 hours | |
Logs (EFK) Namespace | Using Velero backup, recover the entire namespace that includes components and objects of the application deployment (such as PVC, ConfigMap, Certificate, etc.). | Adeptia | Recovery will remain in the same region if the existing cluster is operational. If a new cluster needs to be set up in a different region, recovery operations will be conducted in that new region. | 2-4 hours |
Monitoring (Grafana) Namespace | Using Velero backup, recover the entire namespace that includes components and objects of the application deployment (such as PVC, ConfigMap, Certificate, etc.). | Adeptia | Recovery will remain in the same region if the existing cluster is operational. If a new cluster needs to be set up in a different region, recovery operations will be conducted in that new region. | 2-4 hours |
Backup Location
Backups are stored in the following locations for restoration when needed:
...
Backups from customer environments follow this naming convention:
daily<<customername>>prod_YYYYMMDDHHmmSS
Object\Namespace Included
...