Lesson video coming soon. The player below contains a sample video, not this lesson. You can use the written lesson and slide guide now.

Open video on YouTube ↗

Download slide guide (PDF)10 pages · 4.6 MB

Work through the lesson

Use these explanations alongside the slide guide. Expand any section to read its full explanation.

Before the demonstration

• Your assigned responsibility
• The correct training record
• Evidence of the result

Today’s outcome
Custodian can plan recovery and recognize destructive operations without performing an unsafe change.

Read the full explanation

Before we begin, check these prerequisites: A07; authorized disposable recovery target for any live restore; otherwise tabletop. The intended outcome is: Custodian can plan recovery and recognize destructive operations without performing an unsafe change. Keep a note of the training identity and date so that you can recognize the result. We will pause before any action that your role or the exercise does not authorize.

Backup coverage

• Open Settings > Backup & recovery and inspect backup date/status and signing-assets coverage

In this step
Check the backup date, status and signing-assets coverage. Data recovery and later signature verification depend on the correct supporting assets. A filename alone does not prove that the required recovery material is present.

Read the full explanation

Open Settings > Backup & recovery and inspect backup date/status and signing-assets coverage. Check the backup date, status and signing-assets coverage. Data recovery and later signature verification depend on the correct supporting assets. A filename alone does not prove that the required recovery material is present. I will pause here so you can identify the control or result that tells us where we are in the workflow.

The scheduled runner

• Review schedule and explain the external scheduled runner dependency
• save/create only under approved rehearsal

In this step
The application schedule depends on an external runner. Saving a time in the page does not install an operating-system scheduler. Confirm the operational arrangement with the appliance owner before relying on scheduled backups.

Read the full explanation

Review schedule and explain the external scheduled runner dependency; save/create only under approved rehearsal. The application schedule depends on an external runner. Saving a time in the page does not install an operating-system scheduler. Confirm the operational arrangement with the appliance owner before relying on scheduled backups. I will pause here so you can identify the control or result that tells us where we are in the workflow.

The restore decision

• For a restore tabletop identify exact target, backup, safety copy and approval before the destructive action

In this step
This exercise is a tabletop discussion unless an isolated target has explicit approval. Name the target, chosen backup and safety copy before discussing the restore. A mistaken restore can replace current data.

Read the full explanation

For a restore tabletop identify exact target, backup, safety copy and approval before the destructive action. This exercise is a tabletop discussion unless an isolated target has explicit approval. Name the target, chosen backup and safety copy before discussing the restore. A mistaken restore can replace current data. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Recovery verification

• In an explicitly authorized isolated drill restore and verify row signatures/results
• otherwise use a sanitized previous drill capture

In this step
An authorized recovery drill includes result checks and row-signature verification. Current source includes the attendance event kind in the verification input. Record the actual drill outcome rather than treating a restored database as automatically verified.

Read the full explanation

In an explicitly authorized isolated drill restore and verify row signatures/results; otherwise use a sanitized previous drill capture. An authorized recovery drill includes result checks and row-signature verification. Current source includes the attendance event kind in the verification input. Record the actual drill outcome rather than treating a restored database as automatically verified. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Retention effects

• Review retention policy and its deletion/redaction effects
• do not execute it on live training/production records

In this step
Retention can delete selected data and redact location information. Explain the effect on future reporting and evidence before any approved run. Never execute retention merely to tidy the records used in a lesson.

Read the full explanation

Review retention policy and its deletion/redaction effects; do not execute it on live training/production records. Retention can delete selected data and redact location information. Explain the effect on future reporting and evidence before any approved run. Never execute retention merely to tidy the records used in a lesson. I will pause here so you can identify the control or result that tells us where we are in the workflow.

Common problems

• Assuming schedule UI alone installs an OS scheduler
• restoring the wrong database
• separating signing keys from backups
• running retention to tidy a demonstration

A useful support report
The task and record
The expected result
The actual message
The authorized next step

Read the full explanation

Let us consider the mistakes that can disrupt this workflow. Assuming schedule UI alone installs an OS scheduler; restoring the wrong database; separating signing keys from backups; running retention to tidy a demonstration. Describe what you expected and what the application actually showed before choosing a remedy. Preserve the relevant record and error. The role responsible for a review or configuration change should make that decision. Do not borrow broader access simply to finish the exercise.

Guided practice

• Tabletop: choose a backup, explain signing-key custody, recovery validation and retention impact; identify where to stop for authorization

Evidence to show
The correct training case
The result or permitted decision
Your explanation of the next step

Read the full explanation

Now it is your turn. Tabletop: choose a backup, explain signing-key custody, recovery validation and retention impact; identify where to stop for authorization. Work within the assigned training role. When you finish, show the result and explain which identity and date it belongs to. If the exercise includes a restricted action, explain the decision and its authorized owner rather than carrying it out without approval.

Practice debrief

• Correct context and permitted action
• A result you can trace
• A clear next step if blocked

Expected result
Custodian can plan recovery and recognize destructive operations without performing an unsafe change.

Read the full explanation

The expected outcome is: Custodian can plan recovery and recognize destructive operations without performing an unsafe change. Walk me through the record you used and the result you found. Explain these workflow checkpoints in order: Open Settings > Backup & recovery and inspect backup date/status and signing-assets coverage. Review schedule and explain the external scheduled runner dependency; save/create only under approved rehearsal. For a restore tabletop identify exact target, backup, safety copy and approval before the destructive action. In an explicitly authorized isolated drill restore and verify row signatures/results; otherwise use a sanitized previous drill capture. Review retention policy and its deletion/redaction effects; do not execute it on live training/production records. For an exception, name the evidence you would preserve and the person with authority to take the next action.