As I recently kind-of-partly messed up my log a bit (part of improving #wavelog, you may find the pr, fixed before merge ;)) I know about my log-backup quite well: There are nightly MariaDB dumps, which are part of a (deduplicated, versioned, compressed, encrypted) 'default' backup strategy of the server. The resulting backup archive has a 'sporadic' manual rotating offsite offline copy (read harddisks). Weak points: encryption key and software. @hamchallenge #HC14S

#hamchallenge Week 14: My #hamradio logbook #backup system is simple: My central log (to which I live-log contacts and import all my contest logs) is the console logger "YFKlog", which uses a MySQL database backend. It's running on a Hetzner VPS which creates nightly snapshots of the system disk that reach back seven days. In addition, a nightly cron-job creates a database dump which gets rsynced to another VPS in another datacenter. I also regularly upload my log to LoTW. #HC14S @hamchallenge

For this week's #hamchallenge : My primary logging software is #Wavelog. The webserver and backend database both run on virtualized machines in a #HighAvailability #Proxmox #cluster (same one that hosts this instance!). Those are backed up daily to another machine on site via PBS, then those backups are synced to a remote server running in a house in another city.

In addition, my log is also synced to both #QRZ and #LOTW every 6 hours or so, but I didn't think it qualifies as a true backup, since there is some data which those logs don't record.

#HC14S @hamchallenge #hamradio #amatuerradio