Snapshot Instructions for Heimdall and Bor

Archive Matic Mainnet
1

When setting up a new Sentry, Validator, or Full Node server, it is recommended you use a snapshot for faster syncing without having to sync over the network. Using snapshots will save you several days for both Heimdall and Bor.

Please refer to https://snapshots.matic.today for the latest snapshots.

Using Snapshots

Heimdall

First, you need to set up your node with pre-requisites as per the node setup guide. Before you start services for Heimdall to sync, follow the below steps to use snapshot:

Download the Snapshot to your VM. To download the Snapshot Tar file to your VM you can run the following command

wget -c <Snapshot URL>

For example:

wget -c https://matic-blockchain-snapshots.s3-accelerate.amazonaws.com/matic-mainnet/heimdall-snapshot-2021-09-12.tar.gz

This will download the Snapshot of Heimdall.

Now, to unpack the Tar file in the Heimdall Data directory run the following command. You need to ensure that you’re running this command before you start the Heimdall service on your node. If your Heimdall service has started, please stop and then run the below command. Once unpacking is complete you can start the Heimdall service again.

tar -xzvf <snapshot file> -C <HEIMDALL_DATA_DIRECTORY>

For example:

tar -xzvf heimdall-snapshot-2021-09-12.tar.gz -C ~/.heimdalld/data/

Note that if your Heimdall data directory is different then please mention that directory name correctly. When this command completes, you can delete the tar file to reclaim space.

Bor

First, you need to set up your node with pre-requisites as per the node setup guide. Before you start services for Bor to sync, follow the below steps to use snapshot:

Download the Snapshot to your VM. To download the Snapshot Tar file to your VM you can run the following command

wget -c <Snapshot URL>

For example:

wget -c https://matic-blockchain-snapshots.s3-accelerate.amazonaws.com/matic-mainnet/bor-pruned-snapshot-2021-09-08.tar.gz

Now, to unpack the Tar file in the Bor Data directory run the following command. You need to ensure that you’re running this command before you start the Bor service on your node. If your Bor service has started, please stop and then run the below command. Once unpacking is complete you can start the Bor service again.

tar -xzvf <snapshot file> -C <BOR_DATA_DIRECTORY>

For example:

tar -xzvf bor-pruned-snapshot-2021-09-08.tar.gz -C ~/.bor/data/bor/chaindata

Note that if your bor data directory is different then please mention that directory name correctly. When this command completes, you can delete the tar file to reclaim space.

2 Likes
2

This might be a better way to download and extract if you’re limited on storage space.
wget [snapshot-link] -O - | tar -xzf - -C [data-directory]

2 Likes
3

What’s the difference between the pruned and fullnode snapshot variants?

4 
Jan 24 09:42:34 ip-10-1-1-148 heimdalld[87977]: E[2022-01-24|09:42:34.262] Unable to get checkpoint                     module=checkpoint error="No checkpoint found in buffer"

I get these error logs in heimdalld service. Is it normal?

1 Like
6

@anon63684144 is a scammer.

7

You will need to provide more info, but I don’t think this is a problem if the app is still in sync. The Discord is a better place to ask a question like this.

8

Note: the two tarballs are over 250GB, had to increase my partition size in accommodate.

dpeng@matic:~$ ls -lh *.gz
-rw-r–r-- 1 dpeng dpeng 141G Mar 16 21:32 bor-pruned-snapshot-2022-03-13.tar.gz
-rw-r–r-- 1 dpeng dpeng 119G Mar 16 21:07 heimdall-snapshot-2022-03-13.tar.gz

9

676GB? wget --spider https://matic-blockchain-snapshots.s3-accelerate.amazonaws.com/matic-mainnet/bor-pruned-snapshot-2022-04-10.tar.gz
Spider mode enabled. Check if remote file exists.
Length: 726356804767 (676G) [application/x-tar]
Remote file exists.