Migration Guide (On Pillar)
Last updated
Was this helpful?
Last updated
Was this helpful?
This guide outlines the steps to migrate an existing orchestrator from one Pillar virtual machine (VM) to another, preserving its ability to participate in the HyperCore bridge’s Threshold Signature Scheme (TSS) signer set. It builds on the .
Old VM Access: Ensure the original VM (old Pillar) is still accessible and running the orchestrator.
New VM Setup: The new VM should have a working Pillar node synced with the Zenon Network of Momentum (NoM), as per the .
Backup: Back up the old VM’s orchestrator directory (/root/.orchestrator) and producer keystore before proceeding.
SSH Access: You need SSH access to both the old and new VMs with sufficient permissions (e.g., root or sudo).
If the orchestrator isn’t already installed on the new VM, follow the initial setup steps from the first.
Copy the entire .orchestrator folder from the old VM to the new VM. This includes the old /producer folder and old config.json:
Confirm the orchestrator is functioning and recognized by the bridge.
a) Check Logs:
View recent logs for errors:
b) Test Health Check:
Query the orchestrator’s API:
Expected output includes version info, e.g.,
Follow of the Setup Guide.