Production · corporate video shoot cards and drives
corporate video shoot: check a backup size mismatch
Why is the backup from the corporate video shoot smaller than the source?
Short answer
Not always missing footage: backups made with filters often leave out sidecar folders, XML metadata or thumbnails the camera wrote, which lowers the total. Compare clip counts and per-file byte sizes instead of folder totals. If a video clip itself is smaller than on the card, copy it again from the card.
The situation
A copy exists, but byte totals or file counts do not match the recorded cards.
A backup that reports fewer bytes than the cards is worth checking, but it is not yet evidence of loss. What differs is often everything around the video: sidecar folders, metadata files and thumbnails the camera wrote and the backup rule filtered out.
01 / Diagnose
Work out what actually disappeared
Backup jobs on corporate projects are usually configured by file type or by folder, which excludes camera structures such as CLIPINF, XML sidecars and proxy directories. Add differing cluster sizes between card and archive drive, plus the odd clip that failed silently because the destination was full or formatted FAT32, and the totals drift apart without any footage being lost.
Hidden sidecars, failed large files, filters and allocation errors can all change totals. For corporate video shoot, this matters because the corporate video shoot combines several sources, takes and handoff steps that must be reconciled as a set
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Change nothing on either side yet; leave the cards unformatted and the backup folder exactly as the job left it.
- 2
Generate a recursive file list with names and byte sizes for each card and for the archive, then compare those lists instead of the totals.
- 3
Read the backup job's log for skipped items and check its filter rules against the folder structure the camera actually writes.
- 4
Copy every difference directly from the card, sidecars included, and verify the byte size of each copied file afterwards.
Do not clear the cards because the archive looks complete enough, and do not trust a progress dialog that ended without an error summary. Corporate footage often has to be reproduced years later, and a silently skipped clip only becomes visible when nobody can shoot it again.
03 / Choose the method
Match the tool to the source
For stable, readable exFAT, NTFS and FAT16/FAT32 or uncompressed IMG, DD, RAW and BIN images.
Unconfirmed exports are marked .UNVERIFIED.
This is a verification task, not a recovery task; no software licence is required to compare and copy. Recovery only enters the picture for material already deleted from a readable exFAT, NTFS or FAT16/FAT32 volume, and it never writes to the source it reads.
04 / Verify
Check the recovered content, not just its name
The comparison is finished when every file name on a card has a counterpart in the archive with the same byte size, and when the remaining difference is explained by allocation only. Open the largest clip from the archive and confirm it plays to its final frame.
Keep the source until two verified copies exist. One working preview is not enough.
Sources and technical references
FAQ
Questions about this recovery case
Can corporate video shoot cards and drives be recovered in this situation?+
A backup that reports fewer bytes than the cards is worth checking, but it is not yet evidence of loss. What differs is often everything around the video: sidecar folders, metadata files and thumbnails the camera wrote and the backup rule filtered out. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not clear the cards because the archive looks complete enough, and do not trust a progress dialog that ended without an error summary.
Does scanning write to my memory card?+
Your memory card is only read. Nothing is saved to it.
How do I know whether the result is complete?+
The comparison is finished when every file name on a card has a counterpart in the archive with the same byte size, and when the remaining difference is explained by allocation only.