hermes-recovery/scripts/migration-backup/migration-recovery.md

Hermes Migration — Old Hetzner Box → New Netcup Box

If anything goes wrong, start here.

BOX REFERENCE

• Old box (Hetzner agent): germaine@agent — currently hosting this conversation
• New box (Netcup app1): root@152.53.192.33 via wisp_rsa key
• wisp_rsa key location: /root/.ssh/wisp_rsa (both boxes)
• SSH into new box from old: ssh -i /root/.ssh/wisp_rsa root@152.53.192.33

WHAT NEEDS TO MOVE

Phase 1 — Before decommissioning old box

1. Skills → ~/.hermes/skills/ — all the custom workflows
2. Scripts → ~/.hermes/scripts/ — backup scripts, configs
3. Cron jobs → Hermes cron (not system cron) — need to be recreated on new box
4. Memory → persistent memory entries (fact_store + memory tool)
5. DR documents → ~/.hermes/dr-documents/
6. Migration plan docs → ~/.hermes/skills/devops/infrastructure-automation/references/

Phase 2 — The switch

1. Shut down old Hermes gateway: systemctl stop hermes (or kill the process)
2. New box grabs Telegram bot token automatically
3. Verify by sending a Telegram message to the bot

RECOVERY — if new box fails

Rollback: Talk to old Hermes again

1. SSH into the old box: ssh germaine@agent (or via Hetzner console)
2. Restart Hermes gateway: cd ~/.hermes && screen -S hermes && hermes gateway run --replace
3. Send a Telegram message — it'll grab the bot token back
4. You're back on the old box with all history intact

If Netcup box is completely dead and unreachable

1. Go to https://www.servercontrolpanel.de/SCP/ — login with SCP 389212
2. Reset OS / reinstall
3. Re-provision with: Docker, AWS CLI, Hermes install script, config.yaml
4. Restore skills/scripts from Wasabi S3 backup

If ONLY Hermes on new box is broken (but SSH works)

1. SSH in: ssh -i /root/.ssh/wisp_rsa root@152.53.192.33
2. Restart Hermes: systemctl restart hermes.service
3. Check logs: journalctl -u hermes.service -n 50
4. Or reinstall: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash

---

What you need to know to help me

If this session ends abruptly (I disappear or the model resets):

1. Tell the new Hermes: "I'm Germaine. I was migrating from a Hetzner VPS named 'agent' to a Netcup server at 152.53.192.33. I need you to restore my previous Hermes setup." Then show it this file.

2. Critical infrastructure facts to give the new Hermes:

   • Wasabi S3 buckets: hermes-vps-backups, itpropartner-backups, mikrotik-ccr-backups
   • Wasabi IAM user: Hermes-User (Access Key GYH83FP0KL0K85N60JKQ)
   • Admin-AI provider: https://admin-ai.itpropartner.com/v1, key sk-lbhhxIk_9pQ2Vmlym7bWPA
   • Telegram bot token: 8359374835:AAEsPPBWGVa53jHkwSo9j4mAxIGsdp6SGUY
   • Home channel: 5813481339
   • SSH key: wisp_rsa at /root/.ssh/wisp_rsa
   • Router backup SSH: shonuff@192.168.88.1 via wisp_rsa over L2TP/IPsec VPN

3. If this file doesn't exist on the new box: SSH into the old box and read it from ~/.hermes/migration-recovery.md before it's decommissioned.