mirror of
https://github.com/Start9Labs/documentation.git
synced 2026-03-30 20:14:50 +00:00
cc91baf172
* Beefed up initial and updating guides with sounds and an updated screenshot * Added scary warning to top of blockchain migration guide * Changed purchased to downloaded since EmbassyOS is 100% free now * Added vaultwarden browser secure context faq question * Update updating.rst * Update faq-services.rst Co-authored-by: kn0wmad <39687477+kn0wmad@users.noreply.github.com>
59 lines
2.7 KiB
ReStructuredText
59 lines
2.7 KiB
ReStructuredText
.. _blockchain-copy:
|
|
|
|
====================
|
|
Blockchain Migration
|
|
====================
|
|
|
|
.. contents::
|
|
:depth: 2
|
|
:local:
|
|
|
|
.. warning:: This is an advanced feature and should be used with caution. Start9 is not responsible for any damage you might cause through SSH access.
|
|
|
|
If you have already synced the Bitcoin blockchain to the tip on one Embassy, and would like to skip IBD on another Embassy, follow this guide.
|
|
|
|
.. note:: The following guide requires that you have already :ref:`setup SSH on both Embassies<ssh>`.
|
|
In this guide, we will refer to your synced Embassy as embassy-AAAAAAA.local and the Embassy with no Bitcoin synced as embassy-BBBBBBB.local. Of course, please replace AAAAAAA and BBBBBBB with your appropriate Embassies' names.
|
|
|
|
**Install but don't start Bitcoin Core on the blockchain-less Embassy**
|
|
|
|
#. Log into `https://embassy-BBBBBBB.local` and install Bitcoin Core (**Marketplace > Bitcoin > Bitcoin Core > Install**). Do *NOT* yet **CONFIGURE** or **START** Bitcoin Core.
|
|
|
|
**Prep your Embassy with the synced blockchain**
|
|
|
|
#. Stop the Bitcoin Core service on `https://embassy-AAAAAAA.local` (**Services > Bitcoin Core > Stop**)
|
|
|
|
#. :ref:`Open an ssh session <connecting-via-ssh>` to embassy-AAAAAAAA.local
|
|
|
|
#. Once at the shell, perform the following commands
|
|
|
|
.. code-block:: bash
|
|
|
|
sudo -i
|
|
ssh-keygen -t ed25519 -N '' -f .ssh/embassy2.key
|
|
chmod 600 .ssh/embassy2.key*
|
|
cat .ssh/embassy2.key.pub
|
|
|
|
#. Copy the output from the cat command into embassy-BBBBBBB's **Embassy > SSH > Add New Key** text field:
|
|
|
|
.. figure:: /_static/images/walkthrough/ssh_key_add.jpg
|
|
|
|
#. Back on the shell of embassy-AAAAAAA.local, do the following (don't forget to replace embassy-BBBBBBB.local in the rsync command before you perform it):
|
|
|
|
.. code-block:: bash
|
|
|
|
cd /embassy-data/package-data/volumes/bitcoind/data/main/
|
|
rsync -e "ssh -i ~/.ssh/embassy2.key" -povgr --append-verify --rsync-path="sudo mkdir -p /embassy-data/package-data/volumes/bitcoind/data/main ; sudo rsync" ./{blocks,chainstate} start9@embassy-BBBBBBB.local:/embassy-data/package-data/volumes/bitcoind/data/main/
|
|
|
|
#. Wait some hours until the copy is complete. On a gigabit network, the limiting factor will be the write speed of your SSD on the receiving Embassy. When it is complete, clean up a bit:
|
|
|
|
.. code-block:: bash
|
|
|
|
rm .ssh/embassy2.key*
|
|
exit
|
|
|
|
#. Switch back to `https://embassy-BBBBBBB.local`, selecting **Services > Bitcoin Core**, **CONFIGURE**, configure it as desired, **SAVE** and then **START** your Bitcoin Core service. You should see it begin at 99%+ pre-synced.
|
|
|
|
#. You can now restart your Bitcoin Core service on `https://embassy-AAAAAAA.local` (**Services > Bitcoin Core > Start**)
|
|
|
|
.. _bitcoin-service: |