Back up your backup system itself, or rebuilding it becomes the disaster
When the server dies, your beautiful backup config dies with it. Capture it:
— Export the cron schedules and the backup scripts to version control
— Document every destination, bucket name, region, and endpoint
— Store credentials for the backup targets OFFsite, separately
— Note retention rules and immutability settings in plain text
— Keep a one-page "how this whole thing works" outside the server
If recovering means first reinventing your entire pipeline from memory, you doubled your downtime. Fight me in the comments.

Their snapshots were perfect — and totally useless

Startup wanted to leave their cloud provider after a price hike. "We have 90 days of snapshots, we're fine." Then they learned the snapshots only restore inside that same provider's platform. Locked in. To actually export the data they had to spin the VMs back up and rsync everything out — 3 days of work and a final $2,200 bill to the vendor they were trying to escape.

A snapshot you can't take elsewhere isn't a backup. It's a hostage note. Fight me in the comments.

Meta ограничивает расходы на токены для сотрудников

Meta ввела внутренние лимиты на использование ИИ из-за резкого роста расходов: в 2026 году только на сотрудников заложены миллиарды долларов, а общий бюджет на ИИ-инфраструктуру оценивается в 130–145 млрд. Вывод простой: даже у Big Tech ИИ перестал быть бесплатной игрушкой и требует жёсткого контроля затрат.

➡️ Читайте на сайте: https://aff.top/blog/meta-ogranichivaet-raskhody-na-tokeny-dlia-sotrudnikov

🧠 Ещё больше инсайтов → в канале AFF.top

Claude Cowork, Claude Design объединили в один Claude

➡️ Читайте на сайте: https://aff.top/blog/claude-cowork-claude-design-obedinili-v-odin-claude

🧠 Ещё больше инсайтов → в канале AFF.top

Microsoft планирует вставлять рекламу в игры

➡️ Читайте на сайте: https://aff.top/blog/microsoft-planiruet-vstavliat-reklamu-v-igry

🧠 Ещё больше инсайтов → в канале AFF.top

Their offsite backup was offsite — and wide open to the internet

Company finally did the right thing: nightly DB dumps to cloud object storage. The bucket was public. A researcher found 2.3 million customer records — names, emails, hashed-but-weak passwords — sitting in plaintext backup files indexed by a search engine.

Fine: regulatory penalty in the low six figures, plus mandatory breach notices to every user.

An unencrypted, public backup isn't safety — it's a breach with extra steps. Encrypt at rest, lock the bucket. Change my mind.

Hunt down the data your backup silently skips, here's the sweep
Every site has a folder nobody told the backup about. Sweep:
— Walk the full web root and list directories your job does NOT cover
— Check for user uploads stored outside the app, in a CDN or separate volume
— Find secrets in env files, queues, and Redis that hold real state
— Catch external state: DNS records, webhook configs, API keys
— Add each gap to the job, then restore-test the WHOLE set
The file you forgot to back up is always the one that ends the company. Change my mind.

Encrypting your backups stops thieves. It does nothing against ransomware. You confused the two.

Ransomware doesn't read your backups, it deletes or encrypts them. Your AES-256 means nothing when the attacker just overwrites the bucket.

What stops them is immutability: object-lock, WORM, append-only repos with a key the server can't revoke.

— Encryption: confidentiality, useless vs deletion
— Immutability: the only thing that survives ransomware

Encrypt AND lock. But if you only did one, you picked the wrong one. Fight me.

You're doing the 3-2-1 rule wrong, and it's not even close.
Most people brag about 3-2-1 then keep all three copies in the same building. That's not 3-2-1, that's three ways to lose everything in one fire. The rule is 3 copies, on 2 different media types, with 1 truly offsite. "Offsite" doesn't mean a second drive in the same server room. It means a different physical location with a different failure domain. A flood, a power surge, a building fire, one landlord lockout — and your "three copies" vanish together. Geography is the whole point. Fight me in the comments.