Skip to content
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.

Latest commit

 

History

History
40 lines (30 loc) · 1.91 KB

backup_sla.md

File metadata and controls

40 lines (30 loc) · 1.91 KB

Backup Service Level Agreement (SLA)

Backup Coverage

Folloing services will be backed up using ansible playbook

  • Web Service with Nginx - covered by ansible repository
  • App Service (Agama) - covered by ansible repository
  • Database services (InfluxDB, MySQL) - Daily back up
  • DNS services (Bind9) - covered by ansible repository
  • Logging services (Grafana, exporters) - covered by ansible repository

RPO

The backup will be updated to the point where the database is no more than 1 day in the past.

Versioning and Retention

Database Backup Schedule (Time in EET)

Day Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Local Backup 1:00 1:00 1:00 1:00 1:00 1:00 1:00
Full Backup 1:30
Increment Backup 1:30 1:30 1:30 1:30 1:30 1:30

Local backup is made once a day at 1:00 AM(EET), includeing Influxdb, MySQL
Old back up will be deleted after the new one is made.

Full backup is made every Sunday at 1:30 AM(EET), including Influxdb, MySQL.

Incremental backup is made at 1:30 AM(EET) on Mon - Sat, including Influxdb, MySQL.

All the backup will be retained for 4 weeks/28 days.
Only 2 versions can be stored at the same time.
The oldest backup will be deleted at 2:00 AM(EET) on 28th day of every month.

Usability checks

Usability of backups must be checked before implemented on the real production infrastacture. The test will be simulated on virtual environment every Monday.

Restoratoin criteria

Backup will be restored in any case of data loss or down in monitoring service.

RTO

Our infrastructure is still small, therefore restoring of backup should take no longer than 2 hours.