Back to all posts

How to create a NEBULAS switchover solution

Sometimes you may want to secure your Nebulas node from high downtime and Block Generation Penalties that is caused by the server failure. In order to avoid negative scenarios you can use the switchover solution, that implies deployment of a backup server with the preconfigured Nebulas node. Following this practice, we’ll have fast and reliable transition process from one server to another, having possibility to continue producing blocks with minimal downtime. 

💡 Always analyze your Nebulas node activities and be ready to determine a problem. The following script can help you to monitor the status of the Nebulas node, while sending server status notifications to a Telegram channel in case the node stops syncing or goes down. 

Configuration

The Nebulas switchover solution is surprisingly easy to set up. 

  • Firstly, you need to have a backup server. Install and launch the Nebulas node on the backup server. To switch quickly add your key block signature address to the keydir directory and make sure your config.conf looks like 


    $ vim mainnet/conf/config.conf

    ```

    start_min: false

    # start_mine: true

    # coinbase: "your_coinbase_address"

    # miner: "your_miner_address"

    # passphrase: "your_pass_for_miner_address"

    ```

Switch to the backup server

If your main Nebulas node or server goes down, you can manually initiate the switch to the backup server by following steps:

  1. 💡 Make sure that your main node doesn’t work or is working in start_min: false mode without the main miner key in config.conf!
  2. Uncomment lines in config.conf on the backup server 

    $ vim mainnet/conf/config.conf

    ```

    # start_min: false

    start_mine: true

    coinbase: "your_coinbase_address"

    miner: "your_miner_address"

    passphrase: "your_pass_for_miner_address"

    ```

  3. Restart your backup Nebulas node in order to start to produce blocks.

    Next time if your main Nebulas node or server goes down, you can quickly switch from one server to another, allow for a smooth continuation of producing. Thus, you can fix the problem with the main node at a convenient time.

    ...

    Website: everstake.one

    Twitter: @Everstake_pool

    Telegram: @Everstake_chat

    Facebook: fb.me/everstake.one

    Reddit: /r/Everstake/

Previous post Next post