If your backups live on the same server as your app… you have no backups
Published on June 30, 2026
𝗜𝗳 𝘆𝗼𝘂𝗿 𝗯𝗮𝗰𝗸𝘂𝗽𝘀 𝗹𝗶𝘃𝗲 𝗼𝗻 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝘀𝗲𝗿𝘃𝗲𝗿 𝗮𝘀 𝘆𝗼𝘂𝗿 𝗮𝗽𝗽… 𝘆𝗼𝘂 𝗵𝗮𝘃𝗲 𝗻𝗼 𝗯𝗮𝗰𝗸𝘂𝗽𝘀.
I learned that the hard way.
In several projects I started storing database backups directly on the VPS or EC2 where the app was running. Convenient at first. Problematic over time. 😅
Disk space shrinks with every backup. And the worst part: if that server crashes, gets corrupted, or is accidentally deleted… you lose the app AND the backups at the same time. No way to restore. 🔥
Since then I use 𝗦𝟯 or 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗥𝟮 for everything that shouldn't live on the server:
→ 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗯𝗮𝗰𝗸𝘂𝗽𝘀
→ 𝗜𝗺𝗮𝗴𝗲𝘀 and user files
→ 𝗣𝗗𝗙𝘀 and documents
→ Infrastructure files (𝗱𝗼𝗰𝗸𝗲𝗿-𝗰𝗼𝗺𝗽𝗼𝘀𝗲, configs)
The server does what it does best: 𝗿𝘂𝗻 𝘆𝗼𝘂𝗿 𝗮𝗽𝗽. 💻
The storage does what it does best: 𝘀𝘁𝗼𝗿𝗲 𝘆𝗼𝘂𝗿 𝗳𝗶𝗹𝗲𝘀 with redundancy. 🛡️
Separating responsibilities is not just a code principle. It's infrastructure. 💪
Do you already separate your storage from your server? 👇
Keep flying, Champions! ✈️