docs: Rebuild documentation as enterprise-grade TLAS platform
- Migrate from custom HTTP server to VitePress framework - Rename project to Tokenized License Approval System (TLAS) - Add comprehensive documentation for all stakeholders: - Business: Executive summary, value proposition, governance - Operations: Infrastructure, installation, monitoring, backup - Departments: User guide, workflows, verification, issuance - Developers: API reference, authentication, webhooks, SDKs - Compliance: OWASP, DPDP Act, IT Act, audit framework - Add modern theme with dark mode and full-text search - Update Dockerfile for VitePress build process Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
84
Documentation/operations/backup.md
Normal file
84
Documentation/operations/backup.md
Normal file
@@ -0,0 +1,84 @@
|
||||
# Backup & Recovery
|
||||
|
||||
## Backup Strategy
|
||||
|
||||
| Data Type | Frequency | Retention |
|
||||
|-----------|-----------|-----------|
|
||||
| Database (full) | Daily | 30 days |
|
||||
| Database (incremental) | Hourly | 7 days |
|
||||
| Uploaded documents | Daily | 1 year |
|
||||
| Configuration | On change | 90 days |
|
||||
| Blockchain state | Daily | 90 days |
|
||||
|
||||
## Database Backup
|
||||
|
||||
### Automated Backups
|
||||
|
||||
```bash
|
||||
# Daily full backup (runs at 02:00 UTC)
|
||||
pg_dump -Fc tlas_prod > /backups/tlas_$(date +%Y%m%d).dump
|
||||
|
||||
# Hourly WAL archiving
|
||||
archive_command = 'cp %p /backups/wal/%f'
|
||||
```
|
||||
|
||||
### Manual Backup
|
||||
|
||||
```bash
|
||||
# Create backup
|
||||
docker exec postgres pg_dump -U tlas -Fc tlas_prod > backup.dump
|
||||
|
||||
# Verify backup
|
||||
pg_restore --list backup.dump
|
||||
```
|
||||
|
||||
## Recovery Procedures
|
||||
|
||||
### Database Recovery
|
||||
|
||||
```bash
|
||||
# Stop application
|
||||
docker-compose stop api
|
||||
|
||||
# Restore database
|
||||
pg_restore -d tlas_prod -c backup.dump
|
||||
|
||||
# Verify data
|
||||
psql -d tlas_prod -c "SELECT COUNT(*) FROM applications;"
|
||||
|
||||
# Restart application
|
||||
docker-compose start api
|
||||
```
|
||||
|
||||
### Point-in-Time Recovery
|
||||
|
||||
```bash
|
||||
# Restore to specific timestamp
|
||||
recovery_target_time = '2026-02-09 10:00:00'
|
||||
```
|
||||
|
||||
## Disaster Recovery
|
||||
|
||||
### RTO/RPO Targets
|
||||
|
||||
| Metric | Target |
|
||||
|--------|--------|
|
||||
| Recovery Time Objective (RTO) | 4 hours |
|
||||
| Recovery Point Objective (RPO) | 1 hour |
|
||||
|
||||
### DR Procedure
|
||||
|
||||
1. Identify failure scope
|
||||
2. Activate DR environment
|
||||
3. Restore from latest backup
|
||||
4. Verify data integrity
|
||||
5. Update DNS to DR site
|
||||
6. Notify stakeholders
|
||||
|
||||
## Backup Verification
|
||||
|
||||
Monthly backup testing:
|
||||
- Restore to test environment
|
||||
- Run integrity checks
|
||||
- Verify application functionality
|
||||
- Document results
|
||||
Reference in New Issue
Block a user