Workstation Backup Strategy
Overview
This document describes the backup strategy for the BlueGreenCity-KI workstation to ensure data safety and business continuity.
Primary Backup: External Hard Drive
Hardware
- Device: Seagate Expansion 12TB external hard drive
- Connection: USB (disconnected after backup completion)
Backup Method
- Tool: Windows Backup and Restore (Windows 7)
- Type: System image and file backup
- Schedule: Manual, performed at the beginning of each month
- Storage Location: External drive is disconnected and stored safely after backup completion
Backup Process
- Create PostGIS database dump (see Database Export below)
- Connect Seagate Expansion 12TB drive to workstation
- Open Control Panel → System and Security → Backup and Restore (Windows 7)
- Click “Back up now” to start the backup process
- Wait for backup completion (verify success message)
- Safely eject the external drive
- Disconnect and store the drive in a secure location
Important: The drive remains disconnected between backups to protect against:
- Ransomware attacks
- Accidental deletion
- System failures affecting connected drives
Backup Frequency
- Primary backup: Monthly (beginning of each month)
- Next backup due: Check calendar for first week of next month
Secondary Backups
Seafile Cloud Sync
- Purpose: Real-time synchronization of project files
- Scope: Code workspace and documentation
- Sync frequency: Automatic, real-time
- Location: local Seafile workspace for the project repository
GitHub Version Control
- Purpose: Source code versioning and collaboration
- Repository:
wanderfunke/bluegreencity-ki
- Sync frequency: On commit and push
- Scope:
- Source code
- Configuration files
- Documentation
- Scripts
Note: Git does not backup large data files (climate data, derived datasets). These are covered by:
- External drive backup (primary)
- Seafile sync (secondary)
Backup Coverage
| Data Type |
External Drive |
Seafile |
GitHub |
| System image |
✅ |
❌ |
❌ |
| Source code |
✅ |
✅ |
✅ |
| Documentation |
✅ |
✅ |
✅ |
| Configuration files |
✅ |
✅ |
✅ |
| Climate data (NetCDF) |
✅ |
✅ |
❌ |
| Derived datasets |
✅ |
✅ |
❌ |
| Database (PostGIS) |
✅ |
✅ |
❌ |
| Database dumps (SQL) |
✅ |
✅ |
❌ |
| Development tools |
✅ |
❌ |
❌ |
Recovery Scenarios
Full System Failure
- Restore system image from external drive using Windows Recovery
- Reconnect Seafile workspace
- Clone GitHub repository if needed
- Verify PostGIS database integrity
Partial Data Loss
- Restore specific files from external drive backup
- Use Seafile file history for recent changes
- Use Git history for code recovery
Ransomware Attack
- Disconnect all drives immediately
- Do NOT connect external backup drive to infected system
- Clean system or reinstall OS
- Restore from external drive on clean system
- Resync Seafile and GitHub
Backup Verification
Monthly Checklist
Backup Test (Quarterly)
Database Backup
Database Export
Monthly SQL Dumps
PostGIS database dumps are created monthly as part of the backup routine.
Export frequency: Monthly (at the beginning of each month, before external backup)
Export location: data/backups/postgis/YYYY-MM/
Included in:
- ✅ Seafile sync (automatic, real-time)
- ✅ External drive backup (via Windows Backup)
Database Export Process
- Run database backup script:
cd scripts
.\backup_postgis.ps1
- Verify dump files created in
data/backups/postgis/YYYY-MM/:
bgcki_backup_YYYYMMDD_HHMMSS.backup (custom/compressed format, recommended)bgcki_backup_YYYYMMDD_HHMMSS.sql (plain SQL, archival)
- Dumps are automatically synced via Seafile
- External drive backup will include the dumps folder
For detailed information on database backup and restore: