Automated backup restoration validation missing per‑backup‑set checksum scope

Answer

No – the current Automated backup restoration validation feature does not expose a per‑backup‑set option to enable checksum validation separately for full versus incremental sets. The only available control is a global on/off switch; in releases 2.4 and later the switch can be toggled by editing an undocumented raw configuration file, but there is no documented UI or API to set the scope per backup set or to restrict the change to a specific role.

Likely explanation

When a feature is first shipped as a simple global toggle, the underlying code often reads a single Boolean flag. Later releases may add a raw‑config override so advanced users can flip the flag without waiting for a UI, but the configuration schema still only contains a single key (e.g., validation.checksum.enabled) that applies to all backup sets. Until the schema is extended to support per‑set keys (e.g., validation.checksum.full.enabled and validation.checksum.incremental.enabled) or a dedicated API, the product cannot differentiate scope.

Confirmed general facts

• Full and incremental backups legitimately need different checksum handling because an incremental set can only be verified against its chain back to the last full backup.
• Undocumented configuration options are not a supported enforcement mechanism; until a setting appears in documented UI/API with role‑based access control, it cannot be relied on for compliance or delegated administration.

Steps to verify the current state on your system

1. Locate the product’s configuration directory (commonly /etc// or /opt//conf).
2. Search for validation‑related keywords, for example:

   grep -r -i "checksum\|validation" /etc//

3. If the only match is a single global key (e.g., validation.checksum.enabled), then per‑set scope is not available.
4. Attempt to change that key with an account that has only the standard restore role; if the change is rejected or ignored, the operation likely requires administrative privileges.

Missing diagnostic detail

To give a definitive answer about whether per‑set validation can be added via a supported API, we need the exact product name and version you are running. Please provide that information so the documentation can be consulted directly.