Carbon Data partial file restore verification limits

Carbon Data uses a proprietary backup format with a bootable recovery environment for system state restoration. Documentation describes checksum or hash comparisons during the read/write cycle of restoration and filesystem consistency checks on first reboot after a full image restore.

The design goal is to understand verification coverage when restoring individual files from an incremental backup chain versus a full disk image. The constraint is that partial restores of specific files may be subject to different verification constraints than full image restores, and restoration to different hardware may affect bootability.

Is block-level checksum validation applied to each file extracted in a partial restore? Is an incremental chain verified end-to-end before file extraction, or is verification limited to the restore path used for full images? What verification status is surfaced to the operator after a partial file restore completes?