ifixkart-admin/docs/operations/backup-recovery.md
Adithiyan bbd3a3e959 feat: initial commit — full platform snapshot
- Backend: FastAPI app with all models, services, schemas, routes
- Admin Panel: Next.js dashboard with all modules
  (CRM, POS, repairs, warranties, billing, notifications, etc.)
- Ecommerce: storefront (submodule) + product catalog
- AI Agents: .agents/ skill library for Antigravity IDE
- Docs: architecture, billing, notification gateway markdown
- Submodules: Backend/OpenWA, Ecommerce/File 2/storefront
2026-10-13 12:59:47 +05:30

701 B

Backup & Disaster Recovery Architecture

Recovery Point & Time Objectives

  • Recovery Point Objective (RPO): < 5\text{ minutes} (Zero data loss for completed payment/order transactions).
  • Recovery Time Objective (RTO): < 15\text{ minutes} for complete cluster restoration.

Backup Schedules

  1. MySQL Database:
    • Automated continuous binary log (binlog) archiving for Point-In-Time Recovery (PITR).
    • Hourly snapshot backups to multi-region object storage (S3 / GCS).
  2. Redis: RDB snapshots daily; AOF (Append-Only File) enabled for durability.
  3. SQLite POS: Local SQLite backups taken after every 50 local transactions, saved to encrypted local storage.