WEBVTT

1
00:00:00.000 --> 00:00:04.300
Recovery is easiest when you practice it before
anything goes wrong.

2
00:00:04.300 --> 00:00:09.774
FusionWall keeps important state on this
computer, including policies, connections,
protected mappings, and receipts.

3
00:00:09.774 --> 00:00:20.720
In this tutorial, I will show you the recovery
habits that matter: create an encrypted recovery
point, protect its passphrase, verify the file,
and rehearse the restore path.

4
00:00:22.320 --> 00:00:26.155
FusionWall is local-first, but local does not
mean disposable.

5
00:00:26.155 --> 00:00:34.251
Your workspace, policies, encrypted mappings,
and proof ledger are part of the authority you
have built on this computer.

6
00:00:34.251 --> 00:00:43.200
A recovery point protects that state so a device
problem does not turn into a loss of evidence or
operating history.

7
00:00:44.800 --> 00:00:49.004
Open System and Recovery, then create an
encrypted recovery point.

8
00:00:49.004 --> 00:00:53.629
Choose a strong passphrase that is different
from your sign-in password.

9
00:00:53.629 --> 00:00:56.572
FusionWall cannot recover a lost backup
passphrase.

10
00:00:56.572 --> 00:01:04.560
Store it away from this computer, and do not
keep it in the same place as the backup file.

11
00:01:06.160 --> 00:01:10.559
After the backup is created, move the encrypted
file to storage you control.

12
00:01:10.559 --> 00:01:14.620
If the work matters, keep another protected copy
in a separate place.

13
00:01:14.620 --> 00:01:19.358
The backup is encrypted, but you should still
handle it as important business material.

14
00:01:19.358 --> 00:01:23.080
One copy on the same device is not a recovery
plan.

15
00:01:24.680 --> 00:01:30.356
Use the verification control to confirm that
FusionWall can read and validate the recovery
package.

16
00:01:30.356 --> 00:01:34.897
Then follow the restore-check workflow so you
understand the offline owner steps.

17
00:01:34.897 --> 00:01:39.059
A rehearsal should confirm the path without
overwriting the active installation.

18
00:01:39.059 --> 00:01:43.600
The first time you learn recovery should not be
during a crisis.

19
00:01:45.200 --> 00:01:50.446
Create a fresh recovery point after meaningful
changes to policies, connections, workflows, or
evidence.

20
00:01:50.446 --> 00:01:53.069
Also make one before a major update.

21
00:01:53.069 --> 00:01:58.689
Periodically verify the newest copy and retire
old copies according to your own retention
needs.

22
00:01:58.689 --> 00:02:03.560
Recovery stays dependable only when the backup
reflects the system you actually use.

23
00:02:05.160 --> 00:02:09.096
The reliable pattern is separate, encrypted,
verified, rehearsed, and current.

24
00:02:09.096 --> 00:02:18.150
Keep the passphrase away from the file, keep the
file away from the computer, and test the
restore path while everything is healthy.

25
00:02:18.150 --> 00:02:22.480
That turns recovery from a hopeful promise into
an owner-controlled practice.