migrate-database
Migrate the database to a LevelDB2 database.
As of v21.5.0, new Teku installations use a LevelDB2 database. Previous Teku versions use RocksDB which continue to be supported.
Before running the database migration, you must shut down the local Teku instance and confirm the process has fully exited and won't be restarted.
config-file
- Syntax
- Example
- Environment variable
teku migrate-database --config-file=<FILE>
teku migrate-database --config-file=/home/me/me_node/config.yaml
TEKU_CONFIG_FILE=/home/me/me_node/config.yaml
Path to the YAML configuration file. The default is none.
data-base-path, data-path
- Syntax
- Example
- Environment variable
- Configuration file
teku migrate-database --data-base-path=<PATH>
teku migrate-database --data-base-path=/home/me/me_node
TEKU_DATA_BASE_PATH=/home/me/me_node
data-base-path: "/home/me/me_node"
Path to the Teku data directory. The default directory is OS-dependent:
- macOS:
~/Library/teku - Unix/Linux:
$XDG_DATA_HOME/tekuif$XDG_DATA_HOMEis set; otherwise~/.local/share/teku - Windows:
%localappdata%\teku
The default Docker image location is /root/.local/share/teku.
data-beacon-path
- Syntax
- Example
- Environment variable
- Configuration file
teku migrate-database --data-beacon-path=<PATH>
teku migrate-database --data-beacon-path=/home/me/me_node
TEKU_DATA_BEACON_PATH=/home/me/me_node
data-beacon-path: "/home/me/me_node"
Path to the beacon node data. The default is <data-base-path>/beacon where <data-base-path> is specified using --data-base-path.
network
- Syntax
- Example
- Environment variable
- Configuration file
teku migrate-database --network=<NETWORK>
teku migrate-database --network=mainnet
TEKU_NETWORK=mainnet
network: "mainnet"
Predefined network configuration. Accepts a predefined network name, or file path or URL to a YAML configuration file. See the consensus specification for examples.
The default is mainnet.
Possible values are:
| Network | Chain | Type | Description |
|---|---|---|---|
mainnet | Consensus layer | Production | Main network |
holesky | Consensus layer | Test | Multi-client testnet |
ephemery | Consensus layer | Test | Multi-client testnet |
sepolia | Consensus layer | Test | Multi-client testnet |
minimal | Consensus layer | Test | Used for local testing and development networks |
gnosis | Consensus layer | Production | Network for the Gnosis chain |
chiado | Consensus layer | Test | Gnosis testnet |
lukso | Consensus layer | Production | Network for the Lukso chain |