How do I migrate my node to a new device?

To migrate your Node to a new drive or computer, you first need to copy both the contents of your storage folder, as well as your identity folder to the new location.

ARM-based OS

Your identity folder is located in: $Env:APPDATA/Storj/Identity/storagenode

To migrate your Windows storage node you can follow this guide: How to migrate the Windows GUI node from one physical location to another? The only difference - you do not need to share disks, since they are available locally, just use the local paths.

Also, you can enable WSL, install Ubuntu from the Microsoft store and use the Migrating with rsync guide. In this case your drives are mounted automatically. For example, D: disk will be mounted to the /mnt/d .


Your identity folder is located in: ~/.local/share/storj/identity/storagenode

Migrating with rsync

ARM-based OS

On Raspberry Pi, your identity folder is located in (the path may be different for other ARM platforms): /home/pi/.local/share/storj/identity/storagenode

Migrating with rsync


Your identity folder is located in: /Users/USER/Library/Application Support/Storj/identity/storagenode

Migrating with rsync

Migrating with rsync

We will assume that your parameters look like this:

  • the source folder where the existing identity is located is ~/.local/share/storj/identity/storagenode;

  • the source folder where the existing stored data is located is /mnt/storagenode/storage;

  • the destination folder the existing identity will be copied to is/mnt/storagenode-new/identity;

  • the destination folder the existing stored data will be copied to is /mnt/storagenode-new/storage.

To migrate your identity and data to the new location, you can use the rsync command (please, replace the example paths mentioned above to your own!):

  1. Open a new terminal

  2. Keep your original storage node running

  3. Copy the identity:

rsync -aP ~/.local/share/storj/identity/storagenode /mnt/storage-new/identity

4. Copy the data

rsync -aP /mnt/storagenode/storage /mnt/storagenode-new/storage

5. Repeat running the data copying command (step 4.) a few more times until the difference would be negligible, then

6. Stop the storage node (see How do I shutdown my node for system maintenance?)

7. Remove the old container

docker rm storagenode

8. Run the copying command with a --delete parameter to remove deleted files from the destination:

rsync -aP --delete /mnt/storagenode/storage /mnt/storagenode-new/storage

9. After you copied over all the necessary files, update your --mount parameters in your docker run command. For our example, it will look like this (we only show a partial example of the new--mount parameter lines, not the entire docker run command!):

--mount type=bind,source=/mnt/storagenode-new/identity,destination=/app/identity \
--mount type=bind,source=/mnt/storagenode-new,destination=/app/config \

Please, note - we intentionally specified/mnt/storagenode-new as the data source in the --mount parameter and not /mnt/storagenode-new/storage because the storagenode docker container will add a subfolder called/storage to the path automatically. So please, make sure that your data folder contains a storage subfolder with all the data inside (blobs folder, database files, etc.), otherwise the node will start from scratch since it can't find the data in the right subfolder and will be disqualified in a few hours.

Migrating from Docker CLI to a GUI Install on Windows?

1. Make sure the Docker version is stopped and removed.

2. Point to the same exact storage folder where you were previously storing the data.

Do NOT copy the path from the old config.yaml of your Docker node where the storage subfolder was not explicitly included in the path.

3. Verify the complete path to the correct storage folder on your hard drive. If you choose a different folder, your previously stored data will not be recognized, and your node will be disqualified.