bostonwine on Nostr: #node questions 1. You decide to run a pruned node. Let’s say 10 GB limit. The time ...
#node questions
1. You decide to run a pruned node. Let’s say 10 GB limit. The time chain weighs ~575 GB (if I remember correctly). Node/computer’s available storage is around 250 GB.
You expect you may want to convert the pruned node into a full node in the future. It won’t fit on your computer, so you plan to buy an external drive.
Is it relatively simple to “move” your node’s data to the larger storage hardware and re-download the (full) chain, without pruning?
Is it better to simply spin up another node and have two? ✌️
Published at
2024-05-21 01:01:55Event JSON
{
"id": "65e064c9d85d87d6db9688e8e4c37db7d6e1d14ac72a82bdfb64c605fc7bbb1f",
"pubkey": "a80455732d5bfa792f279011a8c871853182971994752b9cf1169611ff91a578",
"created_at": 1716246115,
"kind": 1,
"tags": [
[
"t",
"node"
]
],
"content": "#node questions\n\n1. You decide to run a pruned node. Let’s say 10 GB limit. The time chain weighs ~575 GB (if I remember correctly). Node/computer’s available storage is around 250 GB.\n\nYou expect you may want to convert the pruned node into a full node in the future. It won’t fit on your computer, so you plan to buy an external drive.\n\nIs it relatively simple to “move” your node’s data to the larger storage hardware and re-download the (full) chain, without pruning?\n\nIs it better to simply spin up another node and have two? ✌️",
"sig": "ae0f02faa3a66b9a1eea1a656774d5e19e960c1d3f1fd8a8f5708ab6de9b9a5a0320b38327155a3dd648052945a69c88bd81d3536b2c0301e9a3775e59c95578"
}