Wiki source code of ThingsEye backup policy
Last modified by Alec Chen on 2025/12/12 17:22
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | For ThingsEye , our standard data protection approach is database-level backups, because platform data (devices, telemetry, alarms, attributes, etc.) is stored in the database. |
| 2 | |||
| 3 | We currently run two backup policies in parallel for ThingsEye. | ||
| 4 | |||
| 5 | === Policy 1: Daily backups (short-term) === | ||
| 6 | |||
| 7 | * **Frequency**: Once per day (Full Backup) | ||
| 8 | * **Retention**: 30 days | ||
| 9 | * **Purpose**: Fast recovery from recent issues such as misconfiguration, accidental changes, or data anomalies | ||
| 10 | |||
| 11 | === Policy 2: Weekly backups (mid-term) === | ||
| 12 | |||
| 13 | * **Frequency**: Twice per week — every **Monday** and **Thursday** (Full Backup) | ||
| 14 | * **Retention**: 90 days | ||
| 15 | * **Purpose**: Longer-term recovery and audit/troubleshooting needs | ||
| 16 | |||
| 17 | === Scope === | ||
| 18 | |||
| 19 | * Backups are database-centric and cover core platform data including devices/assets, tenants/users, alarms, attributes, and telemetry (time-series data). |