Quilibrium.one
SocialOfficial
Quilibrium Node Guide
Quilibrium Node Guide
  • 🖖Introduction
  • ✅Safety checks
  • đŸ“ŖAnnouncements
  • 🔗Links & Info
  • đŸ’ģBest server providers
  • đŸ’ģHardware requirements
  • 😎Q1 - Node Manager
  • ⚡Node Auto-installer
  • âŦ†ī¸Updating your node
  • âœ”ī¸Check your node info
  • 🔑Backup your private keys
  • đŸ“ĻBackup your node
  • 🔁Set up the gRPC calls
  • đŸ› ī¸Tools and scripts
  • 🔧Extra tools
  • 🔠Useful commands
  • â‰ī¸Troubleshooting
  • 📌Tutorials
    • Node
      • đŸ”ĸNode step by step installation
      • đŸŗInstalling the node on Docker
      • đŸĒŸInstalling the node and the qclient on Windows WSL
      • â†—ī¸Migrating the node to a new server
      • â„šī¸Running the node via binary file
      • Running a node cluster
      • ✅Reinstalling the node from scratch
      • âš™ī¸Managing your system resources
        • â˜‘ī¸Limiting your vCores usage
        • â˜‘ī¸Limiting your CPU usage
        • â˜‘ī¸Limiting the RAM assigned to each vCore
      • 🔄Switching from tmux to service
      • 💲Log your node balance every 1 hour
      • 🩷Escaping the "Pink Screen of Death"
      • 🔒Set up SSH keys
      • 🔒Creating a root login access
      • 👀Renting Servers Unveiled: Exploring Types and Processor Terminology
    • Qclient
      • Qclient commands
      • How to transfer QUIL
      • How to Bridge QUIL to WQUIL
      • How to retrieve your coin address after a failed bridging operation
  • 📂Archive
    • ⚡OLD - Node Auto-installer
    • đŸ”ĸOLD - Node step by step installation
    • 🔠OLD - Useful server commands
    • â‰ī¸OLD Troubleshooting
    • âŦ†ī¸OLD Updating your node
    • ⚡Importing an existing store folder for fast sync
    • â˜‘ī¸Changing the cpulimit value in release_autorun
  • âš ī¸Work in progress
  • 💜Want to say thank you?
Powered by GitBook
On this page
  1. Tutorials
  2. Node

Migrating the node to a new server

PreviousInstalling the node and the qclient on Windows WSLNextRunning the node via binary file

Last updated 1 month ago

The Q1 - Node Manager has an option to backup your node to StorJ and another one to restore it. Using those options you could also easily migrate the node to another machine. If you did not backed up the node on Storj, then follow the guides below.

SInce v2.0 Node "store" folders are interchangeable. This means that the fastest way to move a node to another machine is the following: - Install node on new machine and let it sync to the latest frame (or restore a "store" folder snapshot if you have it) - Stop new machine node - Import config.yml and keys.yml from old to new machine - Stop old machine node - Restart new machine node Be sure to have a MIGRATIONS file in the node/.config folder of the new machine.

You have access to the source and target servers and your .config folder is on the source server

This guide will only work if you use username and password to access your target server (which is not the best for security). If you use an SSH key, you will need to follow a more advanced method. Or you can simply setup an SSH key AFTER you have migrated the files to the target server.

  • Use the auto-installer script in this guide to install the node. This step is clearly optional if you have already installed the node.

  • Remove the whole node/.config folder from the new server (this will delete your new server keys!).

rm -r ~/ceremonyclient/node/.config
  • Grab your new server IP and password.

  • Login to the old server, stop the node and run the below command. This will copy the entire node/.config folder from the old to the new server. Change <NEW_SERVER_IP> with your new server IP and enter the new server password when requested.

scp -r ~/ceremonyclient/node/.config root@<NEW_SERVER_IP>:/root/ceremonyclient/node/

Moving files like this via a password connection poses a security risk. It's better to setup SSH keys between your servers instead.

You only have access to the target server and your .config folder is on your local PC
  • Use the auto-installer script in this guide to install the node on the new server.. This step is clearly optional if you have already installed the node.

  • Remove the whole node/.config folder from the new server (this will delete your new server keys!).

rm -r ~/ceremonyclient/node/.config
  • Upload your local .config folder to /ceremonyclient/node/.config

  • Restart the node

Complete manual process

This is the simplest migration process if you don't want to use the node auto-installer. But you will have to create the node service manually.

Login to your target server

Upload your .config folder to ~/backup/

Follow the Node step by step installation to install the node manually

Go to the node folder

cd ceremonyclient/node

Copy your .config folder to the node folder

cp -r ~/backup/.config  /.config

Start the node


📌
â†—ī¸
Cover

Want to say thank you?

CLICK TO DONATE