Page Comparison

You should see the following if zend is stopped

Open a second terminal and SSH into your source node (left) with it's non-root user

NOTE: You should now have two terminal windows open and connected to two separate nodes. Arrange the source node on the left side of your screen, and the destination node on the right side of your screen

NOTE: The zend daemon should be stopped to prevent transfer errors in the following steps, the tracker is also stopped to limit errors from the source node (left)

• Execute the following on the source node (left)

sudo systemctl stop zend zentracker

• Execute the following on the destination node (right)

zen-cli stop

• Verify zend is stopped on both the source node (left) and destination node (right)

zen-cli getinfo

You should see the following if zend is stopped

DON'T RUN THIS UNTIL AFTER THE COMMAND FOR THE DESTINATION NODE HAS BEEN EXECUTED!

Executed from the destination node (right)

• Remove all files and folders from the blocks and chainstate directories on destination node (right)
  

rm -rf ~/.zen/blocks/*
rm -rf ~/.zen/chainstate/*

____________________________________________________________________________________________________

Executed from the source node (left)

• Replace <D_USER> with the non-root user of the destination node, replace <D_FQDN> with the fully-qualified domain name of the destination node, remove <brackets>
  
• When prompted, enter the non-root user password for the destination node to execute the transfer

scp -r ~/.zen/blocks/* <D_USER>@<D_FQDN>:~/.zen/blocks/
scp -r ~/.zen/chainstate/* <D_USER>@<D_FQDN>:~/.zen/chainstate/

RUN ON THE DESTINATION NODE FIRST, DO NOT RUN ON THE SOURCE NODE!

NOTE: You may get an error if these files do not exist, you can ignore this

Start zend and zentracker on the source node (left)

• Execute the following on the source node (left)

sudo systemctl start zend && sleep 8 && sudo systemctl start zentracker

• You may exit from the source node (left) and close your terminal
  

exit

Execute the zend daemon on the destination node (right) with the rescan option

• Check your node's block height, compare with: https://explorer.zensystemhorizen.io/

NOTE: If your node is using systemd or monit and pm2, start those after the following, using instructions from step 3

• Change ownership of blocks and chainstate folders recursively to the current user

sudo chown -R $USER ~/.zen/{blocks,chainstate}

• Start the zen daemon with rescanning

zend --rescan && sleep 30

• Check your current block count every 30 seconds

watch -n 30 zen-cli getblockcount

• Your destination node (right) has been successfully bootstrapped after verifying your blocks match the block height on the explorer linked above
• exit the command with CTRL + c