Skip to content

Conversation

@Villaquiranm
Copy link
Contributor

@Villaquiranm Villaquiranm commented Dec 8, 2025

Working on top of #3946
Fixes #1827

Description (thanks @n0izn0iz )

  • Adds a grpc service called Backup in the tendermint2 node that allows to stream blocks efficiently
    It has a single method StreamBlocks that take a start and end height. If end height is 0 it will stream to the latest height. It is disabled by default and require enabling it in the config.toml
  • Adds a contribs binary named tm2backup that pulls blocks from the backup service and store them in compressed 100-blocks files. It takes a start and end height as well as supporting resuming.
    The tar format was chosen to bundle blocks since it's widely supported and efficient. The zstandard format was chosen for compression because it's fast, has a good compression ratio and is widely supported.
  • Adds a restore subcommand to the gnoland binary that allows to replay blocks from a backup. It takes the options from the start subcommand as well as the backup directory and an optional end height.
    It will start at the current node height + 1.

The restore command can only restore at backupEndHeight-1 because I did not figure a way to commit block n without block n+1. I'd gladly take ideas on how to do that.

The backup is fast enough for now IMO (< 20min for test5 on my macbook) but can be optimized because it's not parallelized.
The restore bottleneck seems to be the gnovm currently but I would need to profile to be sure.

How to create a backup

  • Enable the backup service in your node's config.toml
[backup]
laddr = "localhost:4242"
  • (Re-)Start your node
  • Run the tm2backup command
cd contribs/tm2backup
tm2backup -o blocks-backup -remote http://localhost:4242

How to create a node from a backup

  • Get the genesis file, for example:
wget https://example.com/genesis.json
  • Run the restore command
gnoland restore --lazy --backup-dir ../contribs/tm2backup/blocks-backup
  • Start your node
gnoland start

n0izn0iz and others added 30 commits March 6, 2025 22:37
Signed-off-by: Norman <[email protected]>
Signed-off-by: Norman <[email protected]>
Signed-off-by: Norman <[email protected]>
Signed-off-by: Norman <[email protected]>
Signed-off-by: Norman <[email protected]>
Signed-off-by: Norman <[email protected]>
Signed-off-by: Norman <[email protected]>
@github-actions github-actions bot added 📦 🤖 gnovm Issues or PRs gnovm related 📦 🌐 tendermint v2 Issues or PRs tm2 related 📦 ⛰️ gno.land Issues or PRs gno.land package related 🐳 devops 🐹 golang Pull requests that update Go code 🛠️ gnodev labels Dec 8, 2025
@Villaquiranm Villaquiranm changed the title Backup restore feat: blocks backup / restore #3946 Dec 8, 2025
@Villaquiranm Villaquiranm changed the title feat: blocks backup / restore #3946 feat: blocks backup / restore Dec 8, 2025
@Gno2D2
Copy link
Collaborator

Gno2D2 commented Dec 8, 2025

🛠 PR Checks Summary

🔴 Pending initial approval by a review team member, or review from tech-staff

Manual Checks (for Reviewers):
  • IGNORE the bot requirements for this PR (force green CI check)
Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🔴 Pending initial approval by a review team member, or review from tech-staff

☑️ Contributor Actions:
  1. Fix any issues flagged by automated checks.
  2. Follow the Contributor Checklist to ensure your PR is ready for review.
    • Add new tests, or document why they are unnecessary.
    • Provide clear examples/screenshots, if necessary.
    • Update documentation, if required.
    • Ensure no breaking changes, or include BREAKING CHANGE notes.
    • Link related issues/PRs, where applicable.
☑️ Reviewer Actions:
  1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.
📚 Resources:
Debug
Automated Checks
Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: Villaquiranm/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🔴 Requirement not satisfied
└── 🔴 If
    ├── 🔴 Condition
    │   └── 🔴 Or
    │       ├── 🔴 At least one of these user(s) reviewed the pull request: [jefft0 leohhhn n0izn0iz notJoon omarsy x1unix] (with state "APPROVED")
    │       ├── 🔴 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🔴 This pull request is a draft
    └── 🔴 Else
        └── 🔴 And
            ├── 🟢 This label is applied to pull request: review/triage-pending
            └── 🔴 On no pull request

Manual Checks
**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

  • Any user with comment edit permission

@Villaquiranm Villaquiranm marked this pull request as ready for review December 10, 2025 17:55
@Gno2D2 Gno2D2 added the review/triage-pending PRs opened by external contributors that are waiting for the 1st review label Dec 10, 2025
Comment on lines +81 to +95
for height := startHeight; height <= endHeight; height++ {
block := b.store.LoadBlock(height)
if block == nil {
return fmt.Errorf("block store returned nil block for height %d", height)
}

data, err := amino.Marshal(block)
if err != nil {
return err
}

if err := stream.Send(&backuppb.StreamBlocksResponse{Data: data}); err != nil {
return err
}
}
Copy link
Contributor Author

@Villaquiranm Villaquiranm Dec 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ajnavarro coment from #3946 (comment)

Some things to comment on this:

  • Fetching blocks one by one from the K/V storage is extremely slow. We need to use iterators for that.
  • We are getting byte arrays from the K/V storage, the LoadBlock method is unmarshalling that to a Block struct, after that we marshal again blocks to a byte array. After that, we unmarshal a StreamBlocksResponse into protobuf... That's a lot of unnecessary processing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After my first tests:
current implementation:
go run main.go -o blocks-backup -remote http://localhost:4242 6.60s user 1.93s system 67% cpu 12.581 total
go run main.go -o blocks-backup -remote http://localhost:4242 7.14s user 2.08s system 68% cpu 13.543 total (over 78.84k blocks)

I will try to improve it with your suggestions, I'll keep you updated

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On commit 3382675
We removed the one pair of marshal/unmarshal
and we got:
go run main.go -o blocks-backup -remote http://localhost:4242 3.57s user 2.01s system 40% cpu 13.702 total
Around 2x faster

Comment on lines +393 to +397
if !skipVerification {
if err := state.Validators.VerifyCommit(
chainID, firstID, first.Height, second.LastCommit); err != nil {
return fmt.Errorf("invalid commit (%d:%X): %w", first.Height, first.Hash(), err)
}
Copy link
Contributor Author

@Villaquiranm Villaquiranm Dec 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from @ajnavarro comment #3946 (comment)

Can we add a flag to skip commit verification? If we trust the backup, it can improve import speed.

}
}

bcR.store.SaveBlock(first, firstParts, second.LastCommit)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from @ajnavarro comment #3946 (comment):

We have to use insert Batches here. It will be an order of magnitude faster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🐳 devops 🛠️ gnodev 🐹 golang Pull requests that update Go code 📦 🌐 tendermint v2 Issues or PRs tm2 related 📦 ⛰️ gno.land Issues or PRs gno.land package related 📦 🤖 gnovm Issues or PRs gnovm related review/triage-pending PRs opened by external contributors that are waiting for the 1st review

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

[chain] Backup / Restore Functionality

3 participants