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

Administrators need to verify that restored data matches the source archive by applying checksum validation, but the current Automated backup restoration validation feature only offers a global on/off switch that is undocumented in the management console and unavailable per backup set.

In releases before 2.4 the feature omits checksum validation entirely, while version 2.4 and later expose optional validation only through raw configuration files, leaving no way to differentiate between full and incremental backups or to enforce the check through role‑based permissions.

• Can the checksum validation scope be set individually for full versus incremental backup sets?
• Does enabling per‑set validation require administrative privileges beyond the standard restore role?
• How is this setting exposed in version 2.4 and later without relying on undocumented file edits?