A backup you can't check isn't a backup.
Backing up isn't enough: you also need to know the copy is intact — and, when the day comes, that you can really rely on it. Ozorys checks, and answers you clearly rather than with a vague message.
The silent danger
A backup can look like it's there and yet no longer read back: an interrupted transfer, a flipped byte on a tired disk, a file truncated during copying. The worst case isn't the missing backup — it's the false backup, the one you believe in until the day you need it.
That's why Ozorys doesn't just write a copy: it knows how to check it. Verifying integrity turns “I think it's fine” into “I know it's fine”.
A corrupted copy reassures you wrongly: it takes the place of a real backup. A frank warning today beats a nasty surprise on the day of need.
The signature that doesn't lie
You met it in module 18: the “GCM” in AES-256-GCM adds a signature to every block. If a single byte were altered, that signature would no longer match, and Ozorys would detect it at once. The system would rather refuse tampered data than silently show you nonsense.
Integrity and confidentiality thus advance together: the very mechanism that makes your data unreadable to others also makes it impossible to falsify without being spotted.
An undetected alteration is poison; a detected one is merely a warning. Ozorys always chooses the warning: it tells you rather than misleads you.
Codes that say what
When something is off, Ozorys doesn't leave you staring at a mysterious “error”. It answers with a precise failure code: incomplete file, key that doesn't match this backup, incompatible format. Every case has its cause — and therefore its fix.
Knowing precisely what's wrong is already half the fix: you retry the right strand, re-export the file, or check you're restoring the right vault.
Faced with a failure code, note it down and follow the lead it gives rather than starting over at random. A precise diagnosis saves you what matters most: time and peace of mind.
Trust, but verified
Checking isn't something you have to remember to do: it runs at opening and at restoring, discreetly. You never discover a problem at the worst moment, because Ozorys would have flagged it long before.
That's this module's quiet promise: the net from module 19 isn't merely strung up, it's been tested. What remains is where to keep the final strand — the paper — and that's the next module.
Let's check it stuck
Six questions, marked instantly. Your answers never leave this page.
1. What's the worst case for a backup?
A corrupted copy takes the place of a real one: hence the importance of checking, not just copying.
2. How does Ozorys detect that a block has been altered?
The same mechanism that encrypts (AES) also authenticates (GCM): altering without being spotted is impossible.
3. Faced with tampered data, Ozorys…
Detecting beats enduring: it tells you rather than misleads you.
4. If there's a problem, Ozorys shows…
A clear diagnosis points to the cause — and therefore the fix.
5. When does the integrity check run?
You never discover a problem at the worst moment: it would already have been flagged.
6. At Ozorys, integrity and confidentiality…
What makes your data unreadable to others also makes it impossible to falsify without being spotted.
Today's challenge
Run a check on your backup in cold blood, today. If it all comes back green, you have proof your net will hold; if a code appears, you'll know exactly what to fix — long before you need it.