Skip to main content

ThingsEye backup policy

Last modified by Alec Chen on 2025/12/12 17:22

For ThingsEye, our standard data protection approach is database-level backups, because platform data (devices, telemetry, alarms, attributes, etc.) is stored in the database.

Backup Policies​

We currently run two backup policies in parallel for ThingsEye.

Policy 1: Daily backups (short-term)​

  • Frequency: Once per day (Full Backup)
  • Retention: 30 days
  • Purpose: Fast recovery from recent issues such as misconfiguration, accidental changes, or data anomalies

Policy 2: Weekly backups (mid-term)​

  • Frequency: Twice per week — every Monday and Thursday (Full Backup)
  • Retention: 90 days
  • Purpose: Longer-term recovery and audit/troubleshooting needs

Scope​

Backups are database-centric and cover core platform data including:

  • Devices / Assets
  • Tenants / Users
  • Alarms
  • Attributes
  • Telemetry (time-series data)

Backup Storage & Security (Supplemental)​

  • Storage Location: Backups are securely stored in [Insert Storage Location, e.g., Cloud Storage / NAS] to ensure redundancy.
  • Encryption: All backups are encrypted at rest using industry-standard protocols.
  • Access Control: Access to backup files is strictly restricted to authorized system administrators only.

Backup Verification & Restoration (Supplemental)​

  • Testing Frequency: Backup integrity and restoration procedures are tested [Insert Frequency, e.g., quarterly] to ensure data can be successfully recovered.
  • RTO/RPO:
    • RTO (Recovery Time Objective): [Insert RTO]
    • RPO (Recovery Point Objective): [Insert RPO, e.g., 24 hours]
  • Restoration Procedure: In the event of data loss, administrators will follow the standard database restoration procedural runbook using the latest valid backup.