Requirement
To guarantee the AC4 cloud environments and their related resources are securely backed up and can be efficiently restored with minimal downtime in the event of any failure.
Scope of Backup & Restoration
The scope of restoration depends on the type of failure and its frequency. Velero tools are essential for backing up and restoring Kubernetes objects, playing a crucial role in establishing a dependable disaster recovery strategy.
Complete AKS cluster (Namespace with PVC) backup
Selected resources backup (e.g., PVC, Namespace)
AC4 cloud backend and log database backup
Restoration of selected resources
Restoration of AC4 cloud backend and log database
Policy Statements
All systems and databases must be preserved for AKS Cluster and applications to be completely recoverable, utilizing a combination of namespace duplicates, incremental backups, and database backups.
The volatility of data determines the frequency of backups; the retention period is determined by the criticality of data, with a minimum retention period of 7 days.
It is essential to securely store at least one fully recoverable version off-site, in a different Azure region, or off-site storage.
Backup documentation should clearly outline all critical data and necessary support items for recovery. Restoration documentation should encompass procedures for both individual system/application failures and total data center disaster scenarios.
It is crucial to regularly review and update backup and recovery documentation to align with new technology and business changes.
Annual testing of recovery procedures is imperative to ensure effectiveness.
Backup Points
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:
Storage account:
accloudbackupswusAccount type: BlobStorage
Primary Location: West US, Secondary Location: East US
Backup Data storage in below containers or respective Customer
Backup Naming Convention
Backups from customer environments follow this naming convention:
daily<<customername>>prod_YYYYMMDDHHmmSS
Object\Namespace Included
Following the namespace and database configured part of the backup
AC4 Production
AC4 NonProduction
Production PVC
Non-Production PVC
Non Production
Production Database
Non-Production Database
Monitoring tool
EFK(log View) tool
Ingress Controller
Backup Log
The backup log includes details about all critical data, namespace, and necessary support items for recovery, ensuring the entire process is documented and reviewed regularly.
Database Backup Procedure
Azure provides automated backups for MySQL Flexible Server.
Backup retention can be configured up to 35 days (default is 7 days).
Diagram Explanation
The attached diagrams illustrate the backup and restore process for an application database in the Azure Cloud environment with Adeptia Connect 4.x. This setup ensures data integrity, business continuity, risk mitigation, and operational efficiency by enabling quick recovery from data-related incidents.
This document outlines a comprehensive backup and restore strategy for AC4 cloud environments, ensuring minimal downtime and efficient recovery in case of failures.