Overview#
Restore Verification consists of several configuration elements that work together. The central element is the Restore Test, which brings together information about what should be tested, where the data should be restored, how it should be verified, and when the test should be started.
The following diagram shows these relationships.
The sections below provide only a general overview of the role of each element. Detailed configuration instructions for each of them are available on the corresponding documentation pages.
1. Backup Job / Restore Point / Scope#
This part is not a separate Restore Verification configuration object. It is part of the Restore Test definition and specifies the source data that should be tested.
Backup Job – defines which Bacula backup Job is subject to the test.
Restore Point – defines the backup version or point in time that should be restored.
Scope – defines the amount of data that should be restored and tested.
Together, these settings answer the question: What should be tested?
2. Restore Test#
The Restore Test is the central element of the Restore Verification configuration. Each Restore Test is associated with one Bacula backup Job and defines how data from that Job should be tested.
For example, if you want to test data from three different Backup Jobs named
docs, invoices, and dbs, you need to create three separate
Restore Tests.
A Restore Test brings together all settings required to perform the test, including the backup selection, Restore Destination, Verification Method, Verification Rules, and Restore Policy.
More information: Restore Tests
3. Restore Destination#
A Restore Destination defines the test environment where data is restored and verified. It includes the Bacula Client, restore path, restore mode, and the verification capabilities supported by the destination.
A Restore Test references a Restore Destination as one of its dependencies.
It answers the question: Where should it be tested?
More information: Restore Destination
4. Verification Method / Verification Rules#
The Verification Method determines how the restored data will be verified. Restore Verification currently provides two verification methods:
Rule-based Verification
Native Bacula Verify
Verification Rules are used with Rule-based Verification. They define which restored data should be checked and which checker conditions should be applied.
Together, these settings answer the question: How should it be verified?
More information: Verification Rules
5. Restore Policy#
A Restore Policy defines when and how a Restore Test is started.
A Restore Test references a Restore Policy as one of its dependencies.
It answers the question: When and how should it run?
More information: Restore Policy
Reusing configuration objects#
Restore Destinations, Verification Rules, and Restore Policies are reusable objects that can be shared by multiple Restore Tests.
This allows common settings to be defined once and reused wherever the same restore environment, verification criteria, or execution policy is needed. A Restore Test references these objects instead of duplicating their configuration, which helps keep the setup consistent and easier to maintain.