52 Week Ham Radio Challenge 2025 - Week 14: Implement and describe a backup solution for your ham radio log.

Challenge for 2025-03-31 - 2025-04-06:

Category: šŸ–„ļø - Difficulty: šŸŸ¢

Implement and describe a backup solution for your ham radio log.
This may include steps like:


Toots mentioning this challenge

DateUserUser scoreStatusToot summary & link
2025-03-31 09:16:03hobbsc@social.sdf.org1Success!@hamchallenge paper logs for years and then xlog. simple and essentially writes to a text file. it all gets passed around with the rest of my text files by way of syncthing and nightly backups with rsync to an external drive. then weekly backups to a nas.
2025-03-31 10:56:05me@social.k3can.us0Working on it...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
2025-03-31 19:05:03DJ5CW@social.darc.de13Success!#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
2025-04-01 00:54:39mcdanlj@social.makerforums.info7Working on it...Thanks to at least @DJ3CE and @hb9hox for suggesting that I try #wavelog for my #HamRadio logging needs.Yesterday, I accidentally completed HC14 (which I had completely forgotten about) by implementing Wavelog in a docker installation running on top of local RAID on SSD in an AlmaLinux 9 VM on a Fedora 41 server, transferring all my various logs into it, and setting up restic to do daily backups of /var/lib/docker/volumes offsite about 1000 miles away. The restic encryption key is also backed up
2025-04-03 00:53:10ei7ijb@mastodon.radio5Success!For the 14th challenge, 'Implement and describe a backup solution for your ham radio log.ā€™, I realised that my backup options are simple. I keep copies of my ham log in different places like QRZ, Club Log, HamQTH etc., a copy taken automatically into my personal cloud backup, and my favourite paper logbook. Iā€™m not an active operator and do not have the need for an offsite backup. #hamchallenge HC14S @hamchallenge
2025-04-03 07:45:48ian@mastodon.radio12Success!52-week Ham Radio Challenge week 14 is to describe the backup system for your log. I log using a Wavelog instance on a Hetzner VPS, so I'm covered by the daily backups of the machine. I also confirm all contracts with LOTW, QRZ, eQSL and Clublog so I could recover the important bits from any of them if necessary. HC14S
2025-04-04 17:19:22mischk@bunt.social10Success!this one was easy again. I log with POLO and export the logs, then upload them to wavelog and qrz.com. I also save them on my laptop, which is backed up once a month on an external disk. HC14S #hamchallenge #amateurradio
2025-04-04 18:54:31pg4i@mastodon.radio10Success!#hamchallenge HC14S.I have a laptop and a PC in the shack, both running Linux. Although my main logging is on paper, SKCC contacts are logged in SKCCLogger and WWFF logs are entered with FLE under Wine. Backup is made once in a while on an external harddisk using "Back In Time": https://github.com/bit-team/backintime
2025-04-05 10:01:25DJ3CE@social.darc.de9Success!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. #HC14S
2025-04-06 09:00:10g7kse@mastodon.radio12Success!Hmm ham radio log back up. Well this might be controversial..I don't routinely back up my QSO's. I think the logging programme I use does back stuff up but I have so few QSO's at home that it's probably not worth it.Most of my QSO's are xOTA ones. I can't remember ever going back to them and those programmes hold the logs I use for points. But I'm also not bothered about the points. So I'm not that fussed, maybe I should be.HC14S
2025-04-06 21:33:26DC4LW@social.darc.de13Success!For #hamchallenge HC14S I do on- and off-site backups of my computers regularly. So my logs are also in the backup. I use @restic for backup for some years already (and it is developed by a fellow amateur radio operator). From time to time I already restored some data from the backup, so this works as well.The bigger problem are too many logfiles. Quite every digimode app comes with its own logging abilities. And I did not find a proper way to merge all logs yet.@hamchallenge

52 week ham radio challenge: Home