Rullst AcademyRullst Academy/Lesson
From application to release with Rullst · Lesson 10 / 12

Prove recovery without risking the original

“I have a backup” becomes evidence when you can open recovered data and explain what was left out.

Learning paths30 min

Let's discover together

  1. 1

    Confirm the previous names: original missions.db, copy backup-01.db. Choose restored-01.db, which does not yet exist. Stop the board before switching the file it uses.

  2. 2

    Run restore and verify below. Restore uses the same validated snapshot mechanism and rejects any existing destination, including the original. It does not restore over a running service.

  3. 3

    Set MB_DATABASE=restored-01.db using your OS command in README and start serve. Check titles and priorities, not just the count. The mission created after backup should be absent.

  4. 4

    Stop, set MB_DATABASE=missions.db again and check all three missions remain in the original. Do not create a fourth mission in the restored file to pretend it was recovered. Record actual differences.

  5. 5

    Repeat restore using the same destination and observe refusal; then confirm existing data is still readable. The report should also state what the backup did not contain and when restoration was rehearsed.

From reasoning to execution

The core path runs on your computer with fictional data. Podman, Quadlet and Caddy are optional extensions; no domain purchase or cloud subscription is needed. This lab is not ready for public writes.

Read the steps before running anything. The commands below are a reference; README.md explains your OS syntax and LAB.md contains the sequence. The site does not run these commands for you.

cargo run --locked -- restore backup-01.db restored-01.db
cargo run --locked -- verify restored-01.db
My evidence record

Deliver a table for original, backup and restored: fictional names, expected content, observed content and verify result. Explain the interval of changes not recovered.

Separate prediction, execution and observed result. Record “not executed” when the environment is missing. Site progress does not validate real deployment or grant professional certification.

My files and GitHub

Official links and next step

✦
YOUR MISSION

Restore to a new file, inspect contents and demonstrate the original was unchanged.

Now it's your turn

Discovery workshop

Decide using evidence

The original has 3 missions; the snapshot had 2. Restoration used a separate file.
Build your answers and check when you are ready.
A moment to understand

Why restore to another file first?

I need a hint

Isolated recovery lets you compare states. The third mission’s absence is expected: it was created after the snapshot.

Loading your journey…

Take it with you

Deliver a table for original, backup and restored: fictional names, expected content, observed content and verify result. Explain the interval of changes not recovered.

At your own pace

My files and GitHub

Every lesson can become your own record: code, notes or a practice plan. Saving a file to GitHub is optional and does not change your XP.

Student guide

The editor and downloads open when this lesson is available to your account. Check access below or return to the track map.

Checking your access to this lesson…

Rullstpetbot

AI can make mistakes. Check the lesson material.