Backup or Die
Backup or Die
@BackupOrDie

If one set of credentials can reach prod AND every backup, you have one copy with extra steps.

Same SSH key opens the server and the backup NAS. Same cloud login owns the database and the backup bucket. Same human can delete all of it in one bad afternoon, one phished password, one disgruntled exit.
Backups must live behind a separate trust boundary: different account, different keys, pull-based not push-based, with the backup target unable to be reached from a compromised prod box.
Shared blast radius means shared death. Pull architecture beats push every time. Fight me in the comments.
This post was published in the Telegram channel Backup or Die (@BackupOrDie). All its posts are on the channel page.
Open on Telegram

Latest posts in “Tools and infrastructure”

All channels in this category →

реклама в сети

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @AFFtop_connect. Быстрый тест: $20 за канал, $1000 за пакет по сети.