Skip to content

Latest commit

 

History

History
56 lines (31 loc) · 1.93 KB

export-and-import-from-the-blockchain.md

File metadata and controls

56 lines (31 loc) · 1.93 KB

Export and import of the blockchain

Note This functionality available since version 0.8.

Export existing blocks to a binary file {#user-content-export-existing-blocks-to-a-binary-file}

Note You have to stop the node before starting export of blocks.

To export existing blockchain to the binary file run following command. Export is quite a fast operation, but resulting binary file could additionally take up to 1/3 ofdatafolder size on disk.

On Windows:

java -cp waves-all-<version>.jar com.wavesplatform.Exporter [configuration-file-name] [output-file-name] [height]

On Linux:

sudo -u waves[-testnet] java -cp '/usr/share/waves[-testnet]/lib/*' -Dwaves.directory=/var/lib/waves[-testnet] com.wavesplatform.Exporter /etc/waves[-testnet]/waves.conf [output-file-name] [height]

By default, the Testnet configuration file will be used.

If parameterheightwas not given all blocks will be exported. In another case, only blocs up to the height will be exported to the output file.

The output file name parameter is optional, name 'blockchain' is used by default. As a result, a file named '<output-file-name>-<height>' will be created in the current folder.

Import blocks from the binary file {#user-content-import-blocks-from-the-binary-file}

Warning This operation will completely overwrite existing node data. Do not forget to make a backup of your node’sdatafolder.

To import the blockchain and fully rebuild the state run the following command.

On Windows:

java -cp waves-all-<version>.jar com.wavesplatform.Importer [configuration-file-name] [binary-file-name]

On Linux:

sudo -u waves[-testnet] java -cp '/usr/share/waves[-testnet]/lib/*' -Dwaves.directory=/var/lib/waves[-testnet] com.wavesplatform.Importer /etc/waves[-testnet]/waves.conf [binary-file-name]

Import is a heavy operation and could take few hours to complete.