Restoring aptos node using a backup

[lukas-vc]

Discord user ID

lukas5804

Describe your question in detail.

Using Aptos CLI to perform a db restore.

Running the command as:

aptos node bootstrap-db \
  --ledger-history-start-version 6668999950 \
  --command-adapter-config /gcs.yaml \
  --target-db-dir /data

(the same if I add a target version, e.g, --target-version 6786836197)

Getting OOM when it finishes the first step of restoring epochs and enters the step of restoring transactions.
The first step operates on ~2GB. The transaction step, in a couple of seconds, increases to 32GB, causing an OOM issue.

2025-06-16T10:05:30.214138Z [tokio-runtime-worker] INFO storage/backup/backup-cli/src/backup_types/epoch_ending/restore.rs:407 Epoch history recovered in 3555.20 seconds
2025-06-16T10:05:30.214507Z [tokio-runtime-worker] INFO storage/backup/backup-cli/src/backup_types/epoch_ending/restore.rs:342 epoch history restore succeeded.
2025-06-16T10:05:30.214515Z [tokio-runtime-worker] INFO storage/backup/backup-cli/src/coordinators/restore.rs:238 Start restoring DB from version 6727653019 to tree snapshot version 6785964492
2025-06-16T10:05:30.214532Z [tokio-runtime-worker] INFO storage/backup/backup-cli/src/backup_types/transaction/restore.rs:262 transaction restore started.
2025-06-16T10:05:45.286654Z [tokio-runtime-worker] INFO storage/aptosdb/src/state_store/mod.rs:944 Write usage at version 6727663018, Tracked { items: 199914629, bytes: 95632726923 }.
2025-06-16T10:05:52.391763Z [tokio-runtime-worker] INFO storage/backup/backup-cli/src/backup_types/transaction/restore.rs:564 KV replayed. {"accumulative_tps":797,"version":6727663018}
2025-06-16T10:05:53.594507Z [tokio-runtime-worker] INFO storage/aptosdb/src/state_store/mod.rs:944 Write usage at version 6727673018, Tracked { items: 199914775, bytes: 95632786963 }.
2025-06-16T10:06:00.361037Z [tokio-runtime-worker] INFO storage/backup/backup-cli/src/backup_types/transaction/restore.rs:564 KV replayed. {"accumulative_tps":974,"version":6727673018}
2025-06-16T10:06:01.720613Z [tokio-runtime-worker] INFO storage/aptosdb/src/state_store/mod.rs:944 Write usage at version 6727683018, Tracked { items: 199914995, bytes: 95632865317 }.
2025-06-16T10:06:09.466080Z [tokio-runtime-worker] INFO storage/backup/backup-cli/src/backup_types/transaction/restore.rs:564 KV replayed. {"accumulative_tps":1012,"version":6727683018}
2025-06-16T10:06:10.671053Z [tokio-runtime-worker] INFO storage/aptosdb/src/state_store/mod.rs:944 Write usage at version 6727693018, Tracked { items: 199915288, bytes: 95632972437 }.

What error, if any, are you getting?

No response

What have you tried or looked at? Or how can we reproduce the error?

No response

Which operating system are you using?

Linux (Ubuntu, Fedora, Windows WSL, etc.)

Which SDK or tool are you using? (if any)

Aptos CLI

Describe your environment or tooling in detail

No response

[sionescu]

The DB restore tool requires large amounts of RAM. I suggest trying with the prod specs of 64G.

[lukas-vc]

I increased the amount of RAM to 128 GB. That works better, but I'm still getting OOM after around an hour of the transaction replay step.