OWNER-MANAGED BACKUP & RECOVERY
Keep what matters.
Have a way back.
DockerBackup saves selected Docker application data and configuration as encrypted backups in Google Drive, ready to recover on a replacement host.
A personal utility operated by Chris Clark for his own infrastructure.
Application data & configuration
Authenticated encrypted package
Private, offsite recovery copies
Validated data & rebuilt applications
The recovery key is kept separately from Drive.
Confirm the stored package matches the local copy.
Prune eligible older copies after a verified upload.
A PRACTICAL RECOVERY WORKFLOW
From a working host
to a recoverable environment.
DockerBackup captures selected Compose definitions, deployment inputs, configuration files, small application datasets, and supported database snapshots. It checks file integrity and supported SQLite databases before packaging the captured sources.
The package is encrypted on the source host and uploaded to a designated DockerBackup folder in the owner's Google Drive. A companion restore container can list and download those packages, verify and decrypt them, and restore captured data to a replacement Docker host.
Recovery includes reviewing missing or intentionally excluded data, rebuilding application images, validating application behavior, and updating host-specific storage, network addresses, or tunnels.
Understand the data handlingWHY GOOGLE DRIVE ACCESS IS REQUESTED
Offsite storage,
with an explicit purpose.
Google authorization lets the private backup and restore tools manage encrypted recovery packages in the owner's Drive: create and upload backups, inspect metadata and checksums, download recovery copies, and move expired backups to Trash.
The current integration requests the Google Drive scope https://www.googleapis.com/auth/drive. That scope grants broader Drive access than a single folder. The tools are configured to use the designated backup folder; that configuration is not a Google permission boundary.
TRANSPARENCY COMES FIRST