| # Fathom VM Recovery Guide |
|
|
| This guide matches the live VM state observed on 2026-04-09 08:59:55 UTC. |
|
|
| ## HF dataset repo |
|
|
| - `umer07/vllm-deployement-backup` (private) |
|
|
| ## Required recovery set |
|
|
| - `vllm_deployement_backup_20260409_085856.tar.gz` |
| - `fathom_minio_data_20260409_085856.tar.gz` |
| - `fathom_neo4j_data_20260409_085856.tar.gz` |
| - `fathom_neo4j_logs_20260409_085856.tar.gz` |
| - `VM_RECOVERY_GUIDE_20260409_085856.md` |
|
|
| ## What the application archive contains |
|
|
| - `/opt/fathom` |
| - `/root/serve.py` |
| - `/root/vllm.log` |
| - `/root/serve.log` |
| - `/etc/os-release` |
|
|
| ## Live stack |
|
|
| - Host OS: Ubuntu 24.04 |
| - Host-side model process: `/root/serve.py` |
| - Model API port: `8001` |
| - Docker app root: `/opt/fathom` |
| - Backend port: `7860` |
| - Dashboard port: `3000` |
| - Neo4j ports: `7474`, `7687` |
| - MinIO ports: `9000`, `9001` |
|
|
| ## Recovery steps |
|
|
| 1. Provision an Ubuntu 24.04 VM with Docker and Python. |
| 2. Download all files from `umer07/vllm-deployement-backup`. |
| 3. Extract `vllm_deployement_backup_20260409_085856.tar.gz` at `/`. |
| 4. Recreate Docker volumes `fathom_minio_data`, `fathom_neo4j_data`, `fathom_neo4j_logs`. |
| 5. Restore `fathom_minio_data_20260409_085856.tar.gz` into `fathom_minio_data`. |
| 6. Restore `fathom_neo4j_data_20260409_085856.tar.gz` into `fathom_neo4j_data`. |
| 7. Restore `fathom_neo4j_logs_20260409_085856.tar.gz` into `fathom_neo4j_logs`. |
| 8. Start `python3 /root/serve.py`. |
| 9. Start `docker compose up -d --build` from `/opt/fathom`. |
| 10. Verify ports `8001`, `7860`, `3000`, `9000`, `7687`. |
|
|
