From f8c062242654f0d3a891d65d7a2bcacc12e68671 Mon Sep 17 00:00:00 2001 From: Felix Lange Date: Tue, 5 Nov 2019 13:36:40 +0100 Subject: [PATCH] improve backup/restore docs --- docs/_install-and-build/Backup--restore.md | 52 +++++++++------------- 1 file changed, 22 insertions(+), 30 deletions(-) diff --git a/docs/_install-and-build/Backup--restore.md b/docs/_install-and-build/Backup--restore.md index 8c41794eae..d717f50236 100644 --- a/docs/_install-and-build/Backup--restore.md +++ b/docs/_install-and-build/Backup--restore.md @@ -1,41 +1,28 @@ --- -title: Backup & restore +title: Backup & Restore sort_key: C --- -**DO NOT FORGET YOUR PASSWORD** and **BACKUP YOUR KEYSTORE** +Most important info first: **REMEMBER YOUR PASSWORD** and **BACKUP YOUR KEYSTORE**. - +## Data Directory -# Backup & restore - -## Data directory - -Everything `geth` persists gets written inside its data directory (except for the PoW Ethash DAG, see note below). -The default data directory locations are platform specific: +Everything `geth` persists gets written inside its data directory. The default data +directory locations are platform specific: * Mac: `~/Library/Ethereum` * Linux: `~/.ethereum` * Windows: `%APPDATA%\Ethereum` -Accounts are stored in the `keystore` subdirectory. The contents of this directories should be transportable between nodes, platforms, implementations (C++, Go, Python). +Accounts are stored in the `keystore` subdirectory. The contents of this directories +should be transportable between nodes, platforms, implementations (C++, Go, Python). -To configure the location of the data directory, the `--datadir` parameter can be specified. See [CLI Options](../interface/command-line-options) for more details. +To configure the location of the data directory, the `--datadir` parameter can be +specified. See [CLI Options](../interface/command-line-options) for more details. -_**note:** the [ethash dag](../legacy/mining) is stored at `~/.ethash` (Mac/Linux) or `%APPDATA%\Ethash` (Windows) so that it can be reused by all clients. You can store this in a different location by using a symbolic link._ - -## Upgrades - -Sometimes the internal database formats need updating (for example, when upgrade from before 0.9.20). This can be run with the following command (geth should not be otherwise running): - -``` -geth upgradedb -``` +Note the [ethash dag](../interface/mining) is stored at `~/.ethash` (Mac/Linux) or +`%APPDATA%\Ethash` (Windows) so that it can be reused by all clients. You can store this +in a different location by using a symbolic link. ## Cleanup @@ -45,24 +32,29 @@ Geth's blockchain and state databases can be removed with: geth removedb ``` -This is useful for deleting an old chain and sync'ing to a new one. It only affects data directories that can be re-created on synchronisation and does not touch the keystore. +This is useful for deleting an old chain and sync'ing to a new one. It only affects data +directories that can be re-created on synchronisation and does not touch the keystore. -## Blockchain import/export +## Blockchain Import/Export Export the blockchain in binary format with: + ``` geth export ``` -Or if you want to back up portions of the chain over time, a first and last block can be specified. For example, to back up the first epoch: +Or if you want to back up portions of the chain over time, a first and last block can be +specified. For example, to back up the first epoch: ``` geth export 0 29999 ``` -Note that when backing up a partial chain, the file will be appended rather than truncated. +Note that when backing up a partial chain, the file will be appended rather than +truncated. Import binary-format blockchain exports with: + ``` geth import ``` @@ -70,4 +62,4 @@ geth import _See https://github.com/ethereum/wiki/wiki/Blockchain-import-export for more info_ -And finally: **DO NOT FORGET YOUR PASSWORD** and **BACKUP YOUR KEYSTORE** +And finally: **REMEMBER YOUR PASSWORD** and **BACKUP YOUR KEYSTORE**