Danil Sidorov
RU EN DE
Telegram

PostgreSQL backups from the browser

A web service for full, incremental and differential PostgreSQL backups without a console or scripts

DevOps / Базы данных

Live interactive demo stand

An exact copy of the project interface and business logic with demo data. All actions run in real time.

Инкрементальные копии без SSH и без updated_at

StackPython, Django, PostgreSQL, S3, Docker

Safe perimeter (NDA): production logic on test data

What to test in the stand:
  1. Создайте инкрементальную копию базы с вычислением diff строк
  2. Переключите хранилище на S3 и проверьте лог шифрования учетных данных
  3. Запустите симуляцию восстановления базы данных через psql
https://datastudio.internal/backups
Live Stand
DataStudio PostgreSQL 17 Backup Manager
admin · worker: active
Всего копий 6 3 базы данных в контуре
Объём хранилища 1.34 ГБ S3 + локальный диск
Последняя копия 8 мин назад billing_demo (Incremental)

Журнал резервных копий

База данных Тип Хранилище Размер Создан Статус Действия

Turnkey implementation

Need a similar system for your business processes?

I will develop the architecture, fault-tolerant backend, and fast interface. Protected by NDA, clean transferable code, and transparent milestones.

  1. Free timeline and budget estimate within one day
  2. Contract and invoice
  3. Warranty and post-launch support

On weekdays usually within a couple of hours

I will reply personally, no aggressive sales pitch

Task

Several PostgreSQL databases had to be backed up without SSH access to the server and without running pg_dump by hand. A full copy of a large database is expensive, so small backups with only the changes were needed between full ones.

Solution

Built a web application on Django. Every backup saves a fingerprint of all rows, and the next one compares the current state with it and writes only the difference: new, changed and deleted rows. The difference goes into a single SQL file applied with plain psql on top of the restored full backup. Before a run the app checks the connection and explains any error in plain words.

What was done

  • Built full backups with pg_dump and incremental and differential ones on top of them
  • Captured every change, deleted rows included, without updated_at columns
  • Tested restores end to end against a real PostgreSQL
  • Moved backups to a background worker, so the site never waits for a dump
  • Offered a choice of storage: the server disk or S3
  • Kept database passwords out of storage: encrypted in the queue and erased after the backup
  • Separated access: every user sees only their own backups

Result

A database backup takes a couple of clicks in the browser, and only the changes are stored between full backups. The code is open on GitHub, and the service starts with a single docker compose up.

Technologies

PythonDjangoPostgreSQLS3Docker

Sources

The links confirm the numbers in this case

Tell me about your task

Telegram