Document Name: | Database Backup & Restoration Policy |
|
|
Classification: | Internal |
|
|
Document Owner: | CISO/MR- |
|
|
Document Approver: | Top Management |
|
|
Original Document Issue Date: | 10/10/2023 |
|
|
Current Edition: | Version 3.0 |
|
|
Revision History: |
|
|
|
S. No. | Description of Change | Date of Change | Version No. |
1 | Initial Release | 10/10/2023 | 1.0 |
2 | Second Release | 10/10/2024 | 2.0 |
3 | Third Release | 10/10/2025 | 3.0 |
1. Policy Purpose
This document defines the requirements and procedures for the backup and restoration of Legistify's cloud database clusters. The objective is to maintain high availability and ensure data can be recovered to meet Recovery Point Objectives (RPO) and Recovery Time Objectives (RTO) during incidents.
2. Backup Configuration Standards
All production-level clusters are required to implement the following automated backup policy to ensure multi-layered protection.
Frequency Unit | Interval | Retention | Use Case |
Hourly Snapshot | Every 6 Hours | 7 Days | Granular recovery from recent data errors. |
Daily Snapshot | Every 24 Hours | 7 Days | Standard daily rollback capability. |
Weekly Snapshot | Every Saturday | 4 Weeks | Archival for medium-term data history. |
Monthly Snapshot | Last day of month | 12 Months | Long-term compliance and audit requirements. |
Point-in-Time Recovery (PITR): The system maintains a continuous oplog for a 7-day window, allowing for restoration to any specific second within that timeframe.
3. Restoration Procedures
Restoration must be initiated through the cloud management console by authorized administrators. There are two primary workflows:
3.1 Snapshot Restoration
Reverts a cluster to the exact state captured at a specific interval (e.g., last night's 23:23 UTC snapshot). Best for major environment rollbacks.
3.2 Point-in-Time (PIT) Restore
Allows an administrator to specify a precise date and time. The system restores the closest snapshot and replays logs to that exact moment. Best for reversing specific accidental deletions.
4. Operating Guidelines
Verification: After any restoration, the "Status" must be verified as "Completed". Data integrity checks must be performed before pointing production traffic to the restored instance.
Security: Restoration access is limited to the 'Project Owner' role to prevent unauthorized data exfiltration.
Monitoring: Backup health status must be monitored daily via the administrative dashboard.