- Organized 252 files across project - Root directory: 187 → 2 files (98.9% reduction) - Moved configuration guides to docs/04-configuration/ - Moved troubleshooting guides to docs/09-troubleshooting/ - Moved quick start guides to docs/01-getting-started/ - Moved reports to reports/ directory - Archived temporary files - Generated comprehensive reports and documentation - Created maintenance scripts and guides All files organized according to established standards.
3.5 KiB
3.5 KiB
r630-01 Migration Complete - VMIDs 100-130 and 7800-7811
Date: 2025-01-20
Status: ✅ Migration Complete
Method: Backup/Restore Migration
Executive Summary
Successfully migrated 12 containers from r630-02 to r630-01 using backup/restore method:
- VMIDs 100-130 (7 containers) → thin1 storage (96 GB)
- VMIDs 7800-7811 (5 containers) → local storage (210 GB)
- Total: 306 GB migrated
Migration Details
VMs Migrated
VMIDs 100-130 → thin1 storage:
- ✅ 100: proxmox-mail-gateway
- ✅ 101: proxmox-datacenter-manager
- ✅ 102: cloudflared
- ✅ 103: omada
- ✅ 104: gitea
- ✅ 105: nginxproxymanager
- ✅ 130: monitoring-1
VMIDs 7800-7811 → local storage:
- ✅ 7800: sankofa-api-1
- ✅ 7801: sankofa-portal-1
- ✅ 7802: sankofa-keycloak-1
- ✅ 7810: mim-web-1
- ✅ 7811: mim-api-1
Migration Method
Backup/Restore Process
Used vzdump and pct restore to migrate VMs:
- Backup: Created backups on r630-02 using
vzdumpto local storage - Restore: Restored backups to r630-01 with target storage specification
- Verification: Confirmed VMs on target node
- Cleanup: Removed original VMs from source
Commands:
# Backup
vzdump <vmid> --storage local --compress gzip --mode stop
# Restore
pct restore <vmid> /var/lib/vz/dump/vzdump-lxc-<vmid>-*.tar.gz \
--storage <target-storage> \
--target r630-01
# Cleanup
pct destroy <vmid> # on source node
Storage Distribution
r630-01 Storage Usage
| Storage | Type | Used | Available | VMs |
|---|---|---|---|---|
| thin1 | lvmthin | 96 GB | 112 GB | VMIDs 100-130 |
| local | dir | 210 GB | 326 GB | VMIDs 7800-7811 |
| Total | 306 GB | 438 GB | 12 containers |
Issues Resolved
Storage Configuration Mismatch
Problem:
- Direct migration failed due to storage volume group mismatch
- thin1 on r630-02 uses VG
thin1, but config saidpve - thin1 on r630-01 uses VG
pve
Solution:
- Used backup/restore method which bypasses storage configuration issues
- Allows storage conversion during restore (thin4→local, thin1→thin1)
Verification
Pre-Migration
- ✅ All 12 VMs verified on r630-02
- ✅ Storage capacity confirmed (944 GB available)
- ✅ All VMs in stopped state
Post-Migration
- ✅ All 12 VMs verified on r630-01
- ✅ No VMs remaining on r630-02 for these VMIDs
- ✅ Storage usage confirmed
- ✅ VMs configured correctly
Migration Script
Script: scripts/migrate-vms-backup-restore-final.sh
Features:
- Automated backup/restore for all VMs
- Error handling and verification
- Progress reporting
- Automatic cleanup
Next Steps
- ✅ Migration Complete
- ⏳ Verify VM functionality - Start VMs and verify services
- ⏳ Monitor storage usage - Track thin1 and local storage
- ⏳ Cleanup backups - Remove backup files if no longer needed
- ⏳ Update documentation - Document final VM locations
Key Learnings
- Backup/Restore Method: Reliable when storage configurations don't match
- Storage Conversion: Proxmox automatically converts storage types during restore
- Verification: Always verify VMs on target before removing from source
- Storage Planning: Separate storage pools (thin1 vs local) for different VM groups
Last Updated: 2025-01-20
Status: ✅ MIGRATION COMPLETE
Method: Backup/Restore
Result: All 12 containers successfully migrated