#nobackupnomercy — Public Fediverse posts

Wir haben einen (alten) Tresor im (alten) Büro geöffnet, wi niemand mehr wusste ob und falls ja, was da drinn wäre.

Turns out: alte Sony Bänder mit 400GB bzw. 1,5/3,0 TB

Beschriftet mit Monaten und Wochentagen.
In der Schatulle vom dezember lag ein verblasst-beschrifteter Haftnotizzettel bei was wir im Gegenlicht der Sonne dank der veränderten Lichtdurchlässigkeit im Schriftbild als "2016" entziffern konnten.

Dem Azubi erstmal erklärt was das ist, wofür man das brauchte. Unverständlich für ihn. Backups gehören doch in die Cloud damit sie Eventsicher sein!

Wir führten ein langes Gespräch.
Das nur möglich war, weil ich hier im Fediverse so vielen(, passiven) Input bekomme.

#NoBackupNoMercy #Bandspeicher #CyberCrime #NoCloud

Can't recall last time I needed a #backup restore but I guess working late has its consequences.

Editing files directly from the source is always a bad scenario and I avoid it, hence why I use a scratch drive.

But I managed to overwrite one file from the source by accident.

That feeling when you don't panic because you have a backup and you just say to yourself, "you idiot... -.-"
#NoBackupNoMercy

#Synology #HyperBackup #SnapshotReplication #ActiveBackupForBusiness

#selfhosting #selfhosted

Can't recall last time I needed a #backup restore but I guess working late has its consequences.

Editing files directly from the source is always a bad scenario and I avoid it, hence why I use a scratch drive.

But I managed to overwrite one file from the source by accident.

That feeling when you don't panic because you have a backup and you just say to yourself, "you idiot... -.-"
#NoBackupNoMercy

#Synology #HyperBackup #SnapshotReplication #ActiveBackupForBusiness

#selfhosting #selfhosted

Can't recall last time I needed a #backup restore but I guess working late has its consequences.

Editing files directly from the source is always a bad scenario and I avoid it, hence why I use a scratch drive.

But I managed to overwrite one file from the source by accident.

That feeling when you don't panic because you have a backup and you just say to yourself, "you idiot... -.-"
#NoBackupNoMercy

#Synology #HyperBackup #SnapshotReplication #ActiveBackupForBusiness

#selfhosting #selfhosted

Can't recall last time I needed a #backup restore but I guess working late has its consequences.

Editing files directly from the source is always a bad scenario and I avoid it, hence why I use a scratch drive.

But I managed to overwrite one file from the source by accident.

That feeling when you don't panic because you have a backup and you just say to yourself, "you idiot... -.-"
#NoBackupNoMercy

#Synology #HyperBackup #SnapshotReplication #ActiveBackupForBusiness

#selfhosting #selfhosted

Can't recall last time I needed a #backup restore but I guess working late has its consequences.

Editing files directly from the source is always a bad scenario and I avoid it, hence why I use a scratch drive.

But I managed to overwrite one file from the source by accident.

That feeling when you don't panic because you have a backup and you just say to yourself, "you idiot... -.-"
#NoBackupNoMercy

#Synology #HyperBackup #SnapshotReplication #ActiveBackupForBusiness

#selfhosting #selfhosted

Hach, damals, als Instanzen noch #Mailboxen hießen und Admins SysOps. Meine #Mailbox "Boomerang" (hier ANSI-Ansichten von ca. 1989) lief auf RemoteAccess unter MS-DOS. Eine analoge Telefonleitung mit 2400bps-Modem. Später föderierte ich auch im #FIDOnet. Dezentrale Infrastruktur FTW.

Spannende Zeiten für einen 13-Jährigen. Bis dann die Festplatte crashte. #NoBackupNoMercy

The maintenance cycle of my #cloud #provider killed my #FreenetProject #node.

This is how we #learn:
#NoBackupNoMitleid #NoBackupNoMercy