README.md

vdc bootable-OS backup (encrypted)

Bit-exact, bootable image of a hybrid BIOS+UEFI Ubuntu cloud disk (originally device vdc), captured as used-blocks-only, zstd-compressed, and AES-256 encrypted. Each partition is stored separately; the GPT is backed up so the target disk is repartitioned identically on restore.

Encryption

Every *.gpg file is GnuPG symmetric AES-256 (compressed with zstd first). Passphrase: 60-char secret, sha256 fingerprint starts ff23c993e47836f2. Without the passphrase these files are unrecoverable.

Contents

• vdc.sgdisk.gpt GPT partition-table backup (sgdisk) — restores identical layout + PARTUUIDs
• vdc.sfdisk.txt human-readable partition dump
• vdc1.img.zst.gpg partition 1: BIOS-boot (4 MiB)
• vdc2.img.zst.gpg partition 2: ESP / /boot/efi (vfat)
• vdc3.ext4.img.zst.gpg partition 3: /boot (ext4, used blocks)
• vdc4.ext4.img.zst.gpg partition 4: root / (ext4, used blocks) — approx 984G compressed+encrypted
• restore.sh one-command restore to a target disk
• SHA256SUMS integrity checksums of every file above

Restore

1. Download the bundle (e.g. hf buckets sync hf://buckets/AntonioLopardo/Backup ./restore-dir).
2. sha256sum -c SHA256SUMS to verify integrity.
3. sudo ./restore.sh /dev/TARGET_DISK — prompts for the passphrase, then rebuilds the GPT and writes every partition (gpg -d | zstd -d | dd).
4. The restored disk is a bit-exact bootable clone of the original vdc. It keeps vdc's original UUIDs, so don't run it alongside the original vdc.

Manual per-partition restore (if not using restore.sh):

sgdisk --load-backup=vdc.sgdisk.gpt /dev/TARGET
gpg -d vdc4.ext4.img.zst.gpg | zstd -d --long=31 | dd of=/dev/TARGET4 bs=64M conv=fsync
# ...repeat for vdc1/vdc2/vdc3 -> TARGET1/2/3

Generated Wed Jul 15 23:45:14 UTC 2026.