Verified Backups for Object Storage: Manifests, Multipart Uploads and Restore Checks
The article argues that a backup should be treated as a verifiable object paired with a restore contract, not merely a file that a scheduler reports as successful. It recommends streaming database dumps to private object storage alongside an immutable manifest recording the key, byte length, checksum, timestamp, schema version and included partitions. Backups should live in a separate namespace from private uploads, and presigned download links should be issued only after authorization because they act as bearer credentials. A backup counts as complete only after read-after-write verification confirms the length and checksum, and the author suggests bounded retries, concurrency limits and idempotent commits for multipart transfers. The piece also illustrates the risk with a quiet failure, in which a full ephemeral disk masked a truncated archive until a restore check caught the mismatch.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in