You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: terra/README.md
+84-10Lines changed: 84 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -90,12 +90,14 @@ This will create a ".terrad" directory in the home folder. It comes with a file
90
90
91
91
For the Mainnet (columbus-4), the genesis file can be downloaded from https://columbus-genesis.s3-ap-northeast-1.amazonaws.com/columbus-4-genesis.json (reference [docs.terra.money](https://docs.terra.money/node/join-network.html#download-the-genesis-file)).
92
92
93
-
The address book can be found at https://network.terra.dev/addrbook.json (reference [docs.terra.money](https://docs.terra.money/node/join-network.html#picking-a-network)).
93
+
~~The address book can be found at https://network.terra.dev/addrbook.json (reference [docs.terra.money](https://docs.terra.money/node/join-network.html#picking-a-network)).~~ The address book is not actually required.
94
94
95
95
For the Testnet (tequila-0004), the genesis file can be downloaded from https://raw.githubusercontent.com/terra-project/testnet/master/tequila-0004/genesis.json (reference [github.com](https://github.com/terra-project/testnet)).
96
96
97
97
The address book can be found at https://network.terra.dev/testnet/addrbook.json
98
98
99
+
> For Bombay testnet, the genesis file is at https://raw.githubusercontent.com/terra-project/testnet/master/bombay-0007/genesis.json
100
+
99
101
Update the seeds (~/.terrad/config/config.toml) to begin running the blockchain. The seeds for Mainnet are (reference: [docs.terra.money](https://docs.terra.money/node/join-network.html#define-seed-nodes)):
100
102
101
103
```
@@ -120,18 +122,93 @@ The daemon can now be started to run through the blocks.
120
122
121
123
# For a replacement server
122
124
125
+
One key consideration when preparing a replacement server is whether the blockchain data is migrated or is a new one created.
126
+
127
+
## Replacement server with new data
128
+
123
129
Do the same steps for initializing the server. This includes downloading the snapshot file and extracting it.
124
130
125
131
To do the migration:
126
132
127
-
1. Stop the old terrad server
133
+
1. Stop the old terrad server.
128
134
2. Copy `.terrad/config/priv_validator_key.json` to the new node.
129
135
3. Copy `.terrad/data/priv_validator_state.json` to the new node.
(No need to move .terrad/config/node_key.json - [https://discord.com/channels/566086600560214026/566126867686621185/842673595117207573])
134
141
142
+
## Replacement server with existing data
143
+
144
+
Prepare the server by making the software components are in place. There is no need to download the blockchain snapshot since the data is already available for migration.
145
+
146
+
What _needs_ to be done is to re-attach the block storage when doing the migration. To prepare for this step, the following commands can be run prior to the stopping of the old server.
147
+
148
+
```bash
149
+
sudo mkdir /mnt/columbus4
150
+
sudo chown $USER:$USER -R /mnt/columbus4
151
+
mkdir -p ~/columbus
152
+
mv -i ~/.terrad/data ~/columbus
153
+
ln -s /mnt/columbus4/data ~/.terrad/data
154
+
```
155
+
156
+
To do the migration:
157
+
158
+
1. Stop the old terrad server.
159
+
2. Unmount the storage volume.
160
+
3. Copy `.terrad/config/priv_validator_key.json` to the new node.
161
+
4. Mount the storage volume to the new server.
162
+
5. Start the new terrad server.
163
+
164
+
The sequence of commands is described in the next section.
165
+
166
+
## Synchronization
167
+
168
+
To sync data quickly and easily, the replacement server (Server B) needs to generate a set of SSH keys to access the origin server (Server A).
169
+
170
+
```bash
171
+
# Server B
172
+
## Create a hosts file entry for the origin server server-a.
0 commit comments