Backups

In order to ensure you are able to redeploy your Bee node in the event of a disaster, the contents of several directories must be retained.

danger

Your keys represent your ability to access your gBZZ. Make sure to back up your keys directory in multiple places, so you can keep your gBZZs safe! See below to discover the location of your keys.

info

Don't forget - it's not a backup until you have restored it! Make sure to test your backups out so that you can be sure of recovery incase of data loss or data corruption.

Bee#

To restore a Bee node you must have the following directories, all backed up in an atomic moment so that they are syncronised.

All of this data is contained within the data directory specified in your Bee configuration.

Ubuntu / Debian / Raspbian / CentOS Package Managers#

For Linux installations from package managers yum or apt, your data directory is located at:

/var/lib/bee

It may be also useful for you to retain your configuration files, which are held at:

/etc/bee

Manual#

For a manual installation your data directory is normally located at:

~/.bee

Docker Compose#

When using our Docker Compose configuration files to run your node, Docker will create a volume for Bee and a volume for Bee Clef.

You may use docker cp to retrieve the contents of these folders.

docker cp bee_bee_1:/home/bee/.bee/ bee
docker cp bee_clef_1:/app clef

Data Types#

Your Bee data directory contains three stores.

/Users/sig/.bee
โ”œโ”€โ”€ keys
โ”‚ย ย  โ”œโ”€โ”€ libp2p.key
โ”‚ย ย  โ”œโ”€โ”€ pss.key
โ”‚ย ย  โ””โ”€โ”€ swarm.key
โ”œโ”€โ”€ localstore
โ”‚ย ย  โ””โ”€โ”€ ...
โ””โ”€โ”€ statestore
โ””โ”€โ”€ ...

Keys#

The keys directory contains your important key material. This is the most important data by far, and is produced and retained from Bee's initialisation procedure. If you have used Bee-clef to manage your key material and signing procedures, see below for information on how to keep backups of your keys.

info

If you are using Bee to manage your keys (not recommended - please use Bee Clef!). You must convert your keys in order to import into Metamask and other Ethereum wallets. You may use exportSwarmKeys to make the conversion.

Statestore#

The statestore directory retains information related to your node, including SWAP balances, info on peers, blocklisting and much more.

info

Although your statestore retains your node's state. It is only possible to restore from this if your node has not been connected in the meantime, as the blockchain and state may have desyncronised if your node was turned on in the meantime.

Localstore#

The localstore directory contains chunks that are pinned in your node, or are in your neighbourhood of responsibility.

Clef#

It is also important to back up Clef's stored data. This includes your sensitive key material, so make sure to keep this private and safe!

Ubuntu / Debian / Raspbian / CentOS Package Managers#

danger

Your keys represent your ability to access your gBZZ. Make sure to back up your keys directory in multiple places, so you can keep your gBZZs safe!

For Linux installations from package managers yum or apt, your Clef data directory is located at.

/var/lib/bee-clef/

Configuration files are stored in:

/etc/bee-clef/

Manual#

For a manual installation of Clef your data directory is normally located at:

~/.clef