Snapshot before a move

Take a local copy of this project's graph and its ledger before anything moves. Nothing schedules it, prunes it or sends it anywhere.

Before you start

• Price and run the first pass, and know it landed
• The graph has to be running. A snapshot reads every node and edge out of it.

Configuration page

Command line

1. Read what has been snapshotted here:

   revetly snapshot list
   

   no snapshot taken yet — `revetly snapshot` takes one
   

2. Take one, named for the move it comes before:

   revetly snapshot --label before-host-move
   

   snapshot <STAMP> — …
   

   If the engine container is running, Revetly refuses this on the host and prints the same command through docker compose exec -T revetly to run.

3. Read it back among the snapshots taken here:

   revetly snapshot list
   

   <STAMP> [before-host-move]  <AGE>  group '<NAMESPACE>'  corpus revision <REVISION>  …
   

Troubleshooting

• Nothing has been read into this project yet. There is no ledger to copy, so run a pass before you snapshot.
• A read pass is holding the lock. A snapshot taken mid-pass would hold a ledger ahead of its graph, so it is refused rather than queued. Take it again once the pass is done.

Next steps

• Move an instance
• When the ledger and the graph disagree, and how the corpus comes back