I have backups for my servers. I have a script that notifies me when the backup succeeds or fails. I manually run backups before any software upgrades.
Today I wanted to upgrade one component in one of the servers, so I started a backup. The backup was broken. Irreversibly broken. For a whole two weeks.
"Whyyyyy?!", I yelled.
I made a mistake on my backup notification script, so it didn't tell me when the backup failed two weeks ago (no, it was not vibe coded). Because of that, the failed backup has been backing up on top of the failed backup.
What's the lesson here? Sometimes custom scripts are cool. Sometimes they are a liability.
Gladly I didn't need the backups. I erased everything and started fresh.
But. Lesson learned. Don't blindly trust the notification scripts. 😄
PS.: Good excuse to go shop for a new backup tool.
#HomeLab nprofile1qyt8wumn8ghj7un9d3shjtnyd968gmewwp6kytcqypw3hqcr7s8dzn2n6fyfm0atmlp2kjydmewfycs8nqgjkeegvsyhycjwp3h (nprofile…wp3h) #Backup
Mauricio Teixeira 👨💻☁️🐧
npub157…m6dhc
2025-11-06 02:12:21 UTC
Author Public Key
npub15733wrmg24u9ja93crx7tnzdsvqnr2r9h4p5vrpde2w34ejx89yq8m6dhcSeen on
wss://relay.ditto.pubPublished at
2025-11-06 02:12:21 UTCEvent JSON
{
"id": "34ebda5dbda6d2c5a1d1ca05f5f30ca20744e968e28190e02991291a11247cd9",
"pubkey": "a7a3170f6855785974b1c0cde5cc4d830131a865bd43460c2dca9d1ae6463948",
"created_at": 1762395141,
"kind": 1,
"tags": [
[
"p",
"5d1b8303f40ed14d53d2489dbfabdfc2ab488dde5c92620798112b6728640972",
"wss://relay.ditto.pub/"
],
[
"p",
"ae1d36e0eefd691293cacf438629d82c492dc2740817ea9a42e970f416484b87",
"wss://relay.ditto.pub/"
],
[
"t",
"homelab"
],
[
"t",
"backup"
],
[
"proxy",
"https://hachyderm.io/users/badnetmask/statuses/115500327973949314",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub/"
]
],
"content": "I have backups for my servers. I have a script that notifies me when the backup succeeds or fails. I manually run backups before any software upgrades.\n\nToday I wanted to upgrade one component in one of the servers, so I started a backup. The backup was broken. Irreversibly broken. For a whole two weeks.\n\n\"Whyyyyy?!\", I yelled.\n\nI made a mistake on my backup notification script, so it didn't tell me when the backup failed two weeks ago (no, it was not vibe coded). Because of that, the failed backup has been backing up on top of the failed backup.\n\nWhat's the lesson here? Sometimes custom scripts are cool. Sometimes they are a liability.\n\nGladly I didn't need the backups. I erased everything and started fresh.\n\nBut. Lesson learned. Don't blindly trust the notification scripts. 😄\n\nPS.: Good excuse to go shop for a new backup tool.\n\n#HomeLab nostr:nprofile1qyt8wumn8ghj7un9d3shjtnyd968gmewwp6kytcqypw3hqcr7s8dzn2n6fyfm0atmlp2kjydmewfycs8nqgjkeegvsyhycjwp3h #Backup",
"sig": "e5841b61ed3fa8401284e6fff2077488a88e1a5943366127e403c14018fe0ea63dc7a527b3b42caba98ab856a694011c5d1e76353f3edac851b3fba4eda01904"
}